matrix0511
asked on
Where Can I find Websphere 5.0 Core/Java Heap Dump files?
We are on an older version of WAS. WAS 5.0. We are having a lot of random performance issues from our web server that sits on top of WAS.
As troubleshooting steps we want to look at the core head dump files but we cant find them. I have searched under: C:\temp. I have also searched on all drives for: *.dmp or *.trc. but nothing.
Can someone tell me where I can look for these files?
Thanks!
As troubleshooting steps we want to look at the core head dump files but we cant find them. I have searched under: C:\temp. I have also searched on all drives for: *.dmp or *.trc. but nothing.
Can someone tell me where I can look for these files?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey Gary, something I just noticed on the WAS server admin console setting that might explain why we are having these performance issues. NOtice the attached screen print for JVM MIN & MAX memory settings. Ideally they should be set to something like 32MB min & 1024MB max.
but notice that it's set to. do you think this could be the culprit? Perhaps its having to start so low with the memory setting?
1-15-2014-12-44-23-PM.jpg
but notice that it's set to. do you think this could be the culprit? Perhaps its having to start so low with the memory setting?
1-15-2014-12-44-23-PM.jpg
Yes, or course. Inadequate memory can cause all kinds of problems, and setting is restricting the heap to 256MB of RAM.
You've also got some debugging options turned on. Depending what is in there, that can create a lot of overhead, too.
You've also got some debugging options turned on. Depending what is in there, that can create a lot of overhead, too.
ASKER
You mentioned we have debugging turned on. Where did you see that??
ASKER
And shouldn't we be seeing those heap dump files no matter what? And especially with these wrong settings, I would think that there would be heap dump files all over the place. But I don't see any.
Debug arguments box.
ASKER
Ok. So Gary, to turn OFF debug do I just remove that debug argument? (-Xdebug)?
Or what is the best way to disable that? Thanks
Or what is the best way to disable that? Thanks
The debug arguments are probably only applied when you check the Debug Mode box above the debug arguments. Check the help text.
ASKER
I checked with Oracle (JDE) support and they said that argument (-Xdebug) does in fact mean debugging is turned on.
But you make an interesting point. I want to see how we can confirm if its actually debugging or not. Is there certain log files that it creates that would indicate its debugging? I would expect to see a ton of large files if this setting has been in place a long time right?
But you make an interesting point. I want to see how we can confirm if its actually debugging or not. Is there certain log files that it creates that would indicate its debugging? I would expect to see a ton of large files if this setting has been in place a long time right?
The question isn't what -xDebug does, it is whether or not these debug arguments are actually being applied when the JVM is started.
-xDebug enables the remote debugging service, and allows you to attach a remote debugger (from Eclipse, for example) to your application. Usually there will be options too, including -Djava.compiler=NONE, which causes your code to run in pure interpreted mode (no JIT - which is liable to significantly slow your application down)
I think ticking the "Enable Debug" box determines whether these are applied when the JVM is started or not. It wasn't ticked on the screen shot you posted above, so that may mean it won't be applied on the next server start.
To be sure, just read the help text on that page, it should tell you.
Or look as your startServer.sh script. It will contain a line like this:
export DEBUG="-Djava.compiler=NON
or
# export DEBUG="-Djava.compiler=NON
If the line is commented out, debugging is disabled. If it is not commented out, debugging is enabled.
-xDebug enables the remote debugging service, and allows you to attach a remote debugger (from Eclipse, for example) to your application. Usually there will be options too, including -Djava.compiler=NONE, which causes your code to run in pure interpreted mode (no JIT - which is liable to significantly slow your application down)
I think ticking the "Enable Debug" box determines whether these are applied when the JVM is started or not. It wasn't ticked on the screen shot you posted above, so that may mean it won't be applied on the next server start.
To be sure, just read the help text on that page, it should tell you.
Or look as your startServer.sh script. It will contain a line like this:
export DEBUG="-Djava.compiler=NON
or
# export DEBUG="-Djava.compiler=NON
If the line is commented out, debugging is disabled. If it is not commented out, debugging is enabled.
ASKER