Sorry I misread the stack trace - I thought it was a Connection.close
rather than a consumer.close(). I think all the .close() methods
should have a timeout and silently complete if the transport is down.
On 16/11/2007, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
>
> Strange, just tried it again the
Strange, just tried it again there with a basic AMQ test (no RCP etc), and I
get exception when closing listeners "Transport is not running" and app
exits OK. Its the same version of AMQ. What is the behaviour that you would
expect, hang or exception?
James.Strachan wrote:
>
> BTW does the same
BTW does the same thing occur in ActiveMQ 5.x? IIRC there's now a
timeout on closing things down avoiding this block
On 16/11/2007, TOPPER_HARLEY <[EMAIL PROTECTED]> wrote:
>
> Hi,
> Using AMQ4.1.1 with standalone server with embedded broker. Client apps have
> Spring message listeners. If we have
