[
https://issues.apache.org/jira/browse/QPIDJMS-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740872#comment-14740872
]
Timothy Bish commented on QPIDJMS-108:
--------------------------------------
Don't think there was much thought put into the async send case for the error
path. Seems we should add an event point for non-fatal error that just bubble
up to the connection ExceptionListener that doesn't trigger failover.
Currently the failover bit will not fail for JMSException error to allow the
JMS layer to decide if the error is fatal or not.
> producers don't correctly handle modified/released delivery state
> -----------------------------------------------------------------
>
> Key: QPIDJMS-108
> URL: https://issues.apache.org/jira/browse/QPIDJMS-108
> Project: Qpid JMS
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Robbie Gemmell
> Fix For: 0.6.0
>
>
> Producers don't correctly handle modified/released delivery state, treating
> it as an unknown update. They currently only handle accepted adn rejected
> states. In the case of a synchronous send (the default for persistent
> messages on non-tx sessions), this leads to the send call waiting for such a
> state to be attained which it may never be. This was encountered when sending
> messages to Dispatch without a receiver running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
