[JBoss JIRA] (LOGMGR-129) Create a better error message if the time zone argument is missing from the %z format pattern
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-129?page=com.atlassian.jira.plugin... ]
James Perkins commented on LOGMGR-129:
--------------------------------------
We may need to considering reworking the date format in general. However it does make sense order may matter in this specific case.
> Create a better error message if the time zone argument is missing from the %z format pattern
> ---------------------------------------------------------------------------------------------
>
> Key: LOGMGR-129
> URL: https://issues.jboss.org/browse/LOGMGR-129
> Project: JBoss Log Manager
> Issue Type: Task
> Reporter: James Perkins
> Assignee: Bartosz Spyrko-Śmietanko
>
> Using the {{%z}} format pattern and not including a time zone argument results in an NPE. A better error message should be thrown indicating an argument is required.
> {code:title=Example pattern}
> %z{GMT}
> {code}
> A bonus would be to possibly add a warning, once only though, if the time {{%d}} was processed before the time zone {{%z}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-6657) permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-6657?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-6657:
-------------------------------
Priority: Major (was: Minor)
> 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: 8.2.0.Final, 9.0.1.Final, 10.1.0.Final, 11.0.0.Beta1
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-6657) permissions.xml is not parsed if -Dorg.jboss.server.bootstrap.maxThreads is explicitly set
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-6657?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-6657:
-------------------------------
Affects Version/s: 11.0.0.Beta1
10.1.0.Final
> 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: 8.2.0.Final, 9.0.1.Final, 10.1.0.Final, 11.0.0.Beta1
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months