activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] Commented: (AMQNET-138) Unable to select STOMP protocol
Date Thu, 05 Feb 2009 21:35:59 GMT


Jim Gomes commented on AMQNET-138:

Tim, your suggestion is a good one, and fortunately is already implemented.  The wireformat
parameter has been there for a while, and it defaults to OpenWire.  Having the *stomp:* prefix
was just a syntactical shortcut.  However, your logic shows that it isn't really good syntax.
 I would vote then, that the method for *stomp://localhost:61613* be done away with in favor
of *tcp://localhost:61613?transport.wireFormat=stomp*  syntax (or for complete specification:

While it is a bit verbose compared to the previous syntax, it will work better in almost all
situations, especially in a failover situation.  For example:


This would obviate the need for the additional *nmsprovider-stomp.config* file.  This is a
breaking change, though, so documentation will need to be updated to alert the users of the
need to change their URIs.

> Unable to select STOMP protocol
> -------------------------------
>                 Key: AMQNET-138
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>    Affects Versions: 1.1
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>             Fix For: 1.1
>         Attachments: AMQNET-138-741292.diff
> User reported issue with using the STOMP protocol due to recent changes made to NMS.
 See the following Nabble conversation for details:
> When we went to actually connect to our server (stomp:// or whatnot,
same as always), we get the following errors:
> 19/01/2009 1:36:08 PM WRN Transmitter.Setup:: The transport stomp is not supported.
>    at Apache.NMS.ActiveMQ.Transport.TransportFactory.AddTransportFactory(String scheme)
>    at Apache.NMS.ActiveMQ.Transport.TransportFactory.findTransportFactory(Uri location)
>    at Apache.NMS.ActiveMQ.ConnectionFactory.CreateConnection(String userName, String
>    at FAInterface.Transmitter.Setup_R()
> This seems to be a client code issue as if we use our old DLL we can connect to both
4.1 and 5.2 brokers.  What are we missing? 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message