[ https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268963#comment-15268963 ]
Robbie Gemmell commented on QPID-7230: -------------------------------------- Ok so it seems like the underlying issue is throughput with large messages, as Gordon raised QPID-7241 for already, leading to the queue size being hit, with broker and client seeming to act approprialtey given that. I'm going to close this JIRA out and suggest tracking further progress on QPID-7241, as this one has become a bit scattered and the only apparent issue looks to be what precisely what QPID-7241 covers. We can always reopen if needed. > 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 > Attachments: 200-a.log, 300-a.log, ben-trace.log > > > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org