How do I turn on the Repository internal tracing to help isolate Repository problems?
Article ID: KB0087703
Updated On:
| Products | Versions |
|---|---|
| TIBCO Repository | - |
| Not Applicable | - |
Description
Resolution:
You can turn on internal tracing by setting the appropriate values in the server.ini file. Specifically, you can set values for the variable:
com.tibco.infra.tools.trace.typesEnabled
Multiple values can be set in a comma separated list.
Example:
com.tibco.infra.tools.trace.typesEnabled = ClientBridge,RemoteRepoProcess, CachedServer, NodeCache
ClientBridge - shows instance data messages being
received and sent
RemoteRepoProcess - shows InstanceManagement
CachedServer - shows status as server processes
requests
NodeCache - shows actions in the server cache
You can turn on internal tracing by setting the appropriate values in the server.ini file. Specifically, you can set values for the variable:
com.tibco.infra.tools.trace.typesEnabled
Multiple values can be set in a comma separated list.
Example:
com.tibco.infra.tools.trace.typesEnabled = ClientBridge,RemoteRepoProcess, CachedServer, NodeCache
ClientBridge - shows instance data messages being
received and sent
RemoteRepoProcess - shows InstanceManagement
CachedServer - shows status as server processes
requests
NodeCache - shows actions in the server cache
Issue/Introduction
How do I turn on the Repository internal tracing to help isolate Repository problems?
Environment
Product: TIBCO Repository
Version: All
OS: All
--------------------
Feedback
Yes
No
Powered by
