You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Created) (JIRA)" <ji...@apache.org> on 2011/10/05 15:34:35 UTC
[jira] [Created] (QPID-3523) the 0-10 client is non compliant in
its use of the exception listener
the 0-10 client is non compliant in its use of the exception listener
---------------------------------------------------------------------
Key: QPID-3523
URL: https://issues.apache.org/jira/browse/QPID-3523
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.12
Reporter: Robbie Gemmell
the 0-10 client is non compliant in its use of the exception listener, with some exceptions being reported both through the exception listener and method calls which caused them or occur after them.
Looking at the JMS spec section for ExceptionListener, it is quite clear about intended behaviour:
"A JMS provider should attempt to resolve connection problems itself prior to notifying the client of them.
The exceptions delivered to ExceptionListener are those which don’t have any other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (i.e. ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection)."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Updated] (QPID-3523) the 0-10 client is non compliant in
its use of the exception listener
Posted by "Rob Godfrey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Godfrey updated QPID-3523:
------------------------------
Description:
the 0-10 client is non compliant in its use of the exception listener, with some exceptions being reported both through the exception listener and method calls which caused them or occur after them.
Looking at the JMS spec section for ExceptionListener, it is quite clear about intended behaviour:
"A JMS provider should attempt to resolve connection problems itself prior to notifying the client of them.
The exceptions delivered to ExceptionListener are those which don't have any other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (i.e. ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection)."
was:
the 0-10 client is non compliant in its use of the exception listener, with some exceptions being reported both through the exception listener and method calls which caused them or occur after them.
Looking at the JMS spec section for ExceptionListener, it is quite clear about intended behaviour:
"A JMS provider should attempt to resolve connection problems itself prior to notifying the client of them.
The exceptions delivered to ExceptionListener are those which don’t have any other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (i.e. ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection)."
> the 0-10 client is non compliant in its use of the exception listener
> ---------------------------------------------------------------------
>
> Key: QPID-3523
> URL: https://issues.apache.org/jira/browse/QPID-3523
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.12
> Reporter: Robbie Gemmell
> Labels: exception-handling
>
> the 0-10 client is non compliant in its use of the exception listener, with some exceptions being reported both through the exception listener and method calls which caused them or occur after them.
> Looking at the JMS spec section for ExceptionListener, it is quite clear about intended behaviour:
> "A JMS provider should attempt to resolve connection problems itself prior to notifying the client of them.
> The exceptions delivered to ExceptionListener are those which don't have any other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (i.e. ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection)."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org