Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Appendix B Trace Messages : Trace Message Fields

Trace Message Fields
Each trace message includes the following fields:
Table 18 Tracing Fields
Timestamp of occurrence. For example, 2003 Feb 22 20:14:51:718 GMT -8.
---Info. Indicates normal adapter operation. No action is necessary. A tracing message tagged with Info indicates that a significant processing step was reached and has been logged for tracking or auditing purposes. Only info messages preceding a tracking identifier are considered significant steps.
---Warn. An abnormal condition was found. Processing will continue, but special attention from an administrator is recommended.
---Error. An unrecoverable error occurred. Depending on the error severity, the adapter may continue with the next operation or may stop altogether.
---Debug. A developer-defined tracing message. In normal operating conditions, debug messages should not display.
When configuring the adapter, you define what roles should or should not be logged. For example, you may decide not to log Info roles to increase performance.
Unique code for the message and description. Status codes are identified by a unique number and description. If a trace message includes an error or warn role, the status code documentation includes a resolution. See Status Messages for details.
A unique identifier that is "stamped" on each message by the originating adapter. The tracking identifier remains in effect from a message’s beginning to its completion as it is exchanged by TIBCO applications. If the adapter is the termination point of the message, the tracking identifier is not displayed in the trace message.
Application Information
Application-specific information added to the tracking info to trace the message back to its source. Set initially by the originating adapter and carried forward. It is augmented by each intermediate component.
 
Status Messages
Resolutions are provided wherever possible for error and warning messages. If there is no resolution provided, or if you need additional help, contact TIBCO Support at http://support.tibco.com.
Table 19 Error Messages
The terminate subject is syntactically invalid. Please specify a subject with a valid syntax and naming conventions.
Invalid Instance Name/Adapter Configuration names must have only alphanumeric characters and can be up to 80 characters long. Please type in a valid name.
This message is used to catch any exception thrown during adapter start-up as well as while processing messages. Hence there is now explicit resolution for the same.
Check whether the Tuxedo settings provided (in tpinit.properties) is correct and whether the Tuxedo middleware services are up.
Check the contents of the tpinit.properties file (default location $ARBORDIR/bsdm_site/java).
Check whether FXSecFwkClient.jar is present in the classpath (default location $ARBORDIR/bsdm_site/java).
Check the contents of the tpinit.properties file (default location $ARBORDIR/bsdm_site/java).
Check whether the Kenan Jars (default location $ARBORDIR/bsdm_site/java) are in the classpath.
Check the repourl and the configurl.
Check the repourl provided to the adapter.
Please check the repourl provided to the adapter.
Specify the custom factory class name for CustomCall Out and ensure the custom classes are present in the classpath.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved