Hide Forgot
Date of First Response: 2008-09-14 14:05:25 project_key: SOA From Burr: If you deploy a jboss-esb.xml/.esb archive with a service called "HelloWorld" and then see that in following areas: http://localhost:8080/web-console http://localhost:8080/jbossesb and JON at http://localhost:7080 then you edit the jboss-esb.xml and redeploy so that service is now called "GoodbyeWorld" then the MBean seems to remember the old name and has the new name. It will appear as if both services are still up and alive when in fact there is only one. 2nd part from Burr: after the AS/SOA-P is restarted then it clears up the jbossesb & web-console but JON still shows the old services as "inactive". the only way to clear that up is to UNINVENTORY the platform (a small button under the platform listing of Browse Resources) and re-import from auto-discovery.
Link: Added: This issue depends JBESB-2038
Undeploy all MBeans related to a deployment before the deployment is deployed. This was leading to problems in hot deploys where a service name or service category was changed and duplicate MBeans were registered. drseuss:rosetta tcunning$ svn commit Sending rosetta/src/org/jboss/soa/esb/listeners/config/JBoss4ESBDeployment.java Sending rosetta/src/org/jboss/soa/esb/listeners/lifecycle/LifecycleController.java Transmitting file data .. Committed revision 22759.
Setting Fix Version.
Set ESB component
I have reopened the JBESB issue as the fix is invalid.
I've retested and I am definitely seeing the Service names change. As expected, the old service name does stay around, but it can easily be uninventoried through JON. After a discovery, the new service name will show up. Tested in jmx-console and everything seems fine there too.