activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio
Date Thu, 28 Jun 2012 22:26:44 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish resolved AMQ-3897.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0
         Assignee: Timothy Bish

Fixed in trunk.  
                
> Stomp 1.1 keep alive does not work with stomp+nio
> -------------------------------------------------
>
>                 Key: AMQ-3897
>                 URL: https://issues.apache.org/jira/browse/AMQ-3897
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, stomp
>    Affects Versions: 5.6.0
>         Environment: centos 6, OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>            Reporter: R.I.Pienaar
>            Assignee: Timothy Bish
>             Fix For: 5.7.0
>
>
> using the transport:
> {quote}
>   <transportConnector name="stomp+nio" uri="stomp+nio://0.0.0.0:6163"/>
> {quote}
> When connecting a stomp 1.1 client I see this using tcpdump (tcpdump output so new lines
etc):
> {quote}
> send...>
> CONNECT
> .passcode:xxx.host:kvm4.content-length:0.heart-beat:30000,30000.content-type:text/plain;
charset=UTF-8.login:rip.accept-version:1.1,1.0...
> <...receive
> CONNECTED.heart-beat:0,0.session:ID:kvm4-55239-1340217683781-3:10008.server:ActiveMQ/5.6.0.version:1.1....
> {quote}
> Notice that I send the heart-beat header requesting 30000,30000 heartbeats but then ActiveMQ
replies with 0,0
> If I change the stomp transport to stomp and not stomp+nio and not changing my code or
what I send in CONNECT request I get the correct heartbeats.
> It seems stomp+nio does not have heartbeat support for protocol 1.1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message