Debugging

In the event of an error, the software provides detailed messages that can help you trace through to the cause of an issue. You can adjust logging levels as needed to capture different granularity of messages for different loggers.

Messages returned by TIBCO ActiveMatrix BusinessWorks™ are categorized by component and by error code within component. The following table shows the components of the software that return messages:

Component ID Description
BX

ActiveMatrix BusinessWorks™ Engine Layer

PVM

ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-ADMIN

ActiveMatrix BusinessWorks Administrator

TIBCO-BW-ADMIN-CLI

ActiveMatrix BusinessWorks Administrator Command Line Interface

TIBCO-BW-BINDING-REST

ActiveMatrix BusinessWorks REST Binding

TIBCO-BW-BINDING-SOAP

ActiveMatrix BusinessWorks SOAP Binding

TIBCO-BW-CORE

ActiveMatrix BusinessWorks Engine Layer

TIBCO-BW-FRWK

ActiveMatrix BusinessWorks Framework

TIBCO-BW-PALETTE

ActiveMatrix BusinessWorks Palette Layer

TIBCO-BW-PALETTE-<PaletteName>

ActiveMatrix BusinessWorks Palette specific activity implementation

TIBCO-BW-SR

ActiveMatrix BusinessWorks Shared Resource API Layer

TIBCO-BW-SR-<UniqueName>

ActiveMatrix BusinessWorks specific Shared Resource implementation

TIBCO-BW-STATS

ActiveMatrix BusinessWorks Stats Collector

TIBCO-THOR-FRWK Thor Framework
Note: The Engine layers with component IDs BX and PVM do not follow this convention.

The following tables identifies the log levels used by the software and the corresponding error code range:

Log Level Error Code
TRACE 100001 - 109999
DEBUG 200001 - 209999
INFO 300001 - 309999
WARN 400001 - 409999
ERROR
Errors can be indicated by one of the following error code ranges:
  • 500001 - 509999
  • 600001 and higher
  • 0xxxxx
Note:
  • Error codes 600001 and higher indicate exceptions in the execution and are always associated with a 5xxxxx error code, which can be traced in the log file.
  • Error codes starting with 0xxxxx indicate internal errors. Contact TIBCO Support for possible resolution or a workaround.

If you encounter an error that does not start with a 0, change the logging level of the AppNode and bwagent loggers to DEBUG. Try to recreate the scenario and examine the log file to try and trace the issue. The error messages are detailed and can help you understand the chain of events that led up to the issue. For more information on log files and log file configuration see the section on Logging in the TIBCO ActiveMatrix BusinessWorks™ Administration guide.

The following sections in the TIBCO ActiveMatrix BusinessWorks™ Concepts guide list issues you might encounter, along with possible resolutions:

  • Troubleshooting bwagent Issues
  • Troubleshooting Runtime Entities Issues
  • Troubleshooting Archive Issues
  • Troubleshooting Application Issues
  • Troubleshooting TIBCO Enterprise Administrator Integration Issues