[jboss-dev-forums] [Design of POJO Server] - Re: Strange classloading behavior -- thread stuck

[bstansberry@jboss.com]

"adrian at jboss.org" wrote : 
  | So the issue is to try to figure out how that could happen.
  | 
  | If you know how to reproduce the problem, enabling TRACE logging
  | for org.jboss.classloader would help greatly. ;-)

Bela seems able to reproduce easily enough; I've asked him to add TRACE logging.

He sent me another message this AM with a bunch of stack traces from the problem thread. All showed the thread in different places inside the while (taskList.isEmpty() == false) loop.

anonymous wrote : 
  | I don't think your second guess is correct? The one about the remove
  | being outside the synchronized block. The code is the same as JBoss4.x

That was more something I noticed that just looked wrong in general -- mutating an unguarded object. If it caused a problem though I'd expect it to be an IndexOutOfBoundsException because a thread lost a race to remove the last item.

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

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