4 Replies Latest reply on Mar 15, 2005 1:47 PM by dmorris1238

    Bad JMS Object stuck in queue

    dmorris1238

      We are using JBoss 3.2.2 in a production environment on a Dell server using MS-SQL as the JMS DB. The problem we run across occasionally is that a 'bad' JMS message object gets stuck in the queue. We notice that we have a 'bad' JMS object because the queue size starts building up. To fix the issue, we have to stop JBoss. Go into MS-SQL, clear the top message (or messages) in JMS_MESSAGES table for a particular queue and restart JBoss. The issue is 'fixed' when we notice that the JMS objects in the queue are being consumed.

      The question is:

      Is there an easier way to delete a 'bad' message object from the JBoss queue without having to do the above steps?


      Thanks!

        • 1. Re: Bad JMS Object stuck in queue
          starksm64

          You'll have to define bad. Is this a msg that cannot be processed or what?

          • 2. Re: Bad JMS Object stuck in queue
            dmorris1238

            The object cannot be processed in JBoss. The first 'bad' object prevents further queue processing. The queue will continue adding objects. However, the queue listener does not continue processing. In other words, the queue size continues to grow.

            I think the 'bad' queue object gets corrupted somehow before it is put on the queue.

            Thanks!

            • 3. Re: Bad JMS Object stuck in queue

              All you did was repeat your first comment, which falls into the category:

              "I think this is what is happening, but I haven't verified my assumption.
              I'm not going to provide some usefult information that would enable you to
              verify my assumption but I want you to help me anyway"

              You are probably referring to this?
              http://jira.jboss.com/jira/browse/JBAS-1489

              If not, use "READ THIS FIRST" to provide some usable information.

              • 4. Re: Bad JMS Object stuck in queue
                dmorris1238

                The problem guys was that we were not getting any exceptions thrown in 3.2.2 on the JBoss Server or on the client listener. So I could only report the 'symptoms'. There was no exception reporting.

                I'll advise our client to 'upgrade' to 3.2.7 Final version.

                Thanks Scott & Adrian for your assistance!