activemq-dev mailing list archives

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


Timothy Bish commented on AMQNET-138:

What we do on the C++ client is to document our URI configuration details on the Website with
tags on certain parameters for the version they were added or removed.

Probably a good time to add a page similar to that to the NMS site.  

While the syntax of the URI is more verbose it is more explicit about what is being used and
leaves the door open for other transports to be added like SSL for instance without changing
any code that deals with the selection of Wire Formats.

In the C++ code the WireFormat can be created in an Abstract TransportFactory class and all
our other TransportFactory's just inherit from that and get WireFormat creation for free.

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