[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264202#comment-15264202
]
Gordon Sim commented on QPID-7230:
----------------------------------
The address in use error means there is another broker listening on that port.
If you have root privileges you can shut down the qpidd service (e.g. sudo
service qpidd stop) then start it in a console again (remember to restart the
service is you need it afterwards).
The c++ broker has a default maximum queue depth in bytes. If that is exceeded
it will detach the sending link. If the sender continues to send on that same
link after that, then the broker would close the connection. You can alter the
limits per queue using qpid-config or the broker wide default using the
default-queue-limit option either as a command line argument or through the
conf file. The default conf file location depends on how the broker was
built/packaged/installed. Often it is in /etc/qpid/qpidd.conf, you can see
where it is on your system through the qpidd --help options. There should be an
error logged on the broker if links are detached for hitting the limit.
Large persistent messages are indeed slow with the c++ broker (I see 20MB
messages taking about 1 second though, so not as slow as you are seeing). I
have also observed that sending non-persistent messages over AMQP 1.0 is an
order of magnitude slower than over AMQP 0-10 though that is with the c++
client and I haven't determined whether it is the client or the broker (or
both!) at fault there.
I haven't hit anything like the symptom you describe where the broker becomes
very slow even for smaller messages. My guess there is that either the memory
use is causing swapping or that perhaps the queue is flow controlled(?).
I'll see if I can get a test client for the JMS client you are using.
> 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]
