You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/10/11 11:35:41 UTC

[jira] [Created] (AMQ-4799) Starting AMQ standalone - ws connector url/port not logged

Claus Ibsen created AMQ-4799:
--------------------------------

             Summary: Starting AMQ standalone - ws connector url/port not logged
                 Key: AMQ-4799
                 URL: https://issues.apache.org/jira/browse/AMQ-4799
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Broker
            Reporter: Claus Ibsen
            Priority: Minor
             Fix For: 5.9.0


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



--
This message was sent by Atlassian JIRA
(v6.1#6144)