[
https://issues.apache.org/jira/browse/QPID-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094988#comment-13094988
]
Rajith Attapattu commented on QPID-3461:
----------------------------------------
An easy way to reproduce the issue is to send x number of messages to Queue A
in a transacted session, where the qpid.max_count for Queue A is x-1. This will
cause the broker to throw an exception when a commit is issued for that
transaction.
Another way to reproduce that issue is to start a two node close and kill the
broker the client is connected just before a commit is issued.
> A SessionException is thrown (instead of a JMSException) when an error occurs
> during a commit.
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-3461
> URL: https://issues.apache.org/jira/browse/QPID-3461
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.10, 0.12
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.14
>
>
> If the broker throws a session level exception, during or just before the
> client invokes a commit on a transaction, the JMS client throws a
> SessionException instead of a JMSException.
> This is due to the AMQSession_0_10.java not handing the SessionException.
> (Please note this issue is only present in the 0-10 code path).
--
This message is automatically generated by JIRA.
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:[email protected]
