[
https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450445#comment-13450445
]
Andreas Ländle commented on AMQNET-384:
---------------------------------------
Thanks for providing a fix - just to avoid confusion for other users encounter
the same problem - as far as I can see this wasn't backported to the v1.5.x
branch - so the released v1.5.3 doesn't contain the fix - but of course it is
very simple to merge this yourself.
> Configuration of wireFormat via URL doesn't work
> ------------------------------------------------
>
> Key: AMQNET-384
> URL: https://issues.apache.org/jira/browse/AMQNET-384
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Reporter: Andreas Ländle
> Assignee: Timothy Bish
> Fix For: 1.5.3, 1.6.0
>
>
> The configuration of the STOMP wireformat doesn't work as described here:
> http://activemq.apache.org/nms/stomp-uri-configuration.html
> (btw: there is a type 'wireFormat.maxInactivityDurationInitalDelay' - the
> second 'i' in 'Inital' is missing).
> If you take a look in TcpTransportFactory.cs lines 118-120 it's obvious - the
> class StompWireFormat simple has no fields/properties named
> 'maxInactivityDuration' or 'maxInactivityDurationInitialDelay'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
