You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Albert Strasheim (JIRA)" <ji...@apache.org> on 2007/06/16 00:56:32 UTC
[jira] Created: (AMQCPP-132) Unsubscribe of durable subscription
fails
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.
[jira] Updated: (AMQCPP-132) Unsubscribe of durable subscription
fails
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-132:
--------------------------------
Fix Version/s: 2.1
Assignee: Timothy Bish (was: Nathan Mittler)
> 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: Timothy Bish
> Fix For: 2.1
>
> 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.
[jira] Commented: (AMQCPP-132) Unsubscribe of durable subscription
fails
Posted by "Timothy Bish (JIRA)" <ji...@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.
[jira] Commented: (AMQCPP-132) Unsubscribe of durable subscription
fails
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39430 ]
Timothy Bish commented on AMQCPP-132:
-------------------------------------
For some reason the RemoveSubscriptionInfo command's ID_REMOVESUBSCRIPTIONINFO keeps getting generated as 0 instead of 9 as it should be when I make it 9, everything works just fine. Also it looks like the dotnet client also has this same issue, its ID for RemoveSubscriptionInfo is also 0.
> 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: Timothy Bish
> Fix For: 2.1
>
> 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.
[jira] Resolved: (AMQCPP-132) Unsubscribe of durable subscription
fails
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-132.
---------------------------------
Resolution: Fixed
fixed in trunk
> 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: Timothy Bish
> Fix For: 2.1
>
> 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.