How to suppress JMS connection messages?

[askdolphin]

Dear All,

Is there any way to suppress the JMS connection messages as follows? I
don't want the console to display these messages.

May 15, 2008 9:55:58 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
May 15, 2008 9:55:59 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:REMOTE
May 15, 2008 9:55:59 PM
com.sun.messaging.jms.ra.ManagedConnectionFactory setAddressList
INFO: MQJMSRA_MF1101: setAddressList:NOT setting default
value=localhost
May 15, 2008 9:55:59 PM
com.sun.messaging.jms.ra.ManagedConnectionFactory setPassword
INFO: MQJMSRA_MF1101: setPassword:NOT setting default value
May 15, 2008 9:55:59 PM
com.sun.messaging.jms.ra.ManagedConnectionFactory setUserName
INFO: MQJMSRA_MF1101: setUserName:NOT setting default value=guest
May 15, 2008 9:56:00 PM com.sun.messaging.jms.ra.ManagedConnection
<init>
INFO: MQJMSRA_MC1101: constructor:Created
mcId=1:xacId=4631136308923212288:Using xacf
config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000,
imqOverrideJMSExpiration=false, imqAddressListIterations=3,
imqLoadMaxToServerSession=true, imqConnectionType=TCP,
imqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=,
imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider,
imqJMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000,
imqConnectionURL=http://localhost/imq/tunnel, imqBrokerServiceName=,
imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpiration=0,
imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0,
imqAckOnAcknowledge=, imqConsumerFlowThreshold=50,
imqDefaultPassword=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000,
imqDefaultUsername=guest, imqReconnectEnabled=true,
imqConnectionFlowCount=100, imqAddressListBehavior=RANDOM,
imqReconnectAttempts=3, imqSetJMSXAppID=false,
imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler,
imqSetJMSXRcvTimestamp=false, imqBrokerServicePort=0,
imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false,
imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676,
imqQueueBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false,
imqSSLIsHostTrusted=false, imqConnectionFlowLimitEnabled=false,
imqReconnectInterval=5000, imqAddressList=mq://abaco.labs.mot.com:
7676/, imqOverrideJMSHeadersToTemporaryDestinations=false}

Thanks for your help!

Dolphin

 

[Ajay]

Dear All,

Is there any way to suppress the JMS connection messages as follows? I
don't want the console to display these messages.

Set the log level for "com.sun.*" to ERROR.

HTH

Ajay

 

[askdolphin]

Sorry, it doesn't work. These are not error messages. They are just
some "INFO." It doesn't work either when the log level is set to "ALL"

Please advice!!

Thanks!!!

 

[Owen Jacobson]

Sorry, it doesn't work. These are not error messages. They are just
some "INFO." It doesn't work either when the log level is set to "ALL"

Please advice!!

Thanks!!!

The way logging works in this context is that each log event is a
pair:

(Priority, Message)

The category also has a priority. Any pair whose priority is less
than the category's priority is suppressed; all others are logged.

In this case, ALL is the *lowest* priority (all priorities are higher
than ALL, so no messages will be suppressed). If you want to turn off
INFO for a given category, you must set that category's priority to
something higher than INFO -- WARN is a good value; it's the next
priority up from INFO.

Note that the priority levels -- INFO, ALL, ERROR, WARN, etc -- do not
necessarily mean that the message is an error! It's traditional to
use the priorities as labelled, but ultimately they are just levels of
detail.

-o

 

[askdolphin]

Thank you so much for the info. However, it still doesn't work. I
tried:

Logger.getLogger( "com.sun.*").setLevel( Level.SEVERE);

The INFO messages still shows up when it reaches to Context.lookup()

 

[Arne Vajhøj]

Thank you so much for the info. However, it still doesn't work. I
tried:

Logger.getLogger( "com.sun.*").setLevel( Level.SEVERE);

The INFO messages still shows up when it reaches to Context.lookup()

Logger.getLogger("com.sun").setLevel(Level.SEVERE);

looks more correct to my eyes.

Arne

 

[askdolphin]

Sorry, still not working :-(

Logger.getLogger("com.sun").setLevel(Level.SEVERE);

looks more correct to my eyes.

Arne