[
http://jira.jboss.com/jira/browse/JBPORTAL-1730?page=comments#action_1240... ]
Thomas Heute commented on JBPORTAL-1730:
----------------------------------------
registerMBean is in charge of registering (and throw an exception in case it's already
registered or couldn't register). So the logic shouldn't be there.
That said, all the calls to registerMBean are previously called with unregisterMBean which
would have the same effect as what you are doing here.
So in your case what is happening ? What's calling registerMBean ? What issue do you
face, what's the stack trace ?
IdentityServiceControllerImpl : unregister existing MBean service
before to re register them
--------------------------------------------------------------------------------------------
Key: JBPORTAL-1730
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1730
Project: JBoss Portal
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Portal Identity
Affects Versions: 2.6.1 Final
Reporter: Antoine Herzog
Assigned To: Thomas Heute
Priority: Optional
Fix For: 2.6.5 Final
In IdentityServiceControllerImpl (service
name="portal:service=Module,type=IdentityServiceController")
the Identity Beans are registered as JMX MBeans.
When redeploying the service, an exception is thrown, as the services are yet deployed.
javax.management.InstanceAlreadyExistsException: portal:service=Module,type=User already
registered.
Let's put this code before to register the bean, at line 378 of
IdentityServiceControllerImpl.java
// Unregister the former service is if it is yet there.
// This to avoid the exception when redeploying this service
if (getServer().isRegistered(
new ObjectName(module.getServiceName()))) {
getServer().unregisterMBean(
new ObjectName(module.getServiceName()));
}
Thanks,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira