Network Deployment (Distributed operating systems), v8.0 > Reference > Troubleshoot tips


Enterprise 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:

With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.

If none of these steps solves the problem, check to see if the problem is identified and documented in the following topics: Diagnosing and fixing problems: Resources for learning. If you 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


Application client log error indicates missing JAR file
Use HPEL to troubleshoot applications
Assembling EJB modules

+

Search Tips   |   Advanced Search