Re: Stomp transactions

[singlaive <mu...@mirriad.com>]

After 9 years, this interesting post had no comments or explainations. I just
test and verified activeMQ still works the same way, which I think is
problematic.

Any more thoughts?



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Stomp transactions

[Tim Bain <tb...@alumni.duke.edu>]

Have you confirmed that the broker host (at the OS level) doesn't believe
that the TCP connection is still alive at the time you're saying the broker
is wrongly failing to deliver the message to a new client? If you
ungracefully terminate a TCP connection, the remote side (the broker in
this case) can only detect that fact after the TCP timeout has elapsed
without receiving more bytes across the connection. So if you did your test
before that window has elapsed, then the behavior you described would be
correct. If you've waited long enough that your broker's OS shows the TCP
connection as closed and you get the behavior you describe, then that
sounds like a bug and I encourage you to submit a bug in JIRA for it.

Tim

On Thu, Nov 15, 2018, 7:45 AM singlaive <murphy.meng@mirriad.com wrote:

> After 9 years, this interesting post had no comments or explainations. I
> just
> test and verified activeMQ still works the same way, which I think is
> problematic.
>
> Any more thoughts?
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>