[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Marek Baluch updated JBESB-3344:
--------------------------------
Attachment: Screen.png
Added jUDDI console screen after QS undeployment. This screen shows also what happens when
another QS is deployed which has same service names the same as the QS deployed before
that.
JAXRRegistryImpl does not unregister services correctly from jUDDI.
-------------------------------------------------------------------
Key: JBESB-3344
URL:
https://jira.jboss.org/browse/JBESB-3344
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository, Rosetta
Affects Versions: 4.7 CP1, 4.7 CP2
Reporter: Marek Baluch
Priority: Blocker
Attachments: Screen.png
JAXRRegistryImpl does not unregister services correctly from jUDDI. Only bindings are
deleted but the service itself remains in the registry.
These orphaned service records cause also problems when there are more server instances
in the cluster.
How to reproduce
-------------------
Just deploy and undeploy a QS. Then have a look in jUDDI console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira