|
Problem(Abstract) |
By default, a core file is generated in the same directory
where the executable file was invoked. UNIX® systems provide configuration
options for setting the location where the core file is written when an
application crashes. The core file location can also be change by
modifying the server.xml of the Application Server. |
|
|
|
Resolving the
problem |
UNIX System Configuration Options:
You can change the location where a core file is written using one of
these three methods:
- You can use the coreadm system utility to configure core file names
and locations. See "man coreadm" for examples.
- On AIX® systems, using the /usr/bin/syscorepath command, you
can specify a single system-wide directory where all the process core
files are dumped.
- You can use symbolic links to change the location of core
files. For example, to save a WebSphere® Application Server core
files to the /tmp directory:
ln -s /tmp/core /usr/WebSphere/AppServer/bin/core
Changing the Core File Location in the server.xml File:
To temporarily change the location of where core files are
generated:
- Locate the server.xml file for your Application Server. For
example:
/usr/WebSphere/AppServer/config/cells/yourCell/nodes/yourNode/servers/yourServerName
- Stop the Application Server.
- Create a backup copy of the server.xml file.
- Edit the file:
- Search for "workingDirectory".
- Change $(USER_INSTALL_ROOT) to a temporary location with enough space
to hold the core file.
- Save the server.xml file.
- Start the server.
- Generate a core file to test.
- Collect the core file from the temporary location.
- Restore the original server.xml file.
- Restart the server.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|