[JBoss JIRA] (JBWEB-276) Using non-blocking thread pool causes excessive RejectedExecutionExceptions to be logged
by James Livingston (JIRA)
[ https://issues.jboss.org/browse/JBWEB-276?page=com.atlassian.jira.plugin.... ]
James Livingston updated JBWEB-276:
-----------------------------------
Attachment: JBWEB-276-2.patch
This patch is similar, except it creates a new logging category (org.apache.tomcat.util.executor) and leaves the level at ERROR.
> Using non-blocking thread pool causes excessive RejectedExecutionExceptions to be logged
> ----------------------------------------------------------------------------------------
>
> Key: JBWEB-276
> URL: https://issues.jboss.org/browse/JBWEB-276
> Project: JBoss Web
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: JBossWeb-7.2.0.Beta1
> Reporter: James Livingston
> Assignee: Remy Maucherat
> Attachments: JBWEB-276-1.patch, JBWEB-276-2.patch
>
>
> When a finite-queue thread pool is used to process web requests, the queue being full can either block or drop the request. If you use a pool which drops requests, a RejectedExecutionException is thrown.
> Currently JIoEndpoint catches that exception the same as other ones such as being unable to create threads. When using a non-blocking pool, the task being rejected is not a critical error like other exceptions so should not be logged at ERROR level.
> Under excessive load, these exception will be continuously generated as requests are dropped, which cases a large amount of logging. Setting it to DEBUG level would stop that, but it would hide the potentially useful messages by default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-1370) Add ability to load CDI portable extensions from static modules
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1370?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1370:
-----------------------------------------------
Scott Mumford <smumford(a)redhat.com> made a comment on [bug 927895|https://bugzilla.redhat.com/show_bug.cgi?id=927895]
Added a revised release note draft since this bug is now resolved. Please review and confirm technical accuracy.
Including base-matter here for further reference if required:
Cause:
CDI portable extensions were not picked up from a static module that had its services exposed to the deployment
Consequence:
CDI Portable extensions from a static module were not working unless they were explicitly activated in the deployment with META-INF/services/javax.enterprise.inject.spi.Extension file.
Fix:
The way CDI portable extensions are loaded was changed, so they will be picked up from any module that has its services exposed to the deployment
Result:
CDI portable extensions can now be loaded from a static module.
> Add ability to load CDI portable extensions from static modules
> ---------------------------------------------------------------
>
> Key: WFLY-1370
> URL: https://issues.jboss.org/browse/WFLY-1370
> Project: WildFly
> Issue Type: Feature Request
> Components: CDI / Weld
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Fix For: 8.0.0.Alpha2
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-1362) javax.transaction.xa.XAException thrown when using JTS transactions
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1362?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1362:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 981174|https://bugzilla.redhat.com/show_bug.cgi?id=981174] from MODIFIED to ON_QA
> javax.transaction.xa.XAException thrown when using JTS transactions
> -------------------------------------------------------------------
>
> Key: WFLY-1362
> URL: https://issues.jboss.org/browse/WFLY-1362
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.0.0.Alpha1
> Environment: JBoss EAP 6.1 ER8
> Reporter: Tom Ross
> Assignee: jaikiran pai
> Fix For: 8.0.0.Alpha2
>
>
> When running the quick start ejb-multi-server example with JTS transactions the following exception is thrown:
> {noformat}
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) javax.transaction.xa.XAException
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ats.internal.jta.transaction.jts.jca.XATerminatorImple.recover(XATerminatorImple.java:238)
> 11:21:01,462 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.tryRecoveryForImportedTransaction(XidTransactionManagementTask.java:109)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionCommitTask.manageTransaction(XidTransactionCommitTask.java:62)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.run(XidTransactionManagementTask.java:68)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> 11:21:01,463 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at java.lang.Thread.run(Thread.java:722)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 11:21:01,464 ERROR [stderr] (RequestProcessor-5) at ...asynchronous invocation...(Unknown Source)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.sendCommit(RemotingConnectionEJBReceiver.java:327)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl.commit(EJBClientManagedTransactionContext.java:239)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.commit(XAResourceRecord.java:455)
> 11:21:01,465 ERROR [stderr] (RequestProcessor-5) at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:201)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626)
> 11:21:01,466 ERROR [stderr] (RequestProcessor-5) at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769)
> 11:21:01,467 WARN [com.arjuna.ats.jtax] (RequestProcessor-5) ARJUNA024023: XAResourceRecord.commit caused an XA error: XAException.XAER_PROTO from resource ResourceImpl{transactionKey=0:ffffc0a80164:316a9a9d:5196046f:1a, ejbClientContext=org.jboss.ejb.client.EJBClientContext@216695c0, nodeName='master:app-oneB', state=null} in transaction < 131072, 30, 36, 0000000000-1-1-64-88110049106-102-9981-1064111000264849, 303030303030303030302929-34-583113079136-72-69111-7634141303030567879303030303030 >: javax.transaction.xa.XAException
> at com.arjuna.ats.internal.jta.transaction.jts.jca.XATerminatorImple.recover(XATerminatorImple.java:238) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.tryRecoveryForImportedTransaction(XidTransactionManagementTask.java:109)
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionCommitTask.manageTransaction(XidTransactionCommitTask.java:62)
> at org.jboss.as.ejb3.remote.protocol.versionone.XidTransactionManagementTask.run(XidTransactionManagementTask.java:68)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_21]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_21]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.ejb.client.remoting.InvocationExceptionResponseHandler$MethodInvocationExceptionResultProducer.getResult(InvocationExceptionResponseHandler.java:99)
> at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.sendCommit(RemotingConnectionEJBReceiver.java:327)
> at org.jboss.ejb.client.EJBClientManagedTransactionContext$ResourceImpl.commit(EJBClientManagedTransactionContext.java:239)
> at com.arjuna.ats.internal.jta.resources.jts.orbspecific.XAResourceRecord.commit(XAResourceRecord.java:455) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at com.arjuna.ArjunaOTS.OTSAbstractRecordPOA._invoke(OTSAbstractRecordPOA.java:201) [jbossjts-jacorb-4.17.4.Final-redhat-2.jar:4.17.4.Final-redhat-2]
> at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:306) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:626) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:769) [jacorb-2.3.2-redhat-4.jar:2.3.2-redhat-4]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-1503) Unable to remove custom logging handler
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1503?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1503:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 975085|https://bugzilla.redhat.com/show_bug.cgi?id=975085] from MODIFIED to ON_QA
> Unable to remove custom logging handler
> ---------------------------------------
>
> Key: WFLY-1503
> URL: https://issues.jboss.org/browse/WFLY-1503
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 8.0.0.Alpha1
> Reporter: Carlo de Wolf
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 8.0.0.Alpha4
>
>
> During removal of the custom handler in {{Log4jCustomHandlerTestCase}} the following error is shown:
> {noformat}
> 09:38:24,266 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014612: Operation ("remove") failed - address: ([
> ("subsystem" => "logging"),
> ("custom-handler" => "customFileAppender")
> ]): java.lang.IllegalArgumentException: No reference found for 'org.jboss.as.logging.logmanager.Log4jAppenderHandler'
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$5.validate(AbstractPropertyConfiguration.java:399) [jboss-logmanager-1.4.1.Final.jar:1.4.1.Final]
> at org.jboss.logmanager.config.AbstractPropertyConfiguration$5.validate(AbstractPropertyConfiguration.java:391) [jboss-logmanager-1.4.1.Final.jar:1.4.1.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:333) [jboss-logmanager-1.4.1.Final.jar:1.4.1.Final]
> at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:292) [jboss-logmanager-1.4.1.Final.jar:1.4.1.Final]
> at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:302) [wildfly-logging-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97) [wildfly-logging-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:235) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:124) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:148) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:97) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:114) [wildfly-controller-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [wildfly-protocol-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [wildfly-protocol-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> {noformat}
> This effectively puts the server in a dead state (WFLY-1497 is hiding this issue, because it leaves the handler disabled).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-1379) log4j appenders force initialization of the appender/handler on reboot
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1379?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1379:
-----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 971190|https://bugzilla.redhat.com/show_bug.cgi?id=971190] from MODIFIED to ON_QA
> log4j appenders force initialization of the appender/handler on reboot
> ----------------------------------------------------------------------
>
> Key: WFLY-1379
> URL: https://issues.jboss.org/browse/WFLY-1379
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 8.0.0.Alpha1
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 8.0.0.Alpha2
>
>
> Adding a log4j appender works until the server is rebooted. The difference in the class names, {{org.apache.log4j.SomeAppender}} and manually added {{org.jboss.as.logging.logmanager.Log4jAppenderHandler}}, results in the handler being reconfigured.
> This also hits a bug (LOGMGR-58) in the logmanager where null references are can be retrieved before a full commit is invoked.
> Stack trace:
> {code}
> 10:53:44,909 ERROR [stderr] (Controller Boot Thread) java.lang.NullPointerException
> 10:53:44,909 ERROR [stderr] (Controller Boot Thread) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> 10:53:44,912 ERROR [stderr] (Controller Boot Thread) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 10:53:44,912 ERROR [stderr] (Controller Boot Thread) at java.lang.reflect.Method.invoke(Method.java:601)
> 10:53:44,915 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:218)
> 10:53:44,915 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:198)
> 10:53:44,916 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doApplyPostCreate(LogContextConfigurationImpl.java:316)
> 10:53:44,916 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:341)
> 10:53:44,916 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:290)
> 10:53:44,917 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:282)
> 10:53:44,917 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97)
> 10:53:44,917 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
> 10:53:44,917 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
> 10:53:44,918 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
> 10:53:44,918 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
> 10:53:44,918 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:296)
> 10:53:44,919 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:226)
> 10:53:44,919 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:342)
> 10:53:44,919 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:317)
> 10:53:44,919 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:189)
> 10:53:44,920 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:722)
> 10:53:44,920 ERROR [stderr] (Controller Boot Thread) java.lang.NullPointerException
> 10:53:44,921 ERROR [stderr] (Controller Boot Thread) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> 10:53:44,921 ERROR [stderr] (Controller Boot Thread) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 10:53:44,922 ERROR [stderr] (Controller Boot Thread) at java.lang.reflect.Method.invoke(Method.java:601)
> 10:53:44,922 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:218)
> 10:53:44,923 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:198)
> 10:53:44,923 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doApplyPostCreate(LogContextConfigurationImpl.java:316)
> 10:53:44,923 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:341)
> 10:53:44,924 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:290)
> 10:53:44,925 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:282)
> 10:53:44,925 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97)
> 10:53:44,926 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
> 10:53:44,926 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
> 10:53:44,926 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
> 10:53:44,927 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
> 10:53:44,927 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:296)
> 10:53:44,928 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:226)
> 10:53:44,928 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:342)
> 10:53:44,928 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:317)
> 10:53:44,929 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:189)
> 10:53:44,929 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:722)
> 10:53:44,930 ERROR [stderr] (Controller Boot Thread) java.lang.NullPointerException
> 10:53:44,931 ERROR [stderr] (Controller Boot Thread) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> 10:53:44,931 ERROR [stderr] (Controller Boot Thread) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 10:53:44,931 ERROR [stderr] (Controller Boot Thread) at java.lang.reflect.Method.invoke(Method.java:601)
> 10:53:44,932 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:218)
> 10:53:44,932 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.AbstractPropertyConfiguration$1.applyPostCreate(AbstractPropertyConfiguration.java:198)
> 10:53:44,933 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doApplyPostCreate(LogContextConfigurationImpl.java:316)
> 10:53:44,933 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:341)
> 10:53:44,933 ERROR [stderr] (Controller Boot Thread) at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:290)
> 10:53:44,934 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:282)
> 10:53:44,934 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97)
> 10:53:44,934 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
> 10:53:44,935 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
> 10:53:44,935 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
> 10:53:44,936 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
> 10:53:44,936 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:296)
> 10:53:44,937 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:226)
> 10:53:44,937 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:342)
> 10:53:44,937 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.server.ServerService.boot(ServerService.java:317)
> 10:53:44,938 ERROR [stderr] (Controller Boot Thread) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:189)
> 10:53:44,938 ERROR [stderr] (Controller Boot Thread) at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (AS7-4932) CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4932?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4932:
----------------------------------------------
Paul Gier <pgier(a)redhat.com> changed the Status of [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549] from MODIFIED to ON_QA
> CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
> -------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4932
> URL: https://issues.jboss.org/browse/AS7-4932
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: as713tracking
> Fix For: 7.1.3.Final (EAP)
>
>
> NPE is thrown in roughly 0.36% of HTTP session request processing in the test.
> This results in response code 503 returned to the client with the exception.
> The test is using passivation-enabled WAR of clusterbench
> https://github.com/rhusar/clusterbench
> Here is a shorter soak test run that uncovered the issue
> https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Clustering-Soak/jo...
> {noformat}
> [JBossINF] 19:52:10,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-2570) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:972) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1377) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:673) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:84) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months