[
https://issues.apache.org/jira/browse/AMQ-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sargis Harutyunyan updated AMQ-3263:
------------------------------------
Attachment: logging_session_events.patch
> ActiveMQ LoggingBrokerPlugin too verbose
> ----------------------------------------
>
> Key: AMQ-3263
> URL: https://issues.apache.org/jira/browse/AMQ-3263
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.4.2
> Environment: sargis@sargis:~> uname -a
> Linux sargis.webbfontaine.am 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21
> 10:34:10 +0100 i686 i686 i386 GNU/Linux
> sargis@sargis:~> java -version
> java version "1.6.0_24"
> Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
> Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)
> ActiveMQ 5.4.2-fuse-02-00
> Reporter: Sargis Harutyunyan
> Attachments: logging_session_events.patch
>
>
> Hi all, I am using Apache ActiveMQ v5.4.2-fuse-02-00 and I want to log events
> related connections and added following line into my config
> <loggingBrokerPlugin logAll="false" logConnectionEvents="true"/>
> but I now in my log I have a lot of noise because its enabled also events
> related to sessions. I've prepared patch to add additional flag
> 'logSessionEvents' to have more control what to log. Here is pull request
> URL: https://github.com/apache/activemq/pull/1 and here is log snippet.
> 2011-03-23 12:58:55,861 | INFO | Adding Connection : ConnectionInfo
> {commandId = 1, responseRequired = true, connectionId =
> ID:comunalserver-3451-634364032937500000-1:1141, clientId =
> ID:comunalserver-3451-634364032937500000-1142:0, userName = epaybroker,
> password = *****, brokerPath = null, brokerMasterConnector = false,
> manageable = false, clientMaster = false, faultTolerant = false} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///81.89.210.236:2972
> 2011-03-23 12:58:55,903 | INFO | Adding Session : SessionInfo {commandId = 2,
> responseRequired = false, sessionId =
> ID:comunalserver-3451-634364032937500000-1:1141:1} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///81.89.210.236:2972
> 2011-03-23 12:58:56,517 | INFO | Removing Session : SessionInfo {commandId =
> 71563, responseRequired = false, sessionId =
> ID:test.customs.am-28506-1300862663044-0:2:15904} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///192.168.0.30:21258
> 2011-03-23 12:58:56,517 | INFO | Removing Session : SessionInfo {commandId =
> 71572, responseRequired = false, sessionId =
> ID:test.customs.am-28506-1300862663044-0:3:15906} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///192.168.0.30:21259
> 2011-03-23 12:58:56,518 | INFO | Adding Session : SessionInfo {commandId =
> 71570, responseRequired = false, sessionId =
> ID:test.customs.am-28506-1300862663044-0:2:15905} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///192.168.0.30:21258
> 2011-03-23 12:58:56,518 | INFO | Removing Session : SessionInfo {commandId =
> 71570, responseRequired = false, sessionId =
> ID:test.customs.am-28506-1300862663044-0:2:15905} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///192.168.0.30:21258
> 2011-03-23 12:58:56,518 | INFO | Adding Session : SessionInfo {commandId =
> 71572, responseRequired = false, sessionId =
> ID:test.customs.am-28506-1300862663044-0:2:15906} |
> org.apache.activemq.broker.util.LoggingBrokerPlugin | ActiveMQ Transport:
> ssl:///192.168.0.30:21258
> ........................
> ........................
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
