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

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-4799:
----------------------------

    Fix Version/s:     (was: 5.10.0)
                   5.9.0

> 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
>            Assignee: 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)