February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2089) Infinite wildfly boot on StartException in service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2089: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2143 (was: https://github.com/wildfly/wildfly-core/pull/2053) > Infinite wildfly boot on StartException in service start > -------------------------------------------------------- > > Key: WFCORE-2089 > URL: https://issues.jboss.org/browse/WFCORE-2089 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Jan Kalina > Assignee: ehsavoie Hugonnet > Priority: Blocker > Attachments: threads-2.txt, threads.txt > > > Following exception (and probably similar too) will cause wildfly frozing during start. Visible especially during integration tests (which will never ends), but reproducible directly too (see steps). > {code:java} > 15:59:37,252 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service org.wildfly.security.security-realm.ManagementRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ManagementRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185) > at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > *Update:* This problem with infinite boot will occure everytime the start() method of some service throws StartException(). Not an Elytron problem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2256) Undertow 1.4.10.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-2256: -------------------------------------- Summary: Undertow 1.4.10.Final Key: WFCORE-2256 URL: https://issues.jboss.org/browse/WFCORE-2256 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2216) CLI fails to reload when connection upgrades from http to https

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2216?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2216: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2126 (was: https://github.com/wildfly/wildfly-core/pull/2113) > CLI fails to reload when connection upgrades from http to https > --------------------------------------------------------------- > > Key: WFCORE-2216 > URL: https://issues.jboss.org/browse/WFCORE-2216 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 3.0.0.Alpha23 > > > reload command should manage to reconnect to a server reconfigured with https management interface. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2223) Setting JBOSS_MODULEPATH is lost for second start of embed-server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2223?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2223: ---------------------------------------- Fix Version/s: 3.0.0.Alpha23 Assignee: Brian Stansberry (was: Jean-Francois Denise) Resolution: Done > Setting JBOSS_MODULEPATH is lost for second start of embed-server > ----------------------------------------------------------------- > > Key: WFCORE-2223 > URL: https://issues.jboss.org/browse/WFCORE-2223 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Server > Reporter: Josef Cacek > Assignee: Brian Stansberry > Priority: Critical > Fix For: 3.0.0.Alpha23 > > > When {{embed-server}} command is used more times in the CLI and a custom {{JBOSS_MODULEPATH}} is configured, then only the first server start uses the correct module path. > The subsequent `embed-server` call results in error: > {code} > Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0118: Determined modules directory does not exist: /tmp/jboss-eap-7.0-no-modules/modules > {code} > Using the {{JBOSS_MODULEPATH}} environment variable is documented in https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2255) Upgrade to WildFly Common 1.2.0.Beta5

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2255: ---------------------------------------- Summary: Upgrade to WildFly Common 1.2.0.Beta5 Key: WFCORE-2255 URL: https://issues.jboss.org/browse/WFCORE-2255 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha23 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1855) Possible NPE on controller service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1855?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1855: ------------------------------------------ https://github.com/bstansberry/wildfly-core/tree/WFCORE-1855 is WIP on this. Kind of a workaround. I opened up a PR for it but I think I'll withdraw it for now as it's a bit out of date and I don't feel urgency to get this particular solution in. > Possible NPE on controller service start > ---------------------------------------- > > Key: WFCORE-1855 > URL: https://issues.jboss.org/browse/WFCORE-1855 > Project: WildFly Core > Issue Type: Bug > Reporter: David Lloyd > Assignee: Brian Stansberry > > In {{org.jboss.as.controller.AbstractControllerService}}, the {{start}} method starts up a background thread which performs a certain amount of the boot process. Before this thread is started, a volatile field {{controller}} is initialized with the controller reported by the {{start()}} method. > Inside this thread, some work is performed, and at the end of a certain amount of work, the {{finishBoot()}} method is invoked. This method calls {{controller.finishBoot()}}, referencing the field that was set in the {{start()}} method. > The problem arises when the service itself is stopped before the boot thread completes. This causes the {{controller}} field to be nulled out, resulting in an NPE. > I think we need to look at: > * Why are we using a background thread for this? > * Why are we _not_ using the asynchronous startup feature? > I think we must do one of these two things in order to make this code "safe". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1855) Possible NPE on controller service start

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1855?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1855: ---------------------------------------- Assignee: Brian Stansberry > Possible NPE on controller service start > ---------------------------------------- > > Key: WFCORE-1855 > URL: https://issues.jboss.org/browse/WFCORE-1855 > Project: WildFly Core > Issue Type: Bug > Reporter: David Lloyd > Assignee: Brian Stansberry > > In {{org.jboss.as.controller.AbstractControllerService}}, the {{start}} method starts up a background thread which performs a certain amount of the boot process. Before this thread is started, a volatile field {{controller}} is initialized with the controller reported by the {{start()}} method. > Inside this thread, some work is performed, and at the end of a certain amount of work, the {{finishBoot()}} method is invoked. This method calls {{controller.finishBoot()}}, referencing the field that was set in the {{start()}} method. > The problem arises when the service itself is stopped before the boot thread completes. This causes the {{controller}} field to be nulled out, resulting in an NPE. > I think we need to look at: > * Why are we using a background thread for this? > * Why are we _not_ using the asynchronous startup feature? > I think we must do one of these two things in order to make this code "safe". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-906) SetCallbackHandlerAuthenticationConfiguration should support all sasl mechanisms

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-906: ------------------------------------ Summary: SetCallbackHandlerAuthenticationConfiguration should support all sasl mechanisms Key: ELY-906 URL: https://issues.jboss.org/browse/ELY-906 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta22 SetCallbackHandlerAuthenticationConfiguration should however not override the saslAllowedByConfiguration as that is policy. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2160: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2076, https://github.com/wildfly/wildfly-core/pull/2140 (was: https://github.com/wildfly/wildfly-core/pull/2076) > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > Fix For: 3.0.0.Alpha23 > > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-2160: -------------------------------------- > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > Fix For: 3.0.0.Alpha23 > > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017