You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2017/08/31 19:17:05 UTC
[jira] [Updated] (ARTEMIS-185) 100% transparent failover
[ https://issues.apache.org/jira/browse/ARTEMIS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic updated ARTEMIS-185:
------------------------------------
Fix Version/s: (was: 2.3.0)
2.4.0
> 100% transparent failover
> -------------------------
>
> Key: ARTEMIS-185
> URL: https://issues.apache.org/jira/browse/ARTEMIS-185
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 1.0.0
> Reporter: Miroslav Novak
> Fix For: 2.4.0
>
>
> The client should cache any transactional data, and verify if the information had reached the server or not upon reconnection (through either failover or reconnection).
> Currently standalone JMS client throws exception (ArtemisException 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.4.14#64029)