[
http://jira.jboss.com/jira/browse/JBESB-417?page=comments#action_12359721 ]
Burr Sutter commented on JBESB-417:
-----------------------------------
I believe the specific situations are starting to be addressed by other Jira tasks such
507
439
438
There may be an adjustment needed to the lookup code so that it picks randomly from the
list of EPRs returned. I'm not sure what logic is now. This will help with basic
load-balancing and graceful undeployment should unregister its EPRs and they should no
longer have traffic routed to them. This item likely needs its own Jira task.
Service lifecycle
-----------------
Key: JBESB-417
URL:
http://jira.jboss.com/jira/browse/JBESB-417
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Management, Rosetta
Reporter: Mark Little
Assigned To: Kevin Conner
Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2
Both simple lifecycle on single bus as well as dev, test, staging, production management
--
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