[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268842#comment-15268842
]
Robbie Gemmell commented on QPID-7230:
--------------------------------------
How to configure it depends on what logging framework youa re using. As the doc
(http://qpid.apache.org/releases/qpid-jms-0.9.0/docs/index.html#logging)
mentions, the client uses the SLF4J logging framework, with you then picking an
actual logging implementation that suits your needs, e.g log4j, logback, jul,
etc.
The examples (https://github.com/apache/qpid-jms/tree/master/qpid-jms-examples)
use log4j, with the slf4j-log4j binding listed in the pom, and log4j itself
then configured via log4j.properties on the classpath.
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
