qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Godfrey <rob.j.godf...@gmail.com>
Subject Re: AMQP 1.0 JMS Client hangs on connection.close
Date Thu, 02 Jan 2014 13:05:27 GMT
However - having now looked at the proton-c bug - I see why you can't do
that :-)

In the meantime I'll patch the JMS client...

-- Rob


On 2 January 2014 14:02, Rob Godfrey <rob.j.godfrey@gmail.com> wrote:

> I agree that the JMS client should probably set close=true on the detach
> as it never actually tries to resume, but I think that the correct response
> of the C++ broker should still be to detach (perhaps itself setting
> close=true) even though it is incapable of resuming.  The only other
> alternative would be to close the session/connection with an error I think.
>
> -- Rob
>
>
> On 2 January 2014 13:37, Gordon Sim <gsim@redhat.com> wrote:
>
>> On 01/01/2014 07:12 PM, Rob Godfrey wrote:
>>
>>> OK - I've checked in a fix for the client so it does now timeout when you
>>> attempt the close.
>>>
>>> I imagine Gordon is also out at the moment, but hopefully he can help us
>>> with the C++ broker when he gets back.
>>>
>>
>> I've commented on the JIRA, but to repeat briefly here, the JMS client is
>> detaching without closing (which I suspect may not be what is intended) and
>> that isn't yet supported by proton-c (which the c++ broker uses for its 1.0
>> support).
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message