[jboss-user] [JBoss Messaging] - Re: Removing a MessageListener doesn't remove its associated

[davidrh]

I've gone back to not closing and re-opening the sessions with the CR3 build, and I'm back to the problem of the message listeners not all receiving messages.  I've done a thread dump, and the listener threads are as follows:


  | "Manager core.track.1.0" prio=1 tid=0x08694a20 nid=0x2730 in Object.wait() [0x847f9000..0x847f9228]
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x950329e0> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:429)
  |         at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(Unknown Source)
  |         - locked <0x950329e0> (a java.lang.Object)
  |         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
  |         at java.lang.Thread.run(Thread.java:534)
  | 
  | "Manager core.track.1.1" prio=1 tid=0x08698b28 nid=0x2730 in Object.wait() [0x84676000..0x84676228]
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x95098dc0> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:429)
  |         at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(Unknown Source)
  |         - locked <0x95098dc0> (a java.lang.Object)
  |         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
  |         at java.lang.Thread.run(Thread.java:534)
  | 
  | "Manager core.track.1.2" prio=1 tid=0x091246e8 nid=0x2730 in Object.wait() [0x84157000..0x84157228]
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x9511ec68> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:429)
  |         at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(Unknown Source)
  |         - locked <0x9511ec68> (a java.lang.Object)
  |         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
  |         at java.lang.Thread.run(Thread.java:534)
  | 
  | "Manager core.track.1.3" prio=1 tid=0x08d14530 nid=0x2730 in Object.wait() [0x83f53000..0x83f53228]
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x95101ae0> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:429)
  |         at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(Unknown Source)
  |         - locked <0x95101ae0> (a java.lang.Object)
  |         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
  |         at java.lang.Thread.run(Thread.java:534)
  | 
  | "Manager core.track.1.4" prio=1 tid=0x08d13ec8 nid=0x2730 in Object.wait() [0x83e51000..0x83e51228]
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x951eab10> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:429)
  |         at EDU.oswego.cs.dl.util.concurrent.LinkedQueue.take(Unknown Source)
  |         - locked <0x951eab10> (a java.lang.Object)
  |         at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(Unknown Source)
  |         at java.lang.Thread.run(Thread.java:534)
  | 

Manager core.track.1.0 is the only thread still processing messages, but I think the above shows the listeners aren't stuck somewhere in our code. I am trying to reproduce this in a test harness but have so far been unsuccessful.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962052#3962052

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962052