Check the product Troubleshooting Guides on http://docs.sun.com.
Sun Java System Application Server Enterprise Edition 8.1 2005Q1 Troubleshooting Guide
Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Troubleshooting Guide
Sun Java System Application Server Enterprise Edition 8.2 Troubleshooting Guide
Sun Java System Application Server 9.1 Troubleshooting Guide
If none of the above guides solves your problem, follow the instructions in To Collect Required Debug Data for Any Application Server Problem, then gather the following information:
Run the netstat command and save the output.
netstat -an | grep application_server_port
netstat -an
Identify which part of the Application Server is not starting: node agent, DAS, or instance.
Run the following command on the Web Server start script and save the resulting file.
Node Agent
truss -eafl -wall -vall -rall -o /tmp/as-start.truss \ ./asadmin start-nodeagent -u admin nodeagentname |
Instance
truss -eafl -wall -vall -rall -o /tmp/instance-start.truss \ ./asadmin start-instance -u admin instancename |
DAS
truss -eafl -wall -vall -rall -o /tmp/das-start.truss \ ./asadmin start-domain -u admin domainname |
Node Agent
tusc -v -fealT -rall -wall -o /tmp/as-start.tusc \ ./asadmin start-nodeagent -u admin nogeagentname |
Instance
tusc -v -fealT -rall -wall -o /tmp/as-start.tusc \ ./asadmin start-instance -u admin instancename |
DAS
tusc -v -fealT -rall -wall -o /tmp/as-start.tusc \ ./asadmin start-domain -u admin domainname |
Node Agent
strace -fv -o /tmp/as-start.strace ./asadmin \ start-nogeagent -u admin nogeagentname |
Instance
strace -fv -o /tmp/as-start.strace ./asadmin \ start-instance -u admin instancename |
DAS
strace -fv -o /tmp/as-start.strace ./asadmin \ start-domain -u admin domainname |
Use DebugView tool. You can download this tool from http://www.sysinternals.com/Utilities/DebugView.html.
Collect log files from the following locations, depending on which Application Server component is failing.
DAS – server-root/domains/domainname/logs
Instance – server-root/nodeagents/nodeagentname/instancename/logs
Node agent – server-root/nodeagents/nodeagentname/agent/logs
If the log files do not contain an error message about the problem, use the logging facility from the DAS admin console.
Set logging on the failing component to the FINEST level.
If you cannot access the Application Server Admin GUI, you can directly edit the module-log-levels in the following configuration files:
UNIX (Solaris and HP-UX) and Linux
Edit the server-root/domains/domainname/config/domain.xml file and set logging for the failing component to FINEST.
Windows
Edit the server-root\domains\domainname\config\domain.xml file and set logging for the failing component to FINEST.