[jboss-jira] [JBoss JIRA] (WFLY-5046) Clients should not throw HornetQException/JMSException to application code during failover

[Miroslav Novak (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak moved JBEAP-567 to WFLY-5046:
--------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-5046  (was: JBEAP-567)
             Workflow: GIT Pull Request workflow   (was: CDW v1)
    Affects Version/s: 10.0.0.Alpha1
                           (was: EAP 7.0.0.DR1)
          Component/s: JMS
                           (was: JMS)
       Target Release:   (was: EAP 7.0.0.GA)


> Clients should not throw HornetQException/JMSException to application code during failover
> ------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5046
>                 URL: https://issues.jboss.org/browse/WFLY-5046
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JMS
>    Affects Versions: 10.0.0.Alpha1
>            Reporter: Miroslav Novak
>            Assignee: Clebert Suconic
>            Priority: Critical
>
> 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)