[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266868#comment-15266868
]
Gordon Sim commented on QPID-7230:
----------------------------------
{quote}
I'm using a jms client not the proton library.
{quote}
The details described in that comment are from the JMS client documentation. It
uses proton-j underneath.
{quote}
Even the --log-enable debug+ returns just that it could not bind to any network
address.
{quote}
As mentioned above[1], that means you have a broker already running on another
port.
[1]
https://issues.apache.org/jira/browse/QPID-7230?focusedCommentId=15264202&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15264202
> 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
