You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Toralf Lund <to...@pgs.com> on 2015/03/27 09:52:51 UTC
Problems with auto-creation of exchange
Hi,
I'm having problems with the auto-create functionality in the C++
messaging API. Simply put, I pass the following address string to
Session::createSender(), hoping to create and connect to an exchange
that does not originally exist:
pgs.data; { create: sender, delete: never, node: { type: topic,
durable: False } }
I then get the error message
Create failed for exchange pgs.data; not-found: not-found: Exchange
not found: pgs.data
(/work/build/build/qpid-0.22/cpp/src/qpid/broker/ExchangeRegistry.cpp:144)
Can someone spot the obvious mistake here? I thought the setup worked in
the past, but I may have been imagining things, as always.
- Toralf
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 04/07/2015 12:28 PM, Toralf Lund wrote:
> I notice that I do use the same session for the sender and receiver
[...]
> Once I sort out this issue, everything works as expected
Super, thanks for the update Toralf!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Toralf Lund <to...@pgs.com>.
Hi,
I didn't have time to look into this problem again until today, and now
I notice that I do use the same session for the sender and receiver. The
"extra" session object gets created, but is never actually used. It's
essentially a case of stupidly using the same variable name twice
combined with confusion about which one is in scope :-( Once I sort out
this issue, everything works as expected.
- Toralf
On 27/03/15 16:31, Gordon Sim wrote:
> 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
>
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Gordon Sim <gs...@redhat.com>.
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
Re: Problems with auto-creation of exchange
Posted by Toralf Lund <to...@pgs.com>.
On 27/03/15 15:23, Gordon Sim wrote:
> On 03/27/2015 01:40 PM, Toralf Lund wrote:
>> On 27/03/15 12:41, Gordon Sim wrote:
>>> On 03/27/2015 08:52 AM, Toralf Lund wrote:
>>>> Hi,
>>>>
>>>> I'm having problems with the auto-create functionality in the C++
>>>> messaging API. Simply put, I pass the following address string to
>>>> Session::createSender(), hoping to create and connect to an exchange
>>>> that does not originally exist:
>>>>
>>>> pgs.data; { create: sender, delete: never, node: { type: topic,
>>>> durable: False } }
>>>>
>>>> I then get the error message
>>>>
>>>> Create failed for exchange pgs.data; not-found: not-found: Exchange
>>>> not found: pgs.data
>>>> (/work/build/build/qpid-0.22/cpp/src/qpid/broker/ExchangeRegistry.cpp:144)
>>>>
>>>>
>>>>
>>>> Can someone spot the obvious mistake here? I thought the setup
>>>> worked in
>>>> the past, but I may have been imagining things, as always.
>>>
>>> It works for me, both on trunk and for the 0.22 release, using your
>>> address as above with the spout example.
>> OK.
>>
>> It turns out that everything works in my case, too, if I move the exact
>> same code to a different spot. So I guess there is something weird going
>> on with the way everything is structured. Perhaps it's related to the
>> fact that I look for an existing sender first via getSender() (using the
>> plain exchange name.) I suppose I need to look a bit closer at the
>> logic...
>
> Can you get a broker protocol trace? That might help identify what is
> going on in more detail.
OK. Some trace is included below (with a slight change to some addresses.)
I think I've found out a bit what's going on, though. The thing is, 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.
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: INIT(0-10)
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionStartBody:
server-properties={qpid.federation_tag:V2:36:str16(868927e9-ea3a-439f-8072-a48a108b0be3)};
mechanisms=str16{V2:9:str16(ANONYMOUS), V2:5:str16(PLAIN)};
locales=str16{V2:5:str16(en_US)}; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionStartOkBody:
client-properties={qpid.client_pid:F4:int32(17523),qpid.client_ppid:F4:int32(1193),qpid.client_process:V2:2:str16(rg),qpid.session_flow:F4:int32(1)};
mechanism=ANONYMOUS; response=xxxxxx; locale=en_US; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionTuneBody: channel-max=32767; max-frame-size=65535;
heartbeat-min=0; heartbeat-max=120; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionTuneOkBody: channel-max=32767; max-frame-size=65535;
heartbeat=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionOpenBody: virtual-host=; capabilities=void{}; insist=1; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=0;
{ConnectionOpenOkBody: known-hosts=str16{}; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionAttachBody: name=9606ff50-76b2-495d-932f-de771820763a; }]
2015-03-27 15:56:55 [Protocol] debug Attached channel 1 to
anonymous@QPID.9606ff50-76b2-495d-932f-de771820763a
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionAttachedBody: name=9606ff50-76b2-495d-932f-de771820763a; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionCommandPointBody: command-id=0; command-offset=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionRequestTimeoutBody: timeout=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionCommandPointBody: command-id=0; command-offset=0; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=1;
{SessionTimeoutBody: timeout=0; }]
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;
{SessionCompletedBody: commands={ [0,0] }; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionAttachBody: name=f1470736-b206-4a40-8b88-30480a3aae77; }]
2015-03-27 15:56:55 [Protocol] debug Attached channel 2 to
anonymous@QPID.f1470736-b206-4a40-8b88-30480a3aae77
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionAttachedBody: name=f1470736-b206-4a40-8b88-30480a3aae77; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionCommandPointBody: command-id=0; command-offset=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionRequestTimeoutBody: timeout=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionCommandPointBody: command-id=0; command-offset=0; }]
2015-03-27 15:56:55 [Protocol] trace RECV
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{ExecutionSyncBody: }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionTimeoutBody: timeout=0; }]
2015-03-27 15:56:55 [Protocol] trace SENT
[qpid.127.0.0.1:5672-127.0.0.1:44092]: Frame[BEbe; channel=2;
{SessionCompletedBody: commands={ [0,0] }; }]
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={}; }]
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; }]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 03/27/2015 01:40 PM, Toralf Lund wrote:
> On 27/03/15 12:41, Gordon Sim wrote:
>> On 03/27/2015 08:52 AM, Toralf Lund wrote:
>>> Hi,
>>>
>>> I'm having problems with the auto-create functionality in the C++
>>> messaging API. Simply put, I pass the following address string to
>>> Session::createSender(), hoping to create and connect to an exchange
>>> that does not originally exist:
>>>
>>> pgs.data; { create: sender, delete: never, node: { type: topic,
>>> durable: False } }
>>>
>>> I then get the error message
>>>
>>> Create failed for exchange pgs.data; not-found: not-found: Exchange
>>> not found: pgs.data
>>> (/work/build/build/qpid-0.22/cpp/src/qpid/broker/ExchangeRegistry.cpp:144)
>>>
>>>
>>> Can someone spot the obvious mistake here? I thought the setup worked in
>>> the past, but I may have been imagining things, as always.
>>
>> It works for me, both on trunk and for the 0.22 release, using your
>> address as above with the spout example.
> OK.
>
> It turns out that everything works in my case, too, if I move the exact
> same code to a different spot. So I guess there is something weird going
> on with the way everything is structured. Perhaps it's related to the
> fact that I look for an existing sender first via getSender() (using the
> plain exchange name.) I suppose I need to look a bit closer at the logic...
Can you get a broker protocol trace? That might help identify what is
going on in more detail.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Toralf Lund <to...@pgs.com>.
On 27/03/15 12:41, Gordon Sim wrote:
> On 03/27/2015 08:52 AM, Toralf Lund wrote:
>> Hi,
>>
>> I'm having problems with the auto-create functionality in the C++
>> messaging API. Simply put, I pass the following address string to
>> Session::createSender(), hoping to create and connect to an exchange
>> that does not originally exist:
>>
>> pgs.data; { create: sender, delete: never, node: { type: topic,
>> durable: False } }
>>
>> I then get the error message
>>
>> Create failed for exchange pgs.data; not-found: not-found: Exchange
>> not found: pgs.data
>> (/work/build/build/qpid-0.22/cpp/src/qpid/broker/ExchangeRegistry.cpp:144)
>>
>>
>> Can someone spot the obvious mistake here? I thought the setup worked in
>> the past, but I may have been imagining things, as always.
>
> It works for me, both on trunk and for the 0.22 release, using your
> address as above with the spout example.
OK.
It turns out that everything works in my case, too, if I move the exact
same code to a different spot. So I guess there is something weird going
on with the way everything is structured. Perhaps it's related to the
fact that I look for an existing sender first via getSender() (using the
plain exchange name.) I suppose I need to look a bit closer at the logic...
- Toralf
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Problems with auto-creation of exchange
Posted by Gordon Sim <gs...@redhat.com>.
On 03/27/2015 08:52 AM, Toralf Lund wrote:
> Hi,
>
> I'm having problems with the auto-create functionality in the C++
> messaging API. Simply put, I pass the following address string to
> Session::createSender(), hoping to create and connect to an exchange
> that does not originally exist:
>
> pgs.data; { create: sender, delete: never, node: { type: topic,
> durable: False } }
>
> I then get the error message
>
> Create failed for exchange pgs.data; not-found: not-found: Exchange
> not found: pgs.data
> (/work/build/build/qpid-0.22/cpp/src/qpid/broker/ExchangeRegistry.cpp:144)
>
> Can someone spot the obvious mistake here? I thought the setup worked in
> the past, but I may have been imagining things, as always.
It works for me, both on trunk and for the 0.22 release, using your
address as above with the spout example.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org