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)
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
nce the transaction never finished and my TCP
> connection was terminated, the ACK should have been rolled back and my
> next client that connects should receive a retransmission of MSG1.
>
> Can anyone explain what is going on here?
>
> Thanks
>
--
View this message in con
ext:
http://www.nabble.com/Stomp-transactions-tp23354832p23354832.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
