[
https://issues.apache.org/jira/browse/QPIDJMS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406410#comment-15406410
]
ASF subversion and git services commented on QPIDJMS-195:
---------------------------------------------------------
Commit dfa2b67394b31712ff58c0fcd3725b1c13094b64 in qpid-jms's branch
refs/heads/master from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=dfa2b67 ]
QPIDJMS-195: Ensure any errors also trip the relevant request failure. Ensure
the executor shutdown is attempted during close.
> misc error handling improvements
> --------------------------------
>
> Key: QPIDJMS-195
> URL: https://issues.apache.org/jira/browse/QPIDJMS-195
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.10.0
> Reporter: Robbie Gemmell
> Fix For: 0.11.0
>
> Attachments:
> 0001-QPIDJMS-195-Ensure-any-errors-also-trip-the-relevant.patch
>
>
> Some recent isses reported on the users list have shown that the client
> doesn't handle Errors (as opposed to Exceptions) well during the connection
> creation process. A couple of examples were from using incompatible version
> of proton-j (due to an older version being embedded within another client
> library being earlier on the classpath), and from failing to make some
> required classes available within an OSGi environment.
> Looking closer, this is because the relevant tasks are passed to an Executor,
> but only Exceptions are caught within the task and used to fail their related
> requests, with the Executor itself swallowing any Errors when they weren't
> handled. We should trip request failure upon seeing Errors as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
