Troubleshooting
Problem
A file is recreated after being removed multiple times and fills the file system space if not managed. WebSphere's server.xml has been inspected and this file is not specified in server.xml.
Symptom
What appears to be a binary trace file intended to provide database or datasource tracing grows without bounds and is recreated after a reboot or after WebSphere has been restarted.
Cause
It is possible that a change was made to trace settings within WebSphere's resources.xml file.
Diagnosing The Problem
This command will return all file names that have "dataTrace.trc" in the text of the file.
cd <TWAHome>/eWAS
find . -type f | xargs grep -l "dataTrace.trc" 2>/dev/null
Resolving The Problem
A known location of a trace setting that behaved this way follows:
<TWAHome>/eWAS/profiles/<profileName>/config/cells/<cellName>/nodes/<nodeName>/servers/<serverName>/resources.xml
Sample line with the file reference from resources.xml:
<resourceProperties xmi:id="J2EEResourceProperty_1344437099482" name="traceFile" type="java.lang.String" value="/tmp/dataTrace.trc" description="The trace file to store the trace output. If you specify the trace file, the DB2 Jcc trace will be logged in this trace file. If
this property is not specified and the WAS.database trace group is enabled, then both WebSphere trace and DB2 trace will be logged into the
WebSphere trace file." required="false"/>
As the description states, a file only needs to be specified to have Jcc tracing written to that file. To disable the trace writing to the target file:
Replace:
value="/tmp/dataTrace.trc"
With
value=""
Then restart the WebSphere Application Server.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21622563