The easiest way to get thread dumps is for one to use JDK 1.5 or above on the
server. Make sure the JDK'x JMX MBean Server is turned on and that you've set
the switches to allow for remote JMX connections..
enable jmx remote switch = -Dcom.sun.management.jmxremote
remote jmx port =
err, I meant, the TDA Plugin, not the JTA plugin.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4136915#4136915
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4136915
___
Looks like you have some queries that are not well formed, or your might be
missing some table indexes. You now need to use some postgresql tools (like
ptop) to determine where the problem is and then fix it.
View the original post :
hi Peter,
Increasing RAM from 1 to 2 GB, now the postgres is taking maximim cpu usage
and resulting in the same old problem of system getting hanged.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4136168#4136168
Reply to the post :
Hi Peter,
The configurations are as follows:
jdk version
java version 1.5.0_08
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing)
postgresql version
PostgreSQL 8.1.4
jboss version
jboss 4.0.4 GA
linux
Increasing the RAM to 2GB will help. Right now, the OS is using about 1/2GB and
the app server is using another 1/2GB, which leaves nothing for postgresql. So
I imagine you are doing a lot of page swapping.
View the original post :
Did you google java thread dump?
The max heap size you specified is too large for the amount of ram you have,
which will cause thrashing even if jbossas is the only thing running on that
box. On top of that you have postgresql running on the same box, and the ram
you have is barely enough for
The best thing to do is get a Java thread dump. I recommend doing three thread
dumps at about 10 or 20 second intervals while the CPU usage is high. Examining
the threads to see which ones are busy and what code they are executing should
help pinpoint the problem.
Also, what are your JVM
PeterJ wrote : The best thing to do is get a Java thread dump. I recommend
doing three thread dumps at about 10 or 20 second intervals while the CPU usage
is high. Examining the threads to see which ones are busy and what code they
are executing should help pinpoint the problem.
|
| Also,
