7 Replies Latest reply on Apr 6, 2006 12:17 PM by Scott Stark

    JBOSS DLQ Exception

    Peter Rozario Newbie

      Newbee here. I've a question about DLQ. I've a mbean which process message coming from IBM MQ (setup thru JMS), and sent it to DLQ after 15 retries. It works fine when the message is coming from a standalone java app into mq. But when it comes thru outside clients (using RPG to put message into MQ), we get following exceptions. Something about the message that the DLQHandler doesn't like. We are using ver 3.2.3. Any suggestions would be greatly appreciated.

      >>> jboss log file .>>>>>
      Message resent too many times; sending it to DLQ; message id=ID:c1d4d840d5d1c7c9c4d4404040404040423e67f8200e700b
      Exception in JMSCI message listener
      java.lang.NullPointerException
      at org.jboss.ejb.plugins.jms.DLQHandler.sendMessage(DLQHandler.java:279)
      at org.jboss.ejb.plugins.jms.DLQHandler.handleRedeliveredMessage(DLQHandler.java:233)
      at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:110
      5)
      at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
      at com.ibm.mq.jms.MQSession.run(MQSession.java:1136)
      at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
      at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
      at java.lang.Thread.run(Thread.java:534)

        • 1. Re: JBOSS DLQ Exception
          Adrian Brock Master

          Moderated: Suck it and see.

          Or in the alternative read the release notes, where you can find the version
          where this WSMQ bug has workaround.

          • 2. Re: JBOSS DLQ Exception
            Peter Rozario Newbie

            can you give little more info ... i looked for release notes, but can't find anything releated to the workaround you're talking about (or perhaps i didn't look in the right place). A link would be helpful

            • 3. Re: JBOSS DLQ Exception
              Neil Belford Newbie

              Mr Brock,

              We are getting the same error. Have you forgotten something from 2 years ago?


              quote ...

              Category: JBossMQ
              Group: v3.2
              Status: Open
              Resolution: None
              Priority: 5
              Submitted By: Elias Ross (genman)
              >Assigned to: Elias Ross (genman)
              Summary: NullPointerException in DLQHandler

              Initial Comment:

              Stack trace:

              2003-10-07 14:17:19,845 ERROR [JMSContainerInvoker]
              (Thread Pool Worker-9921) Exception in JMSCI message
              listener
              java.lang.NullPointerException
              at java.util.Hashtable.put(Hashtable.java:386)
              org.jboss.ejb.plugins.jms.DLQHandler.makeWritable(DLQHandler.java:288)
              org.jboss.ejb.plugins.jms.DLQHandler.sendMessage(DLQHandler.java:239)
              org.jboss.ejb.plugins.jms.DLQHandler.handleRedeliveredMessage(DLQHandler.java:213)
              org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerInvoker.java:1039)
              org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
              org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:633)
              org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:433)
              org.jboss.mq.SpySession.run(SpySession.java:298)
              org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
              EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:732)
              at java.lang.Thread.run(Thread.java:536)

              (Hashtable does not allow null values, which seems to
              be the cause of this exception. HashMap could be used
              instead.)

              Probably there is either a null message property
              (SpyMessage does not check for null String values) or
              some sort of race condition as I haven't seen this
              exception before...



              ----------------------------------------------------------------------

              >Comment By: Elias Ross (genman)
              Date: 2003-10-07 14:32

              Message:
              Logged In: YES
              user_id=556458


              I'll fix it -- I still seem to have CVS write access.



              ----------------------------------------------------------------------

              Comment By: Adrian Brock (ejort)
              Date: 2003-10-07 12:14

              Message:
              Logged In: YES
              user_id=9459

              Nulls are allowed according to the spec (String and Object
              properties)
              Elias you have cvs write?
              A HashMap for the temporary copy
              sounds like correct the solution.
              Can you fix it for 3.2.2 release, i.e. before the weekend?
              If not, I'll do it. Don't forget jboss-head

              Regards,
              Adrian
              ... unquote

              Neil Belford

              • 4. Re: JBOSS DLQ Exception
                Neil Belford Newbie

                By the way - we are using version 4.0.1 and the bug remains in the source code

                i.e.


                in org.jboss.ejb.plugins.jms.DLQHandler.java

                /**
                * Make the Message properties writable.
                *
                * @return the writable message.
                */
                protected Message makeWritable(Message msg, boolean trace) throws JMSException
                {
                Hashtable tmp = new Hashtable();
                ...

                • 5. Re: JBOSS DLQ Exception
                  Scott Stark Master

                  It never was ported from 3.2. It has been done for the 4.0.2 release.

                  • 6. Re: JBOSS DLQ Exception
                    Mikl Newbie

                     

                    "scott.stark@jboss.org" wrote:
                    It never was ported from 3.2. It has been done for the 4.0.2 release.

                    What about 4.0.1sp1 ?

                    • 7. Re: JBOSS DLQ Exception
                      Scott Stark Master

                      No, does not look like it.