October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1089) IgnoredResourcesProfileCloneTestCase does not well for domain stabilization following reload

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1089: ---------------------------------------- Summary: IgnoredResourcesProfileCloneTestCase does not well for domain stabilization following reload Key: WFCORE-1089 URL: https://issues.jboss.org/browse/WFCORE-1089 Project: WildFly Core Issue Type: Bug Components: Domain Management, Test Suite Affects Versions: 2.0.0.CR9 Reporter: Brian Stansberry IgnoredResourcesProfileCloneTestCase several times reloads the slave HC without restarting its servers. But it then does not wait for those servers to reconnect before continuing on. This means the servers may not be reattached to the domain when further modifications are made. I'm quite certain this is the cause of the failure at http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=76866&tab=buil... and the other time that test failed. IgnoredResourcesProfileCloneTestCase reloads the slave and then exits. CompositeOperationTestCase follows and immediately adds system-property=composite-op in its @Before method. The other-two server doesn't get this op as it's not reconnected. The test then later fails because the other-two server's state is not as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5607) EJB Server side is needlessly closing remoting channel

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5607?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-5607: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1276513 Bugzilla Update: Perform > EJB Server side is needlessly closing remoting channel > ------------------------------------------------------ > > Key: WFLY-5607 > URL: https://issues.jboss.org/browse/WFLY-5607 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.CR4 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > When an EJB Bean throws a Runtime exception, it is causing the server side to close the remoting channel. This causes several issues such as performance issue of having to recreate the channel, channel leak on the client side and some occasional EJBCLIENT...25 - no ejb receiver exceptions on the client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5607) EJB Server side is needlessly closing remoting channel

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-5607?page=com.atlassian.jira.plugin.... ] Brad Maxwell reassigned WFLY-5607: ---------------------------------- Assignee: Brad Maxwell > EJB Server side is needlessly closing remoting channel > ------------------------------------------------------ > > Key: WFLY-5607 > URL: https://issues.jboss.org/browse/WFLY-5607 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.CR4 > Reporter: Brad Maxwell > Assignee: Brad Maxwell > > When an EJB Bean throws a Runtime exception, it is causing the server side to close the remoting channel. This causes several issues such as performance issue of having to recreate the channel, channel leak on the client side and some occasional EJBCLIENT...25 - no ejb receiver exceptions on the client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5607) EJB Server side is needlessly closing remoting channel

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-5607: ---------------------------------- Summary: EJB Server side is needlessly closing remoting channel Key: WFLY-5607 URL: https://issues.jboss.org/browse/WFLY-5607 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.CR4 Reporter: Brad Maxwell When an EJB Bean throws a Runtime exception, it is causing the server side to close the remoting channel. This causes several issues such as performance issue of having to recreate the channel, channel leak on the client side and some occasional EJBCLIENT...25 - no ejb receiver exceptions on the client side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5606) ManagementOnlyModeTestCase uses non-standard reload idioms

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-5606: -------------------------------------- Summary: ManagementOnlyModeTestCase uses non-standard reload idioms Key: WFLY-5606 URL: https://issues.jboss.org/browse/WFLY-5606 Project: WildFly Issue Type: Bug Components: Domain Management, Test Suite Reporter: Brian Stansberry Assignee: Tomaz Cerar Fix For: 11.0.0.Alpha1 ManagementOnlyModeTestCase was recently reenabled after being turned off for a long time. But it has intermittent failures[1] so I'm going to re-disable it. Looking at it, it's doing some reloads but in a custom way. Custom reloads have been the source of tons of problems, so my assumption is this one is just another case of that and it needs to use the standard approach. [1] http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WildFlyCore_... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1088) NPE on a domain server when configuring a deployment logging configuration resource

by James Perkins (JIRA)

[ 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1087) ManagementResourceRegistration.getOrderedChildTypes() does not account for override models

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1087?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1087: ------------------------------------- Priority: Major (was: Blocker) > ManagementResourceRegistration.getOrderedChildTypes() does not account for override models > ------------------------------------------------------------------------------------------ > > Key: WFCORE-1087 > URL: https://issues.jboss.org/browse/WFCORE-1087 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR9 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Final > > > ManagementResourceRegistration.getOrderedChildTypes() is implemented by simply reading the local state of ConcreteResourceRegistration. It needs to work like getAttributeNames(), by delegating to the root node which in turn uses NodeSubregistry to combine data from any singleton override registration and the corresponding wildcard registration. > Same kind of problem as WFCORE-1086. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1088) NPE on a domain server when configuring a deployment logging configuration resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1088?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1088: ---------------------------------- Description: 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. was: 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. The runtime subsystem resource doesn't seem to get the correct model or logging configuration in domain mode. > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1088) NPE on a domain server when configuring a deployment logging configuration resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1088?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1088: ---------------------------------- Description: 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. The runtime subsystem resource doesn't seem to get the correct model or logging configuration in domain mode. was: 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. > 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. The runtime subsystem resource doesn't seem to get the correct model or logging configuration in domain mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1088) NPE on a domain server when configuring a deployment logging configuration resource

by James Perkins (JIRA)

James Perkins created WFCORE-1088: ------------------------------------- Summary: 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)

7 years, 7 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2015