For a failure for which you need to contact the system administrator or a failure for which you do not understand the measures you need to take, collect the following failure information and contact the system administrator:
Note that '?' in the following file names indicates the number of files:
- Operation log (cjwmessage?.log or cjrmessage?.log)
- Exception log (cjwexception?_?.log or cjrexception?_?.log)
- Maintenance log (cjwmessage?.log or cjrmessage?.log)
- Communication log (cjwtransport?_?.log or cjrtransport?_?.log)
- Command operation log (cjwsimport?.log, cjwapt?.log)
- Command exception log (cjwsimportex?_?.log, cjwaptex?_?.log)
- Command maintenance log (cjwsimport?.log, cjwapt?.log)
- Trace based performance analysis
- User-program specific log (only when present)
- Common definition file (cjwconf.properties or cjrconf.properties)
- Process-wise definition file
- DD file for the Web Service (web.xml, cosminexus -jaxws.xml)
- System properties and system class path set for the server and client
- Standard output and standard error output of the server and client
- Cosminexus Component Container and the Web server log
- Information collected for failure, defined in Cosminexus Component Container:
- User-defined file for the J2EE server
- Maintenance information of the J2EE server
- User-defined file of the server management commands
- Maintenance information of the server management commands
- Standard output and standard error output of the J2EE server
- Cosminexus TPBroker log in the J2EE server
- System properties and the system class path set in the EJB client application
- Standard output and standard error output of the EJB client application
To obtain the collection information as specified in Cosminexus Component Container when a failure occurs, see 3.8.9 How to collect data in the uCosminexus Application Server Maintenance and Migration Guide.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.