[
http://jira.jboss.com/jira/browse/JBESB-866?page=all ]
Mark Little reassigned JBESB-866:
---------------------------------
Assignee: Kurt Stam (was: Mark Little)
Kurt and I have discussed this issue in the past. Last time I *think* we decided that it
would be a manual process to remove stale data.
jUDDI retains invalid EPRs
--------------------------
Key: JBESB-866
URL:
http://jira.jboss.com/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
Assigned To: Kurt Stam
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira