Appendix E.21 Analysis when there is no response from a Cosminexus JMS Provider service
(1) Process preconditions
- The J2EE server process is running.
- The CJMSP resource adapter is running.
- The CJMSP Broker process is running.
- The application is running.
(2) Information and supplementary explanation required for execution
The coding, such as (A1), corresponds to the coding in the figure.
- (A1)
- Collect the PRF trace.
- (A2)
- Collect the thread dump for the J2EE server.
- (A3)
- Check the log beneath Cosminexus-installation-directory/CC/server/public/ejb/server-name/logs, and eliminate the error systematically.
- (A4)
- Collect the thread dump for CJMSP Broker.
- In Windows
- There are two methods for obtaining the CJMSP Broker thread dump:
- Use the JavaVM command jheapprof.
For details on how to use this command, see jheapprof (Output of extended thread dump with Hitachi class-wise statistical information) in the uCosminexus Application Server Command Reference Guide.
- At the command prompt where you start CJMSP Broker, enter the Ctrl + Break keys.
In this case, if you obtain the thread dump and then stop CJMSP Broker, the message Do you want to terminate the batch job? (Y/N)? is displayed. At this time, specify N.
- In UNIX
- Use the kill command.
- Example of execution
kill -3 < process ID>
- (A5)
- Check the log beneath Cosminexus-installation-directory/CC/server/public/ejb/server-name/logs/cjms/connector-name, and eliminate the error systematically.
- (A6)
- Check the log beneath <VAR_HOME>/instances/instance-name/log, and eliminate the error systematically.
- (A7)
- Recover the Cosminexus JMS Provider service according to the procedure described in Appendix E.24 Recovery when there is no response from a Cosminexus JMS Provider service.