Bug 794032 (JBEPP-1101)

Summary:	Warning with stacktrace when server is shutdown: Could not unregister the MBean exo:portal="portal",service=TokenStore,name="jcr-token"
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Matt Wringe <mwringe>
Component:	Portal	Assignee:	Default User <jbpapp-maint>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.2.0.DEV03	CC:	epp-bugs
Target Milestone:	---
Target Release:	5.2.0.GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1101
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-16 14:20:19 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:

Description Matt Wringe 2011-08-22 15:26:31 UTC

project_key: JBEPP

When ever the portal is shutdown, the following stack trace occurs:

11:19:14,663 WARN  [JMXManagementProvider] Could not unregister the MBean exo:portal="portal",service=TokenStore,name="jcr-token"
javax.management.InstanceNotFoundException: exo:portal="portal",service=TokenStore,name="jcr-token" is not registered.
	at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526)
	at org.jboss.mx.server.MBeanServerImpl.unregisterMBean(MBeanServerImpl.java:383)
	at org.exoplatform.management.jmx.impl.JMXManagementProvider$3.run(JMXManagementProvider.java:203)
	at org.exoplatform.management.jmx.impl.JMXManagementProvider$3.run(JMXManagementProvider.java:200)
	at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedExceptionAction(SecurityHelper.java:309)
	at org.exoplatform.management.jmx.impl.JMXManagementProvider.unmanage(JMXManagementProvider.java:199)
	at org.exoplatform.container.management.ManagementContextImpl.unregisterAll(ManagementContextImpl.java:271)
	at org.exoplatform.container.management.ManageableContainer.stop(ManageableContainer.java:260)
	at org.exoplatform.container.ExoContainer.stop(ExoContainer.java:281)
	at org.exoplatform.container.PortalContainer.stop(PortalContainer.java:674)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:100)
	at org.exoplatform.container.LifecycleVisitor.stop(LifecycleVisitor.java:179)
	at org.exoplatform.container.ConcurrentPicoContainer.stop(ConcurrentPicoContainer.java:567)
	at org.exoplatform.container.management.ManageableContainer.stop(ManageableContainer.java:262)
	at org.exoplatform.container.ExoContainer.stop(ExoContainer.java:281)
	at org.exoplatform.container.RootContainer.stop(RootContainer.java:728)
	at org.exoplatform.container.RootContainer$ShutdownThread.run(RootContainer.java:721)

NOTE: its a WARN and not an error stack trace, but it still should not be happening.

Comment 1 Matt Wringe 2011-08-22 15:27:52 UTC

Its an issues in the JCR. We may need to update the version we are using to fix it.

Comment 2 Matt Wringe 2011-08-22 15:27:52 UTC

Link: Added: This issue depends EXOJCR-1473

Comment 4 Jared MORGAN 2011-11-16 03:38:13 UTC

Release Notes Docs Status: Added: Not Required