Enterprise bean and EJB container troubleshooting tips
- Use the administrative console to verify that the application server which hosts the container is running.
- Browse the logs for the application server which hosts the container. Look for the message server server open for e-business in the server log files. If the message does not display, or if we see the message, problems occurred during startup, browse the server log files for details.
- (iSeries) Browse the JVM log files for the application server which hosts the container. Look for the message server server open for e-business in the SystemOut.log. If the message does not display, or if we see the message, problems occurred during startup, browse the SystemErr.log for details.
- (iSeries) Browse the system log files for the application server which hosts the container.
- (iSeries) 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 High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
Check to see if the problem is identified and documented in the following topics: Diagnose and fix problems: Resources for learning. If we do not see a problem that resembles ours, or if the information provided does not solve our problem, refer to the troubleshooting help for further assistance.
IBM Support has documents that can save you time gathering information to resolve this problem. Before opening a PMR, refer to one of the EJB MustGather documents.
See also
- Use High Performance Extensible Logging to troubleshoot applications
- Assembling EJB modules
- Application client log error indicates missing JAR file
- Troubleshooting: Learning more about EJBs and the EJBContainer