[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266899#comment-15266899
]
Ben edited comment on QPID-7230 at 5/2/16 4:13 PM:
---------------------------------------------------
Ah ok didn't know that.
Just using "export PN_TRACE_FRM=true" in my linux shell?
I know what you mean but there is no other broker running. Just my qpid c++
broker runs as a daemon. All other brokers are portable broker that I have to
start manually in my shell. Probably it is possible to use them as a daemon but
I don't have configured them for this. So just the c++ is running on my system.
Netstat says "tcp 0 0 0.0.0.0:5672 0.0.0.0:* LISTEN -". The - at the end of the
line is related to the column "PID/Program name". To me it seems the OS is
listening to this port. But as I said, I can use the broker with small messages
without any problems.
was (Author: ben_):
Ah ok didn't know that.
Just using "export PN_TRACE_FRM=true" in my linux shell?
I know what you mean but there is no other broker running. Just my qpid c++
broker runs as a daemon. All other brokers are portable broker that I have to
start manually in my shell. Probably it is possible to use them as a daemon but
I don't have configured them for this. So just the c++ is running on my system.
Netstat says "tcp 0 0 0.0.0.0:5672 0.0.0.0:* LISTEN -". The "-" at the end of
the line is related to the column "PID/Program name". To me it seems the OS is
listening to this port. But as I said, I can use the broker with small messages
without any problems.
> 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]
