This discussion is archived
2 Replies Latest reply: Oct 22, 2013 12:31 PM by ak RSS

JMS warnings connecting to a Glassfish broker.

joguerra Newbie
Currently Being Moderated
Hi,
I got this warnings when i attempt to connect with a JMS broker on Glassfish v3. Does anyone idea how to get rid of this warning?.

I am not sure whether the problem is related to the issue described on this link: http://docs.sun.com/app/docs/doc/821-1073/aembi?l=en&a=view

Cheers

Oct 4, 2010 2:37:21 PM com.sun.enterprise.transaction.JavaEETransactionManagerSimplified initDelegates
INFO: Using com.sun.enterprise.transaction.jts.JavaEETransactionManagerJTSDelegate as the delegate
Oct 4, 2010 2:37:25 PM com.sun.enterprise.connectors.jms.util.JmsRaUtil getInstalledMqVersion
WARNING: jmsra.upgrade_check_failed
Oct 4, 2010 2:37:25 PM org.hibernate.validator.util.Version <clinit>
INFO: Hibernate Validator bean-validator-3.0-JBoss-4.0.2
Oct 4, 2010 2:37:25 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
Oct 4, 2010 2:37:25 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: SJSMQ JMSRA Started:REMOTE
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:26 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:27 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
Oct 4, 2010 2:37:27 PM com.sun.messaging.jmq.jmsclient.ExceptionHandler logCaughtException
WARNING: [I500]: Caught JVM Exception: com.sun.messaging.jms.JMSException: [HELLO_REPLY(11)] [C4036]: A broker error occurred. :[505] bad version user=guest, broker=localhost:7676(42589)
  • 1. Re: JMS warnings connecting to a Glassfish broker.
    nigeldeakin Explorer
    Currently Being Moderated
    What version of the Glassfish MQ broker are you running? If it is older than Glassfish v3 you will see messages like this.

    The message is really just a debug message, produced when the client connects to the broker. The messages are logged as as part of the standard negotiation between the MQ client and the MQ broker during which they decide decide what protocol level they should use for communications. Unfortunately it is logged as a warning, which is inappropriate.

    You can't supress these messages without disabling warning messages, which I would not recommend.

    This annoys me too. I'll see what I can do to get this fixed in Glassfish 3.1.

    Nigel
    Glassfish team
  • 2. Re: JMS warnings connecting to a Glassfish broker.
    ak Explorer
    Currently Being Moderated

    The warning log message "[C4036]: A broker error occurred. :[505] bad version .." is fixed in GlassFish  MQ 4.5 (GlassFish 3.1)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points