-
Bug
-
Resolution: Done
-
Major
-
None
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
if (configuration.getServerEnvironment().isAllowModelControllerExecutor()) {
serviceBuilder.addDependency(Services.JBOSS_SERVER_EXECUTOR, ExecutorService.class, service.getExecutorServiceInjector());
}
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.
- clones
-
WFCORE-3199 permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set
- Resolved
- is incorporated by
-
JBEAP-12378 (7.1.0) Upgrade to WildFly Core to 3.0.1.Final-redhat
- Closed