Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.24
-
None
-
CentOS 6.4, Qpid 0.24 RC1, Proton 0.4
Description
I have a C++ client based on the qpid.messaging / AMQP 1.0. This client has a container-id specified in the connection options. This client creates a receiver with following address:
z/response.ABCFR_ABCFRALMMACC1.response_queue_1; { create: never, link:
{ name: 'response.ABCFR_ABCFRALMMACC1.response_queue_1', durable: false }}
where z is a name of a topic. The client alone seems to be working fine. It creates the receiver and waits for a message.
However, when I start second instance of the same program, it results in a broker crash. I assume it might be related to the fact that it uses the same container-id and link name.
A trace log from the broker is attached.