Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 11408 invoked from network); 16 Jun 2007 13:09:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Jun 2007 13:09:54 -0000 Received: (qmail 65136 invoked by uid 500); 16 Jun 2007 13:09:57 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 65103 invoked by uid 500); 16 Jun 2007 13:09:57 -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 65094 invoked by uid 99); 16 Jun 2007 13:09:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jun 2007 06:09:57 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Jun 2007 06:09:53 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 05F037141EC for ; Sat, 16 Jun 2007 06:09:33 -0700 (PDT) Message-ID: <27604494.1181999373019.JavaMail.jira@brutus> Date: Sat, 16 Jun 2007 06:09:33 -0700 (PDT) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQCPP-132) Unsubscribe of durable subscription fails In-Reply-To: <23381344.1181948192845.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQCPP-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39429 ] Timothy Bish commented on AMQCPP-132: ------------------------------------- See the stomp protocol spec. http://stomp.codehaus.org/Protocol > Unsubscribe of durable subscription fails > ----------------------------------------- > > Key: AMQCPP-132 > URL: https://issues.apache.org/activemq/browse/AMQCPP-132 > Project: ActiveMQ C++ Client > Issue Type: Bug > Components: Openwire > Affects Versions: 2.1 > Reporter: Albert Strasheim > Assignee: Nathan Mittler > Attachments: owdurableunsub.patch > > > Calling unsubscribe on an Openwire session fails. The C++ application throws the following exception: > response from futureResponse was invalid > FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LINE: 146 > FILE: ..\src\main\activemq\transport\filters\ResponseCorrelator.cpp, LINE: 153 > FILE: ..\src\main\activemq\connector\openwire\OpenWireFormatNegotiator.cpp, LINE: 105 > FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LINE: 1468 > FILE: ..\src\main\activemq\connector\openwire\OpenWireConnector.cpp, LINE: 1250 > FILE: ..\src\main\activemq\core\ActiveMQSession.cpp, LINE: 788 > On a recent ActiveMQ 5.0-SNAPSHOT broker the following is printed in the console: > Exception in thread "ActiveMQ Transport: tcp:///127.0.0.1:1900" java.lang.OutOfMemoryError: Java heap space > at org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.looseUnmarshalByteSequence(BaseDataStreamMarshaller.java:599) > at org.apache.activemq.openwire.v2.WireFormatInfoMarshaller.looseUnmarshal(WireFormatInfoMarshaller.java:132) > at org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:351) > at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:275) > at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156) > at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136) > at java.lang.Thread.run(Thread.java:619) > A patch for the Openwire durable subscribe integration test is attached to perform an unsubscribe when everything is done. This reproduces the problem. > In a related matter, why is unsubscribe not supported for Stomp? Is it due to a protocol limitation? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.