[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated QPID-7230:
------------------------------
Attachment: 300-a.log
200-a.log
Here's two traces.
* 200-a a transfer of 200,000 bytes that works
* 300-a a transfer of 300,000 bytes that fails
This isn't a Jms client, it's AMQP.Net Lite running helloworld. And it isn't
C++ broker 0.32, it's trunk. I don't think it's client related.
The same pattern holds for megabyte buffers. The incoming transfers work OK but
the reply coming back has an issue.
The broker was on windows running:
{noformat}
D:\qpid\qpid\build_2012_x64\src\Debug>qpidd --auth no --no-data-dir
--load-module amqpd.dll --log-enable notice+ --log-enable trace+:Protocol
--log-enable debug+:Network > T:\300-a.log 2>&1
{noformat}
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
