| Author |
HIGH CPU for a WAS procces
|
|
|
| Hi,
I've been having some problems with WAS. A Java procces is running and is at 366% CPU. I've been having this problem for a while now. I turn off and restart WAS using standard and safe procedures and the problems dissapears. After a while (7-8 days) the p
roblem reapears. I want to know if i can find a solution to this problem before i contact a WAS tehnical support specialist. I know that 7-8 days seems like acceptable for a restart... but sometimes i can't afford one. I would appreciate any help you cand
give me.
Thank you,
Paul
| |
|
|
| Ken Hygh 2007-08-07, 1:18 pm |
| paul.chibulcuteanu@bisnet.ro wrote:
> Hi,
>
> I've been having some problems with WAS. A Java procces is running and is at 366% CPU. I've been having this problem for a while now. I turn off and restart WAS using standard and safe procedures and the problems dissapears. After a while (7-8 days) the
problem reapears. I want to know if i can find a solution to this problem before i contact a WAS tehnical support specialist. I know that 7-8 days seems like acceptable for a restart... but sometimes i can't afford one. I would appreciate any help you ca
nd give me.
>
>
> Thank you,
> Paul
Can I get a copy of your WAS? I'd love to be able to run at 366% CPU :-)
Right way: get a profiler, find out what is burning CPU
Poor man's way: do a thread dump, see what threads are running, see what
doesn't look reasonable.
Ken
| |
|
| I have the same problem,the reason is was's version not fit the os's version.
what is your was version? and os version?
| |
| Yuriy Petrov 2007-08-08, 1:17 am |
| paul.chibulcuteanu@bisnet.ro wrote:
> Hi,
>
> I've been having some problems with WAS. A Java procces is running and is at 366% CPU. I've been having this problem for a while now. I turn off and restart WAS using standard and safe procedures and the problems dissapears. After a while (7-8 days) the
problem reapears. I want to know if i can find a solution to this problem before i contact a WAS tehnical support specialist. I know that 7-8 days seems like acceptable for a restart... but sometimes i can't afford one. I would appreciate any help you ca
nd give me.
>
>
> Thank you,
> Paul
Memory leak and, as the result, GC is running all the time? This does fit the symptom "it gets back
to norm after restart for a while, but then..."
| |
|
| I'm sorry that i didn't mention i use WAS 5.1.1 CF 13. on AIX 5.2.0.0. I think i'm gonna go with CF15. I saw that many had this problem before and what u guys said is not a solution.
| |
|
| Also is there a reason why this should happen not necesarily on high traffic? WAS is handling lots of processing perfectly then when he hasn't got so many processes to run it jams. And i don't know what GC is.
Thank you,
Paul
| |
| Paul Ilechko 2007-08-09, 1:23 pm |
| paul.chibulcuteanu@bisnet.ro wrote:
> Also is there a reason why this should happen not necesarily on high
> traffic? WAS is handling lots of processing perfectly then when he
> hasn't got so many processes to run it jams. And i don't know what GC
> is. Thank you, Paul
GC = garbage collection. If you're working with a J2EE appserver you
need to get some understanding of how JVMs work, and also of how
appservers share resources such as threads and connections. This may
explain some of the things you are seeing.
|
|
|
|