[
https://issues.apache.org/jira/browse/QPID-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268616#comment-15268616
]
Robbie Gemmell commented on QPID-7230:
--------------------------------------
As Gordon has mentioned a couple times, the fact the logging indicates the port
(5672) is in use when you try to start the C++ broker on the command line,
means you have something else running on port 5672, and so the command line
initiated C++ broker does not start up. It would seem your other broker tests
should have the same issue if started at similar point, though not all brokers
necessarily shut down in error when their port is already in use at startup, so
you need to be careful that you are actually connecting to what you think you
are (a useful check: connection attempts should fail immediately before you
start the intended broker).
If you are connecting to port 5672 during your testing (if not, please say
so..) and that testing is working at all immediately following the 'in-use'
error, then the something on 5672 is obviously speaking AMQP 1.0. You'd need to
stop the thing on port 5672 (which could well be one of the other brokers you
mention testing..) before starting the C++ broker on the command line with the
trace logging options Gordon suggested. Alternatively, go for his subsequent
suggestion of enabling the protocol trace on the client side, and repeating
your test to get the protocol trace logging.
I can't say I have tried setting/adjusting the 'queue size' on the C++ broker,
but can I enquire if you had deleted the queue before adding it again with the
new config? If not, that seems worth a try (I'm not sure if that config affects
existing queues, or even whether you can issue the 'add' without error in such
cases when the queue already exists). Also, are you clearing the queue out
between runs? Adjusting the config may not help [enough] if the queue is still
largely full of stuff from prior runs.
> 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
