[ https://forge.continuent.org/jira/browse/SEQUOIA-808?page=all ]
Jeff Mesnil resolved SEQUOIA-808:
---------------------------------
Resolution: Fixed
fixed in CVS by adding unregistration of recovery log and abstract scheduler
mbeans in VirtualDatabase.shutdown(int)
> recovery log and scheduler mbeans are not unregistered on vdb shutdown
> ----------------------------------------------------------------------
>
> Key: SEQUOIA-808
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-808
> Project: Sequoia
> Type: Bug
> Components: Management Infrastructure
> Versions: Sequoia 2.10
> Reporter: Jeff Mesnil
> Priority: Minor
> Fix For: Sequoia 2.11
>
>
> When a vdb is shutdown and then restarted, all mbeans instances are not
> properly removed.
> > On vdb reload:
> > 2006-05-25 20:43:45,333 ERROR controller.jmx.MBeanServer MBean with name
> > sequoia:VirtualDataBase=DB1,type=VirtualDataBase.RecoveryLog has already
> > been registered. Deleting old mbean.
> > 2006-05-25 20:43:45,340 ERROR controller.jmx.MBeanServer MBean with name
> > sequoia:VirtualDataBase=DB1,type=VirtualDataBase.AbstractScheduler has
> > already been registered. Deleting old mbean.
> The issue is that the mbeans of the vdb recovery log and scheduler are not
> unregistered when the vdb is shutdown
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
