You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Andreas Ländle (JIRA)" <ji...@apache.org> on 2012/05/22 14:12:42 UTC
[jira] [Created] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
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
[jira] [Commented] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294497#comment-13294497 ]
Timothy Bish commented on AMQNET-384:
-------------------------------------
Added a note on the fact that these are yet supported to the docs page.
> 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
[jira] [Commented] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Andreas Ländle (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-384:
--------------------------------
Fix Version/s: 1.6.0
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-384.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5.3
Assignee: Timothy Bish (was: Jim Gomes)
This is now resolved on trunk.
> 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
>
>
> 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
[jira] [Commented] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281181#comment-13281181 ]
Timothy Bish commented on AMQNET-384:
-------------------------------------
We welcome any patches or NUnit test cases you care to contribute.
> 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
[jira] [Commented] (AMQNET-384) Configuration of wireFormat via URL
doesn't work
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431509#comment-13431509 ]
Timothy Bish commented on AMQNET-384:
-------------------------------------
Added an initial fix for this on trunk for 1.6.0. Needs some testing and probably a few tweaks before back-porting to v1.5.x branch.
> 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