[
https://issues.jboss.org/browse/WFCORE-1088?page=com.atlassian.jira.plugi...
]
James Perkins commented on WFCORE-1088:
---------------------------------------
The issue wasn't just domain servers. It was seen there because the console does a
composite {{read-resource}} when a deployment is being replaced. The same behavior could
be seen on a standalone server if multiple deployments are present and at least one
deployment is using a custom logging configuration. Executing a composite operation to
read the resources would result in an NPE.
NPE on a domain server when configuring a deployment logging
configuration resource
-----------------------------------------------------------------------------------
Key: WFCORE-1088
URL:
https://issues.jboss.org/browse/WFCORE-1088
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
During the deployment process of a deployment that contains a {{logging.properties}} an
NPE is thrown when adding the runtime data to the deployments configuration resource. This
seems to only happen on one server, {{server-one}} in the default configuration.
{code}
[Server:server-one] 11:57:09,503 ERROR [org.jboss.as.controller.management-operation]
(ServerService Thread Pool -- 69) WFLYCTL0013: Operation ("read-attribute")
failed - address: ([
[Server:server-one] ("deployment" => "batch-jdbc-chunk.war"),
[Server:server-one] ("subsystem" => "logging"),
[Server:server-one] ("configuration" => "default"),
[Server:server-one] ("logger" => "com.arjuna")
[Server:server-one] ]): java.lang.NullPointerException
[Server:server-one] at
org.jboss.as.logging.deployments.resources.LoggerResourceDefinition$3.updateModel(LoggerResourceDefinition.java:92)
[Server:server-one] at
org.jboss.as.logging.deployments.resources.LoggerResourceDefinition$LoggerConfigurationReadStepHandler.updateModel(LoggerResourceDefinition.java:112)
[Server:server-one] at
org.jboss.as.logging.deployments.resources.LoggingConfigurationReadStepHandler.execute(LoggingConfigurationReadStepHandler.java:55)
[Server:server-one] at
org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174)
[Server:server-one] at
org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137)
[Server:server-one] at
org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:263)
[Server:server-one] at
org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:933)
[Server:server-one] at
org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
[Server:server-one] at
org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
[Server:server-one] at
org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
[Server:server-one] at
org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
[Server:server-one] at
org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
[Server:server-one] at
org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler.internalExecute(TransactionalProtocolOperationHandler.java:234)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:173)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:136)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.run(TransactionalProtocolOperationHandler.java:132)
[Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
[Server:server-one] at javax.security.auth.Subject.doAs(Subject.java:360)
[Server:server-one] at
org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:81)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:152)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2$1.run(TransactionalProtocolOperationHandler.java:148)
[Server:server-one] at java.security.AccessController.doPrivileged(Native Method)
[Server:server-one] at
org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$2.execute(TransactionalProtocolOperationHandler.java:148)
[Server:server-one] at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)
[Server:server-one] at
org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:465)
[Server:server-one] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[Server:server-one] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[Server:server-one] at java.lang.Thread.run(Thread.java:745)
[Server:server-one] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{code}
The above logger {{com.arjuna}} shouldn't even be found as it's not in the
deployments logging configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)