You'll have to define bad. Is this a msg that cannot be processed or what?
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.
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?
If not, use "READ THIS FIRST" to provide some usable information.
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!