activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-120) Cached Nested Command Type Encoding Is Broken
Date Mon, 26 Apr 2010 13:01:26 GMT

    [ 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.


Mime
View raw message