qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7230) Broker terminates the connection to JMS Client
Date Fri, 29 Apr 2016 16:11:13 GMT

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

Gordon Sim commented on QPID-7230:
----------------------------------

A simpler way to get the protocol trace in your case may be to do so on the client. From the
client doc:

{quote}
When debugging some issues, it may sometimes be useful to enable additional protocol trace
logging from the Qpid Proton AMQP 1.0 library. There are two options to achieve this:

+ Set the environment variable (not Java system property) *PN_TRACE_FRM* to *true*, which
will cause Proton to emit frame logging to stdout.
+ Add the option *amqp.traceFrames=true* to your connection URI to have the client add a protocol
tracer to Proton, and configure the *org.apache.qpid.jms.provider.amqp.FRAMES* Logger to *TRACE*
level to include
 the output in your logs.

{quote}

That would clearly show if the broker is detaching due to a queue limit.

> 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