WAS v8.5 > Reference > Troubleshooting tipsEnterprise bean and EJB container troubleshooting tips
If you are having problems starting an EJB container, or encounter error messages or exceptions that are generated by an EJB container, follow these steps to resolve the problem:
- Use the dmgr console to verify the application server which hosts the container is running.
- Browse the JVM log files for the application server which hosts the container. Look for the message server server_name open for e-business in the SystemOut.log. If the message does not display, or if you see the message, problems occurred during startup, browse the SystemErr.log for details.
- Browse the system log files for the application server which hosts the container.
- Enable tracing for the EJB container component, using the following trace specification EJBContainer=all=enabled. Follow the instructions for dumping and browsing the trace output to narrow the origin of the problem.
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
If none of these steps solves the problem, check to see if the problem is identified and documented in the following topics: Diagnose and fixing problems: Resources for learning. If we do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information to resolve this problem. Before opening a PMR, see the IBM Support page.
Subtopics
Related
Troubleshoot applications with HPEL
Assemble EJB modules