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 20:17:59 GMT


Timothy Bish commented on AMQNET-138:

I think a better solution for this would be to break out the definition of the Wire Format
from the Transport.  Stomp is a wire format, tcp is the transport.  In the C++ client we use
a URI option to override the default wire format which is OpenWire, the Java client does something

So instead of using stomp:// or whatever we use tcp://
this way the the transport that is being used is unambiguous as is the wireFormat.  

> 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