We just saw the same problem occur this week, on the same server at the same time. We
are running 44 nodes so its likely that the problem is environmental i.e O/S,
hardware, etc.
Anyway, thanks for your time. Will upgrade soon nevertheless.
Re: your advice...you're preaching to the converted
Because I made some fixes in this area.
Additionally, you'll find you won't get much help unless you can reproduce the problem
with the latest stable release. Nobody wants to waste time analyzing problems that
have already been fixed.
Off Topic, advice:
If you cannot reproduce a production
Thanks for the tip.
We're only able to reproduce this problem in production. Consequently, there has to be
a reason to upgrade more substantial than just giving 3.2.5 a try.
We are currently running 3.2.3 (Jetty). Why would 3.2.5 fix it? Is there a specific
change to the TimeoutFactory in the
Try to reproduce it with 3.2.5:
http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-common/src/main/org/jboss/util/timeout/TimeoutFactory.java?rev=1.2view=log
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3845929#3845929
Reply to the post :
