You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2010/04/26 15:01:26 UTC
[jira] Commented: (AMQNET-120) Cached Nested Command Type Encoding
Is Broken
[ https://issues.apache.org/activemq/browse/AMQNET-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59093#action_59093 ]
Timothy Bish commented on AMQNET-120:
-------------------------------------
I don't think this even works or is enabled in the Broker any more, its probably best to just make the option depricated and ignore it.
> Cached Nested Command Type Encoding Is Broken
> ---------------------------------------------
>
> Key: AMQNET-120
> URL: https://issues.apache.org/activemq/browse/AMQNET-120
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Environment: ActiveMQ 5.2
> Reporter: Jim Gomes
> Assignee: James Strachan
> Priority: Minor
> Fix For: 1.3.0
>
>
> The Cached Nested Command Type Encoding option does not work and causes connection errors when it is turned on. See the relevant section in the OpenWire specification:
> [http://activemq.apache.org/openwire-version-2-specification.html].
> Turning on the option is accomplished with the connection URI parameter as follows:
> activemq:tcp://localhost:61616?connection.CacheEnabled=true
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.