[JBoss JIRA] Created: (JBESB-3344) JAXRRegistryImpl does not unregister services correctly from jUDDI.
3:24 a.m.
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
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
3:29 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3344) JAXRRegistryImpl does not unregister services correctly from jUDDI.
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3344:
-------------------------------------
This is expected behaviour, only the bindings are deleted.
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
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
3:36 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3344) JAXRRegistryImpl does not unregister services correctly from jUDDI.
[
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
4:08 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3344:
--------------------------------
Summary: Modify JAXRRegistryImpl to coalesce multiple registry object creations when
discovered (was: JAXRRegistryImpl does not unregister services correctly from jUDDI.)
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
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
8:53 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3344:
--------------------------------
Attachment: (was: Screen.png)
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
8:53 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3344:
--------------------------------
Fix Version/s: 4.9 CP1
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
8:53 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
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
12:57 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham reassigned JBESB-3344:
-------------------------------------
Assignee: Tom Cunningham
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
Assignee: Tom Cunningham
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
8:41 a.m.
New subject: [JBoss JIRA] Resolved: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham resolved JBESB-3344.
-----------------------------------
Resolution: Done
Coalesce duplicate services into a single aggregate service. If duplicate services
have unique EPRs, transfer the unique ones over to the duplicate service and remove any
duplicates.
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
Assignee: Tom Cunningham
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
8:41 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3344) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered
[
https://jira.jboss.org/browse/JBESB-3344?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham closed JBESB-3344.
---------------------------------
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
Assignee: Tom Cunningham
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
5012
days inactive
5094
days old
9 comments
3 participants
participants (3)
-
Kevin Conner (JIRA) -
Marek Baluch (JIRA)
-
Tom Cunningham (JIRA)