Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.1.0
    • 1.1.0
    • ActiveMQ
    • None
    • Regression

    Description

      User reported issue with using the STOMP protocol due to recent changes made to NMS. See the following Nabble conversation for details:

      http://www.nabble.com/Changes-to-C--client-in-5.2---Can%27t-connect-via-STOMP...-td21549608.html

      When we went to actually connect to our server (stomp://192.168.0.1:61616 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 password)
      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?

      Attachments

        Activity

          People

            jgomes Jim Gomes
            jgomes Jim Gomes
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: