]
Tom Cunningham updated JBESB-3629:
----------------------------------
Fix Version/s: 4.11
(was: 4.10 CP1)
Moved out of SOA-5.2.0.GA.
Provide alternative registry implementation
-------------------------------------------
Key: JBESB-3629
URL:
https://issues.jboss.org/browse/JBESB-3629
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.10 CP1
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.11
The issue here is: in a cluster environment, after a malfunction on JBoss (e.g. JVM
crash, erroneous deployment etc) the registry remains with invalid endpoints and the ESB
has an erroneous behavior by using those endpoints. Even your removeDeadEPR property is
unusable, because as stated in the documentation the "the end-point reference for a
service that is [...] slow to respond may, inadvertently, be removed from the registry by
mistake".
Since we have a cluster and to manually clean the DB is not just to drop the tables and
restart the server, this is a major issue for us, because it can lead to erroneous service
calls if a server node crashes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: