[
https://issues.apache.org/jira/browse/QPID-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15445702#comment-15445702
]
Lorenz Quack commented on QPID-7405:
------------------------------------
I don't think message parsing is something we want. I don't consider error
messages part of the API (with the exception of operational logging) so I
generally feel free to change them without notice.
Previously, I was considering adding cause-specific exceptions as
Cause/LinkedException.
Now, I just saw that the JMSException has a second constructor taking a vendor
specific error code (of type String). I think this would be a reasonable usage
of the same.
> [Java Client] Improve application-side detectability of Producer side
> FlowControl
> ---------------------------------------------------------------------------------
>
> Key: QPID-7405
> URL: https://issues.apache.org/jira/browse/QPID-7405
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Lorenz Quack
>
> If the broker enforces producer side flow control which then causes a timeout
> the application code currently only sees a JMSException with no way (except
> for error message parsing) to detect the cause of the exception.
> We should consider improving the detectability of flow control so that
> application code can customise the handling of different timeout causes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
