[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268631#comment-15268631
]
Ben commented on QPID-7230:
---------------------------
I already said several times that there is no other broker running on that
port. Netstat showed that there is nor pid listening on that port. And also
mentioned that the c++ broker WORKS. I can send millions of small messages
without any problem. Just sending bis messages will cause the described
problem. So I don't know why this error occurs in log because the server is
running and does not terminate.
by the way, my c++ broker is not command line, it is running as a linux daemon.
I said that I have to start all other brokers via command line. But as gordon
recommended, I will activate the protocol trace on the client side and repeat
my test.
My queue is not durable and before adding the queue with configured size, I
restart the broker daemon. That also means the queue is empty when I start a
test.
> 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]
