If you are having problems starting an Enterprise JavaBeans (EJB) container, or encounter
error messages or exceptions that are generated by an EJB container,
follow these steps to resolve the problem:
- Use the administrative console to verify that 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, by 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.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you 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 or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
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.