Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-4799

Starting AMQ standalone - ws connector url/port not logged

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.9.0
    • Component/s: Broker
    • Labels:
      None

      Description

      Hi

      When starting the broker in standalone mode, we have a number of
      transports out of the box.

      As you can see for openwire, stomp, and mqtt, we also log listening
      for connections at ....

      But for WS we do not do that. It would probably be nice if we could do
      that as well, so people can see the urls / ports in use.

      is there a reason why ws doesn't do that?

      INFO | Listening for connections at:
      tcp://davsclaus.air:61616?maximumConnections=1000&wireFormat.maxFrameSize=104857600
      INFO | Connector openwire started
      INFO | Listening for connections at:
      amqp://davsclaus.air:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600
      INFO | Connector amqp started
      INFO | Listening for connections at:
      stomp://davsclaus.air:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600
      INFO | Connector stomp started
      INFO | Listening for connections at:
      mqtt://davsclaus.air:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600
      INFO | Connector mqtt started
      INFO | Connector ws started

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              davsclaus Claus Ibsen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: