Bug 917010
Summary: | CacheException: Failure while unregistering mbeans at server shutdown | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jitka Kozana <jkudrnac> |
Component: | Clustering | Assignee: | Dominik Pospisil <dpospisi> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitka Kozana <jkudrnac> |
Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | unspecified | ||
Version: | 6.1.1 | CC: | cdewolf, dpospisi, jkudrnac, lthon, myarboro, rhusar, rjanik, sgilda, smumford |
Target Milestone: | DR6 | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previous versions of JBoss EAP 6 contained a bug in the Infinispan component that could cause the following exception at server shut down:
----
WARN [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000032: Problems un-registering MBeans: org.infinispan.CacheException: Failure while unregistering mbeans
----
The error did not prevent successful shut down of the server and was caused by multiple stop requests (from `CacheService` and `EmbeddedCacheManagerService`) being sent to single cache instances.
This issue was resolved with an upgrade to the Infinispan component.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-28 15:29:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1078158 | ||
Bug Blocks: |
Description
Jitka Kozana
2013-03-01 13:04:01 UTC
Here we have it again in EAP 6.1.0.ER2, this time in ipv4 environment: link to server logs: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Clustering/view/EAP6-Failover/job/eap-6x-failover-ejb-ejbstateless-shutdown-repl-async/13/artifact/report/config/perf21/server.log It also happens in EAP 6.1.0.ER3 and indeed, it is NOT specific to IPv6: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbstateless-shutdown-repl-async/14/console-perf21/ Still seeing this with EAP 6.1.0.ER8. For example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbstateless-jvmkill-repl-async/18/artifact/report/config/jboss-perf21/server.log Still seeing this with EAP 6.1.1.ER7. For example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbstateless-jvmkill-repl-async/25/ Radoslav Husar <rhusar> updated the status of jira AS7-4247 to Closed This should no longer be an issue. Still seeing this issue (EAP 6.2.0.CR3), for example: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-failover-ejb-ejbstateless-jvmkill-repl-async/34/artifact/report/config/jboss-perf19/server.log The cause seems to be that we are getting multiple cache stop request on a single cache instance during server shutdown: 08:56:18,692 DEBUG [org.infinispan.CacheImpl] (ServerService Thread Pool -- 5) Stopping cache repl on localhost/web: java.lang.RuntimeException: StackTrace at org.infinispan.CacheImpl.stop(CacheImpl.java:603) at org.infinispan.CacheImpl.stop(CacheImpl.java:599) at org.infinispan.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:348) at org.jboss.as.clustering.infinispan.subsystem.CacheService.stop(CacheService.java:97) at org.jboss.as.clustering.msc.AsynchronousService$2.run(AsynchronousService.java:113) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final-redhat-1.jar:2.1.1.Final-redhat-1] 08:56:18,790 DEBUG [org.infinispan.CacheImpl] (MSC service thread 1-7) Stopping cache repl on localhost/web: java.lang.RuntimeException: StackTrace at org.infinispan.CacheImpl.stop(CacheImpl.java:603) [infinispan-core-5.2.8.CR1.jar:5.2.8.CR1] at org.infinispan.CacheImpl.stop(CacheImpl.java:599) [infinispan-core-5.2.8.CR1.jar:5.2.8.CR1] at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:732) [infinispan-core-5.2.8.CR1.jar:5.2.8.CR1] at org.infinispan.manager.AbstractDelegatingEmbeddedCacheManager.stop(AbstractDelegatingEmbeddedCacheManager.java:179) [infinispan-core-5.2.8.CR1.jar:5.2.8.CR1] at org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.stop(EmbeddedCacheManagerService.java:76) [jboss-as-clustering-infinispan-7.4.0.Final-redhat-SNAPSHOT.jar:7.4.0.Final-redhat-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2088) [jboss-msc-1.1.5.Final.jar:1.1.5.Final] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2049) [jboss-msc-1.1.5.Final.jar:1.1.5.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] The first comes from CacheService instance running the cache stop method and the second comes from EmbeddedCacheManagerService containing the cache stop method. It seems that Infinispan cachemanager and MSC service management is interleaving. The CacheImpl.stop is not synchronized so there is potential conflict. Dominik Pospisil <dpospisi> updated the status of jira ISPN-4127 to Coding In Progress Mircea Markus <mmarkus> updated the status of jira ISPN-4127 to Resolved We will need to revisit https://bugzilla.redhat.com/show_bug.cgi?id=1036889 for Final to pick up this and other possible fixes. This was seen in 6.3.0.DR4 and was NOT seen in 6.3.0.DR6. I will keep this ON_QA for at least one more build and if we don't see it again, we will mark VERIFIED soon. No problem, sounds like a good approach for issues that can be rarely hit. You can also verify the code changes if you want. This wasn't seen in the last 3 builds (DR6, ER1 and ER2), marking as verified. Changed <literal></literal> tags in Doc Text to ticks (`) and removed <programlisting> tag to fix Bug 1096865 |