+

Search Tips   |   Advanced Search

Enterprise bean and EJB container troubleshooting tips

If we 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:

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

If none of these steps solves the problem, 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 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.


Related tasks

  • Use High Performance Extensible Logging to troubleshoot applications
  • Assembling EJB modules

  • Application client log error indicates missing JAR file