Seems a lot of the problems is because of logging. The SocketHubAppender causes
the most of the problems.
A lot of threads is waiting for a lock:
| http-0.0.0.0-8080-53 daemon prio=1 tid=0x671b8858 nid=0x5cf1 waiting for
monitor entry [0x5ff97000..0x5ff98670]
| at
Sorry, already can't. It was time-critical for us. Moved to the Windows OS,
problem disapperied. Propably it was the problem of using 64-bit FreeBSD and
32-bit Java, seems an threads using specific problem.
View the original post :
Can you get a stack trace?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3941079#3941079
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3941079
---
Using Tomcat but need
We have exactly the same problem. The only difference that we are using FreeBSD
6.0-STABLE,I386 and Java version 1.4.2-p7.
The problem occurs exactly in the same way. When high loading, after some time
app hangs (no activity of Java and DB server, 100% idle) and app do not
response at all. We
