[jboss-jira] [JBoss JIRA] (WFLY-6657) permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set
Marius Ani (JIRA)
issues at jboss.org
Fri May 27 04:50:01 EDT 2016
Marius Ani created WFLY-6657:
--------------------------------
Summary: permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set
Key: WFLY-6657
URL: https://issues.jboss.org/browse/WFLY-6657
Project: WildFly
Issue Type: Bug
Components: Security, Security Manager
Affects Versions: 9.0.1.Final, 8.2.0.Final
Environment: Reproduced on both Windows and RedHat machines.
Reporter: Marius Ani
Assignee: Darran Lofthouse
Priority: Minor
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list