]
Brian Stansberry moved WFLY-6657 to WFCORE-3199:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-3199 (was: WFLY-6657)
Component/s: Security
(was: Security)
(was: Security Manager)
Affects Version/s: 3.0.0.Beta31
(was: 8.2.0.Final)
(was: 9.0.1.Final)
(was: 11.0.0.Beta1)
(was: 10.1.0.Final)
permissions.xml is not parsed if
-Dorg.jboss.server.bootstrap.maxThreads is explicitly set
------------------------------------------------------------------------------------------
Key: WFCORE-3199
URL:
https://issues.jboss.org/browse/WFCORE-3199
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.0.Beta31
Environment: Reproduced on both Windows and RedHat machines.
Reporter: Marius Ani
If -Dorg.jboss.server.bootstrap.maxThreads is explictily set in Wildfly, then, the
permissions.xml file is not even parsed when the application is deployed.
Debugging the Wildfly 8.2.0 source code revealed the problem in
org.jboss.as.server.ServerService#addService:218
{code:java}
if (configuration.getServerEnvironment().isAllowModelControllerExecutor()) {
serviceBuilder.addDependency(Services.JBOSS_SERVER_EXECUTOR,
ExecutorService.class, service.getExecutorServiceInjector());
}
{code}
The org.jboss.as.server.ServerEnvironment#allowModelControllerExecutor property is set to
true if -Dorg.jboss.server.bootstrap.maxThreads was set.
The above 'if' seems a little strange because a default value for maxThreads is
always set in org.jboss.as.server.ServerEnvironment#getBootstrapMaxThreads even when the
-Dorg.jboss.server.bootstrap.maxThreads property was not specified.
This may also cause other things to not work properly when
-Dorg.jboss.server.bootstrap.maxThreads is set.