Which JDK version are you using, I had a problem with CPU usage growing on one.
Also have you tried a newer version of JBoss yet?
We are using the 1.3.1 JDK version...
About the JBOSS version, we are still using the same version... Is a good idea to change it???
It is strange that you are getting a runaway process. You need to try and isolate the issue. JBoss itself doesn't normally consume increasing amounts of CPU. Normally, you would expect less than 1% in a quiescent state.
Also, it would be useful to test the conditions that cause the runaway process if you cannot isolate components - you would need to run this in an isolated environment. This would be laborious if it takes up to 48 hours to manifest.
Does it occur if you only deploy the components but do not run the application? Is it related to any special MBeans you have deployed? Look for the more obvious changes to a standard JBoss environment.
We are still facing the same problem.If We reboot the machine and restart the server,the same configuration works fine.Can You explain why is that Happening? Are these known bugs? Please clarify...
No, typically JBoss does not show these conditions. However, on Linux I have used JDK 1.4.x in the past but solely IBM SDK 1.4.x now.
Our enterprise applications run without any problem and the JBoss server can run for months without a problem - maintenance is the only interruption to the lifecycle.
I would try upgrading the JDK and monitor the issue. If it is still a problem, it is going to be related to an introduced element - whether it be an MBean or an EJB. I have heard of incidents where people have misconfigured the scheduler. In any case, the only way for anyone in the forums to help is for the folks who are having these problems to perform some more diagnostics to isolate the problem area.
Or they could pay for expert help. ;)
Anyway, I would try things like observing whether a standard install without any changes or any applications deployed suffers the same problems and work forward from there.
If you are going to upgrade the JDK I would reccomend that you avoid Sun JDK 1.4.0.
I had loads of problems with it (Including run away processed) and I was able to put together some test cases using JBoss that would be guaranteed to make it core dump.
My tests work fine with Sun JDK 1.4.1_03.
1.3.1 had a memory leak in java.lang.StringBuffer.toString( ). We saw bad behavior (lots of Strings allocated, out of mem errors, cpu load increasing with time)
Probably not the problem, but it's possible. You want to upgrade to 1.4.2 if you can, there have been many bug fixes.