Rhapsody's log files are found in the Rhapsody installation directory:
\log\wrapper.log
The wrapper is where the 'service' application writes information relating to JVM startups, shutdowns and crashes. It is also where stdout and stderr are redirected, so sometimes will contain other important information.
This log should be collected any time there is an issue with startup, shutdown or memory. In other words, any Rhapsody issue that is not caused by route or communication point configuration.
\log\log.txt
These logs are the text version of the main Rhapsody logging. This is where all components in Rhapsody log information. These logs should be included any time there is a problem with Rhapsody. These logs are rolling, so will overwrite old information automatically. By default, Rhapsody stores ten files, with a 5MB file size. You can alter the default settings by changing the following lines in log4j.properties.
log4j.appender.FILE.MaxBackupIndex=9 log4j.appender.FILE.MaxFileSize=5MB
\derby.log
Logs events regarding the internal Derby database. Rhapsody uses the Derby database to implement lookup tables.
\equinox\************.log
These logs are the OSGi startup logs. A new log is created every time Rhapsody is restarted. These logs should be included any time there is a problem that stops Rhapsody from starting up or a custom module does not load.
\log\************.log
These logs are the data version of the main Rhapsody log. They include binary data, which makes reading difficult. These logs are only needed if the text version has overridden the information that is relevant, that is, for example, the oldest information in the text log is from yesterday, but the problem reported happened three days ago.
\hs_err_pid****.log
These logs are JVM crash logs. They are only created when the JVM crashes and should be included if they exist (especially when dealing with a crash).