Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A1D99D03 for ; Fri, 22 Jun 2012 20:19:43 +0000 (UTC) Received: (qmail 73687 invoked by uid 500); 22 Jun 2012 20:19:43 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 73650 invoked by uid 500); 22 Jun 2012 20:19:43 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 73632 invoked by uid 99); 22 Jun 2012 20:19:43 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jun 2012 20:19:43 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 2F07414001F for ; Fri, 22 Jun 2012 20:19:43 +0000 (UTC) Date: Fri, 22 Jun 2012 20:19:43 +0000 (UTC) From: "R.I.Pienaar (JIRA)" To: dev@activemq.apache.org Message-ID: <2128940789.45243.1340396383194.JavaMail.jiratomcat@issues-vm> In-Reply-To: <420988649.45240.1340396382551.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Updated] (AMQ-3897) Stomp 1.1 keep alive does not work with stomp+nio MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] R.I.Pienaar updated AMQ-3897: ----------------------------- Description: using the transport: {quote} {quote} When connecting a stomp 1.1 client I see this using tcpdump: {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 was: using the transport:
   
When connecting a stomp 1.1 client I see this using tcpdump:
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....
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 > 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 > > using the transport: > {quote} > > {quote} > When connecting a stomp 1.1 client I see this using tcpdump: > {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