qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (QPID-7230) Broker terminates the connection to JMS Client
Date Wed, 27 Apr 2016 19:38:13 GMT

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

Ben edited comment on QPID-7230 at 4/27/16 7:37 PM:
----------------------------------------------------

Hi gordon,

I'm using this maven dependency:
<groupId>org.apache.qpid</groupId>
<artifactId>qpid-jms-client</artifactId>
<version>0.8.0</version>

Ok so I used just "qpidd --log-enable notice+ --log-enable trace+:Protocol"
And that's the output:
[Broker] notice Broker (pid=4979) start-up
[Security] notice SSL plugin not enabled, you must set --ssl-cert-db to enable it.
[Broker] notice SASL disabled: No Authentication Performed
[Network] warning Couldn't listen to: 0.0.0.0:5672: Can't bind to port 0.0.0.0:5672: Address
already in use (/builddir/build/BUILD/qpid-cpp-0.32/src/qpid/sys/posix/BSDSocket.cpp:197)
[Network] warning Couldn't listen to: [::]:5672: Can't bind to port [::]:5672: Address already
in use (/builddir/build/BUILD/qpid-cpp-0.32/src/qpid/sys/posix/BSDSocket.cpp:197)
[Broker] critical Broker (pid=4979) start-up failed: Couldn't find any network address to
listen to
[Broker] notice Broker (pid=4979) shut-down
[Broker] critical Unexpected error: Couldn't find any network address to listen to

Huge messages are really slow. A persistent 15MB message needs 10 seconds to be received.
After sending few big messages, the whole broker slows down. Now even 0MB messages need 10
seconds to be received. Just a broker restart would help. Afterwards my tiny messages are
fast as before. So after sending big messages the whole broker have problems. But I don't
know whether this is another issue and not related to the connection closing.


was (Author: ben_):
Hi gordon,

I'm using this maven dependency:
<groupId>org.apache.qpid</groupId>
<artifactId>qpid-jms-client</artifactId>
<version>0.8.0</version>

Ok so I used just "qpidd --log-enable notice+ --log-enable trace+:Protocol"
And that's the output:
[Broker] notice Broker (pid=4979) start-up
[Security] notice SSL plugin not enabled, you must set --ssl-cert-db to enable it.
[Broker] notice SASL disabled: No Authentication Performed
[Network] warning Couldn't listen to: 0.0.0.0:5672: Can't bind to port 0.0.0.0:5672: Address
already in use (/builddir/build/BUILD/qpid-cpp-0.32/src/qpid/sys/posix/BSDSocket.cpp:197)
[Network] warning Couldn't listen to: [::]:5672: Can't bind to port [::]:5672: Address already
in use (/builddir/build/BUILD/qpid-cpp-0.32/src/qpid/sys/posix/BSDSocket.cpp:197)
[Broker] critical Broker (pid=4979) start-up failed: Couldn't find any network address to
listen to
[Broker] notice Broker (pid=4979) shut-down
[Broker] critical Unexpected error: Couldn't find any network address to listen to

Huge messages are really slow. A persistent 15MB message needs 10 seconds to be received.
After sending few big messages, the whole broker slows down. Now even 0MB messages need 10
seconds to be received. Just a broker restart brings help. Then my tiny messages are fast
as before. So after sending big messages the whole broker have problems sending messages.
But I don't know whether this is another issue and not related to the connection close.

> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message