activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Justin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3476) Stomp 1.1 - messages sent after heart-beat timeout are lost
Date Sun, 28 Aug 2011 15:12:37 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092499#comment-13092499
] 

Michael Justin commented on AMQ-3476:
-------------------------------------

I will try to write a testcase however with the current test cases I run into a build error,
using maven 3 and this command line from the activemq-core folder:

mvn test -Dtest=org.apache.activemq.transport.stomp.Stomp11Test.java

Result:

Running org.apache.activemq.transport.stomp.Stomp11Test
Tests run: 15, Failures: 0, Errors: 15, Skipped: 0, Time elapsed: 3.042 sec <<<
FAILURE!

Results :

Tests in error:
  testConnect(org.apache.activemq.transport.stomp.Stomp11Test): Error creating b
ean with name 'org.apache.activemq.xbean.XBeanBrokerService#0' defined in class
path resource [org/apache/activemq/transport/stomp/stomp-auth-broker.xml]: Insta
ntiation of bean failed; nested exception is java.lang.ExceptionInInitializerErr
or
(... many similar messages)

Are additional configuration parameters necessary to run the tests?

Many thanks in advance

> 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

        

Mime
View raw message