[jira] [Commented] (QPID-7230) Broker terminates the connection to JMS Client

["Gordon Sim (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256835#comment-15256835 ] 

Gordon Sim commented on QPID-7230:
----------------------------------

Can you get a trace of the protocol frames (e.g. add --log-enable notice+ --log-enable trace+:Protocol to broker command line options)? That would likely shed some light. Also which JMS client library are you using exactly? (There are a couple of them).

My guess is that persistent messages are working because the client waits until they are confirmed before sending the next. 

> Broker terminates the connection to JMS Client
> ----------------------------------------------
>
>                 Key: QPID-7230
>                 URL: https://issues.apache.org/jira/browse/QPID-7230
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, Java Client
>    Affects Versions: 0.32
>         Environment: Fedora21 and C++ Broker installed by package manager
>            Reporter: Ben
>
> Following scenario: 
> One Producer and one Consumer created by a Java JMS-Client. The Producer is sending 200x15mb non persistent messages to a queue. This queue is located on a local running c++ broker. After few messages my broker terminates the connection with the following exception.
> javax.jms.JMSException: send not allowed after the sender is closed.
> The really astonishing is, that this behavior only occurs with non persistent messages. If I change the delivery mode to persistent, my broker won't close the connection.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org