Trace files are high-volume logs of detailed, internal events in SpringSource Application Platform. Much of the trace output is intended to support problem diagnosis and will not be useful in day-to-day usage. Trace messages are of the form shown below:
[2008-04-29 16:39:39.217] latform-tomcat-thread-12 ingsource.management.adapter.jmx.ManagedResourceExporter.unknown I Registered MBean: SpringSource-AP:application=Application,type=ohwhatalovely.war,name=Application Details
By default, trace files are stored in
$PLATFORM_HOME/serviceability/trace.
When an application war is hot deployed, as described in section 5.1,
a new directory is created in $PLATFORM_HOME/serviceability/trace, with the name myapp.war-0. This directory
contains a trace file with information regarding the application and its status. For example:
[2008-04-30 13:54:06.002] async-delivery-thread-1 pringSource-AP.catalina].[localhost].[/springtravelosgi].unknown I Initializing Spring root WebApplicationContext
When the war file is un-deployed (see section 5.2), an exception is thrown and a stack trace is written to the trace file.