Enterprise bean and EJB container troubleshooting tips
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 logs for the application server which hosts the container. Look for the message server server_name open for e-business in the server log files. If the message does not display, or if you see the message, problems occurred during startup, browse the server log files for details.
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.
Note: 이 주제는 하나 이상의 애플리케이션 서버 로그 파일을
참조합니다. 권장되는 대안은 분배 및 IBM® i 시스템에서 SystemOut.log, SystemErr.log, trace.log 및 activity.log 파일을 사용하는 대신
HPEL(High Performance Extensible Logging) 로그를 사용하고
인프라를 추적하도록 서버를 구성하는 것입니다. 원시 z/OS® 로깅 기능과 연계하여 HPEL을 사용할 수도 있습니다. HPEL을 사용하는 경우
서버 프로파일 바이너리 디렉토리의 LogViewer 명령행 도구를 사용하여
모든 로그에 액세스하고 정보를 추적할 수 있습니다. HPEL 사용에 대한 자세한 정보는
HPEL을 사용한 애플리케이션 문제점 해결 정보를
참조하십시오.
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, 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.