activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Ländle (JIRA) <jira+amq...@apache.org>
Subject [jira] [Created] (AMQNET-384) Configuration of wireFormat via URL doesn't work
Date Tue, 22 May 2012 12:12:42 GMT
Andreas Ländle created AMQNET-384:
-------------------------------------

             Summary: 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: Jim Gomes


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message