[
https://issues.apache.org/jira/browse/AMQ-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3476.
-----------------------------
Resolution: Cannot Reproduce
The Stomp v1.1 tests have a case that sends the same CONNECT header and waits
for the broker to close the connection which it does. If you can provide a
test case that shows an issue please reopen and attach it.
> Stomp 1.1 - messages sent after heart-beat timeout are lost
> -----------------------------------------------------------
>
> Key: AMQ-3476
> URL: https://issues.apache.org/jira/browse/AMQ-3476
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.6.0
> Environment: Windows Vista SP 2, Apache ActiveMQ 5.6 Snapshot
> 2011-08-24
> Reporter: Michael Justin
> Labels: stomp
>
> A Stomp 1.1 can send messages after the timeout specified in the heart-beat
> header and these messages will not be rejected. They will also not be visible
> in the admin console so it appears as if they are lost.
> Example:
> client sends:
> CONNECT
> accept-version:1.1
> server:localhost
> heart-beat:1000,0
> received:
> CONNECTED
> heart-beat:0,2000
> session:ID:mj-PC-49595-1314256305896-2:24
> server:ActiveMQ/5.6-SNAPSHOT
> version:1.1
> - here the client waits for about 5 seconds -
> client sends a message:
> SEND
> destination:/queue/TOOL.DEFAULT
> This should fail but the socket connection is still usable for outgoing data.
> Reading from the connection however fails as expected if the client did not
> sent any heart beat signals, so this problem seems to happen only for inbound
> data (from client to server).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
