[
https://issues.jboss.org/browse/WFLY-5046?page=com.atlassian.jira.plugin....
]
Clebert Suconic updated WFLY-5046:
----------------------------------
Summary: JMS Clients should retry any TX transparently (100% transparent failover)
(was: Clients should not throw HornetQException/JMSException to application code during
failover)
Issue Type: Feature Request (was: Enhancement)
Priority: Major (was: Critical)
JMS Clients should retry any TX transparently (100% transparent
failover)
-------------------------------------------------------------------------
Key: WFLY-5046
URL:
https://issues.jboss.org/browse/WFLY-5046
Project: WildFly
Issue Type: Feature Request
Components: JMS
Affects Versions: 10.0.0.Alpha1
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Currently standalone JMS client throws exception (HornetQException or JMSException) to
client application code during failover/failback and leaves on application programmer to
handle this exception and retry the last operation.
This makes client code complex and developer must spent additional effort to handle those
edge cases. This is complicated to achieve especially for consumer with transacted session
of client acknowledge.
Goal of this RFE is to provide exception free behaviour for standalone JMS clients.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)