[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3344:
--------------------------------
Description:
It is possible for the same registry objects to be created concurrently, especially with
multiple VMs, leading to certain registry objects being created multiple times when only
one occurrence is expected.
We need to identify those objects which should be single instances and then have the
JAXRRegistryImpl check, then coalesce, any discovered.
was:
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.
Modify JAXRRegistryImpl to coalesce multiple registry object
creations when discovered
--------------------------------------------------------------------------------------
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
Fix For: 4.9 CP1
It is possible for the same registry objects to be created concurrently, especially with
multiple VMs, leading to certain registry objects being created multiple times when only
one occurrence is expected.
We need to identify those objects which should be single instances and then have the
JAXRRegistryImpl check, then coalesce, any discovered.
--
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