[
https://jira.jboss.org/jira/browse/JBESB-866?page=com.atlassian.jira.plug...
]
Joakim Sandström commented on JBESB-866:
----------------------------------------
Still is really annoying during development and specially in a clustered production
environment.
Patch available upon request.
jUDDI retains invalid EPRs
--------------------------
Key: JBESB-866
URL:
https://jira.jboss.org/jira/browse/JBESB-866
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 3
Reporter: Jiri Pechanec
Assignee: Kurt Stam
Fix For: 4.2
If the ESB is terminated (crashes) it will retain EPRs in the database. Unfortunately
when the EPR is changed e.g. by renaming of underlaying queue, both old and new EPRs are
stored in jUDDI registry on the next start. Then under heavier load both EPRs are selected
with the result of lot error messages related to unavailable EPR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira