qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: Problems with auto-creation of exchange
Date Fri, 27 Mar 2015 15:31:46 GMT
On 03/27/2015 03:12 PM, Toralf Lund wrote:
> I'm also setting up a temporary receiver with auto-create as a way of
> making sure a "well-known" receiver queue is set up and bound to the
> exchange. This is something that's tried and retried until it's
> successful, but it turns out that the first attempt occurs before the
> above mentioned sender initialisation. If I remove the receiver setup,
> everything works fine. So I guess this operation raises type of
> exception that will block future operations. Does that make sense? Note
> that I use the same connection object, but a different session, when
> setting up this receiver.

The session that hits the error would indeed be 'stcuk' in error mode. 
However it *shouldn't* affect other sessions on the same connection.

In the trace:

> 2015-03-27 15:56:55 [Protocol] trace RECV [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {QueueDeclareBody: queue=pgs.xxx.yyy; alternate-exchange=; arguments={qpid.last_value_queue:F1:boolean(1),qpid.last_value_queue_key:V2:12:str16(message_type)};
}]
> 2015-03-27 15:56:55 [Protocol] trace RECV [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {ExchangeBindBody: queue=pgs.xxx.yyy; exchange=pgs.data; binding-key=pgs.xxx.yyy.#;
arguments={}; }]

this is the receiver, I assume...

> 2015-03-27 15:56:55 [Protocol] error Execution exception: not-found: Exchange not found:
pgs.data (qpid/broker/ExchangeRegistry.cpp:144)
> 2015-03-27 15:56:55 [Protocol] trace RECV [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {ExecutionSyncBody: }]
> 2015-03-27 15:56:55 [Protocol] trace SENT [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {ExecutionExceptionBody: error-code=404; command-id=2; class-code=7; command-code=4;
field-index=0; description=not-found: Exchange not found: pgs.data (qpid/broker/ExchangeRegistry.cpp:144);
error-info={}; }]
> 2015-03-27 15:56:55 [Protocol] trace SENT [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {SessionDetachBody: name=9606ff50-76b2-495d-932f-de771820763a; }]
> 2015-03-27 15:56:55 [Protocol] trace RECV [qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe;
channel=1; {SessionDetachedBody: name=9606ff50-76b2-495d-932f-de771820763a; code=0; }]

... the session is detached now, and the same error shouldn't be thrown 
on any other session unless there was a further attempt to use the 
exchange before it was declared.

Was this trace for a segment of time that included the sender failure? 
If so is it at all possible the sender is in fact using the same 
session? (Because the trace doesn't seem to show the senders 
interactions. There are two sessions attached, but the second isn't 
really used.)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message