activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3991) Output version number in started log line to be consistent
Date Wed, 05 Sep 2012 22:24:08 GMT

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

Timothy Bish resolved AMQ-3991.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.7.0

Fix applied in trunk, should output a consistent message now for these cases.
                
> Output version number in started log line to be consistent
> ----------------------------------------------------------
>
>                 Key: AMQ-3991
>                 URL: https://issues.apache.org/jira/browse/AMQ-3991
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.6.0
>            Reporter: Claus Ibsen
>            Priority: Trivial
>             Fix For: 5.7.0
>
>
> AMQ logs when its starting, and later when it has started. Only the 1st log line has
the version number. It would be good to have the version number in the 2nd line as well.
> {code}
> [                          main] BrokerService                  INFO  ActiveMQ 5.6.0
JMS Message Broker (mybroker) is starting
> [                          main] BrokerService                  INFO  For help or more
information please see: http://activemq.apache.org/
> [                 JMX connector] ManagementContext              INFO  JMX consoles can
connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
> [                          main] TransportServerThreadSupport   INFO  Listening for connections
at: tcp://127.0.0.1:61616
> [                          main] TransportConnector             INFO  Connector tcp://localhost:61616
Started
> [                          main] BrokerService                  INFO  ActiveMQ JMS Message
Broker (mybroker, ID:davsclaus.lan-54124-1345820752143-0:1) started
> {code}
> And for stopping the broker the version number is no longer included. That would be good
to have, to be consistent.
> {code}
> [         ActiveMQ ShutdownHook] BrokerService                  INFO  ActiveMQ Message
Broker (mybroker, ID:davsclaus.lan-54124-1345820752143-0:1) is shutting down
> [cp://localhost/127.0.0.1:61616] FailoverTransport              WARN  Transport (tcp://127.0.0.1:61616)
failed, reason:  java.io.EOFException, attempting to automatically reconnect
> [cp://localhost/127.0.0.1:61616] FailoverTransport              WARN  Transport (tcp://127.0.0.1:61616)
failed, reason:  java.io.EOFException, attempting to automatically reconnect
> [cp://localhost/127.0.0.1:61616] FailoverTransport              WARN  Transport (tcp://127.0.0.1:61616)
failed, reason:  java.io.EOFException, attempting to automatically reconnect
> [cp://localhost/127.0.0.1:61616] FailoverTransport              WARN  Transport (tcp://127.0.0.1:61616)
failed, reason:  java.io.EOFException, attempting to automatically reconnect
> [         ActiveMQ ShutdownHook] TransportConnector             INFO  Connector tcp://localhost:61616
Stopped
> [cp://localhost/127.0.0.1:61616] FailoverTransport              WARN  Transport (tcp://127.0.0.1:61616)
failed, reason:  java.io.EOFException, attempting to automatically reconnect
> [         ActiveMQ ShutdownHook] BrokerService                  INFO  ActiveMQ JMS Message
Broker (mybroker, ID:davsclaus.lan-54124-1345820752143-0:1) stopped
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message