Troubleshooting bwagent Issues

Some bwagent issues and possible resolutions are listed below. This list is not complete but provides examples of messages that might be returned.

For a complete list of error codes, see the TIBCO ActiveMatrix BusinessWorks™ Error Codes guide.

Issue Message Resolution
When registering a bwagent to a domain or AppSpace, or unregistering the AppSpace the bwagent cannot be registered.

TIBCO-BW-ADMIN-CLI-500132: Failed to unregister BW Agent [bwagent from the AppSpace [AppSpace]. <CausedBy> TIBCO-BW-ADMIN-500004: Error invoking [methodName] method on the agent [Agent], The BW Agent [Agent] on the remote machine is not running.

Verify the bwagent name. Check that the bwagent on the remote machine is running.
If you are unable to enable or disable the autoregistration feature from the command line after executing the enableautoregistration utility or the disableautoregistration utility. TIBCO-BW-AGENT-500004: Error invoking [method] method on the agent [bwagent]. The BW Agent [bwagent] on the remote machine is not running.

Check if bwagent is running, and if it is, verify its name.

The bwagent could not start because the mode is not set to enterprise. TIBCO-BW-AGENT-500006: Cannot start the agent. The admin mode in bwagent.ini is not configured for enterprise mode. Check your configuration and restart. Open a terminal and type the following command at the command line: bwadmin mode enterprise

Restart the bwagent.

A bwadmin command could not be completed. TIBCO-BW-ADMIN-500008: Error in initializing data manager, TIBCO-BW-ADMIN-PRSTNC-500001: Connection to BW Agent failed.

or

TIBCO-BW-ADMIN-CLI-500006: Failed to initialize transport, TIBCO-BW-ADMIN-PRSTNC-500001: Connection to BW Agent failed.

The first message indicates that the bwagent is not running. Start the bwagent.

The second message is displayed when bwadmin is configured for enterprise mode and the command could not be completed due to a failed bwagent connection.

The bwagent could not start due to an error with datastore initialization. TIBCO-BW-AGENT-500009: Failed to start agent due to an error in initializing data store, reason: Reason The datastore is written to the BW_HOME\domains\.datastore folder.

Verify the following:

* The specified folder exists.

* The bw.agent.technology.as.dataStoreLocation property in the BW_HOME\config\bwagent.ini file points to the datastore folder name.

* The bw.agent.technology.as.role property is set to server.

You might also see this message if there is an issue with the bw.agent.technology.as.dataStoreLocation property setting in the BW_HOME\config\bwagent.ini file. Make sure that the TCP protocol is specified only for the first URL in the string; not for subsequent URLs.

When starting a bwagent that is configured as part of an agent network, the URL of another agent in the network could not be found. unable to resolve network specification ('bwagent') Check the setting of the bw.agent.technology.as.dataStoreLocation property in the BW_HOME\config\bwagent.ini file.

Verify that:

  • The URL is specified as either IP address and port or host name and port, in the format: IP_address/hostname:port
  • There are no typos in the URL or port number.
  • A semicolon separator is used between URLs.
When starting a bwagent that is configured as part of an agent network, the bwagent starts but does not indicate that the agent has joined the network. N/A Check that the setting of the bw.agent.network.name property in the BW_HOME\config\bwagent.ini file is the same as the setting in other the configuration file for other bwagents in the network.
When starting a bwagent that is configured as part of a bwagent network, and the bwagent is not configured for the network, warnings are displayed.

There are [2] agents in the BW Agent group that store data. However, the property "minSeederCount" in the bwagent.ini file is set to [1], refer to the bwagent.ini file or the documentation and choose an appropriate value.

There are [2] agents in the BW Agent group that store data. However, the property "quorumSize" in the bwagent.ini file is set to [1], refer to the bwagent.ini file or the documentation and choose an appropriate value.

See comments in the BW_HOME\config\bwagent.ini file for information.
The TEA agent could not be registered. TIBCO-BW-ADMIN-500504: Failed to register TEA Agent [teaagent] with TEA server [http://host: port], TEA Agent registration failed, TIBCO-BW-TEAAGENT-500300: Failed to register BW TEA agent [teaagent] with TEA server, <CausedBy> Unable to register agent with name [teaagent]' Verify the URL to the TEA agent. Check that the TEA agent is running.

Whenever you initiate any operation such as create domain, create AppNode, the bwagent generates an unique ID for that operation and that ID persists till that operation is complete.

For example, when you create a domain, you get the following entries in the bwagent.log file: 

INFO  [<thread_number>] <fb587904-ab0c-4403-b682-da809ac57b96> c.t.b.t.m.d.u.DomainLifecycleCommand - Creating domain [<domain_name>] at default location
 INFO  [<thread_number>] <fb587904-ab0c-4403-b682-da809ac57b96> bw.audit - create -agent <agent_name> -domainHome <domain_home> domain <domain_name>
INFO  [<thread_number>] <fb587904-ab0c-4403-b682-da809ac57b96> c.t.b.t.m.d.u.DomainLifecycleCommand - TIBCO-BW-ADMIN-300100: Created the domain [<domain_name>]

To retrieve the unique id of the operation executed, follow the steps:

BWAdmin Command Line

  1. Open BW_HOME/bin/bwadmin-logback.xml in a text editor. Change the ROOT level setting at the end of the file as needed. 
    <root level="DEBUG">
    <appender-ref ref="STDOUT" />
    <appender-ref ref="FILE" />
  2. Open the BW_HOME/bin/bwagent-logback.xml file in a text editor. Change the ROOT level setting at the end of the file as needed. 
    <root level="DEBUG">
    <appender-ref ref="STDOUT" />
    <appender-ref ref="FILE" />
  3. Perform the operation such as Create Domain.
  4. Open the BW_HOME/logs/bwadmin.log file and retrieve the unique ID. The unique id is present at the beginning of an operation. 
     2020-12-08 15:32:10.412 DEBUG [main]
<5a83a476-67f1-4bc7-ba49-70451c1bf320> com.tibco.thor.frwk -
Starting Execution for command [com.tibco.bw.thor.admin.cli.commands.CreateEntityCommand]
at Time [timestamp] with
ID[5a83a476-67f1-4bc7-ba49-70451c1bf320]
  5. You can verify the logs associated with the operation in the bwagent.log file using the same unique id of the operation as per the step 4.

BWAgent REST API

  1. Open the BW_HOME/bin/bwagent-logback.xml file in a text editor. Change the ROOT level setting at the end of the file as needed. 
    <root level="DEBUG">
    <appender-ref ref="STDOUT" />
    <appender-ref ref="FILE" />
  2. Perform the operation such as Create Domain.
  3. On receiving the response, you get the operation ID in the response headers.
  4. You can verify the logs associated with the operation in the bwagent.log file using the operation id obtained in the step 3.