[
https://issues.jboss.org/browse/WFCORE-2089?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2089:
------------------------------------------
The main problem I believe is internal calls by the server itself, where now we have a new
requirement for some service that is easily misconfigured by the user, and that
doesn't do anything obviously beneficial to the handling of internal calls. We've
added fragility for little gain.
Presumably if the realm service fails to start, the management interface services depend
on it so they won't start. So outside callers should not have access that way.
Even if we abort the start of the server, I am not confident this call path will not
prevent a clean abort. Perhaps not now but it seems quite easy to inadvertently make some
change and end up calling into this.
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: Darran Lofthouse
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)