activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Davies <rajdav...@gmail.com>
Subject Re: Starting AMQ standalone - ws connector url/port not logged
Date Fri, 11 Oct 2013 09:21:49 GMT
we should do that for ws too (if possible)

On 11 Oct 2013, at 10:10, Claus Ibsen <claus.ibsen@gmail.com> wrote:

> 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
> 
> 
> -- 
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen


Mime
View raw message