IBM Support

TRIRIGA Workflow Agent failed to run after upgrade

Technote (troubleshooting)


Problem(Abstract)

TRIRIGA Workflow Agent will not start on application server. Startup Failed

Symptom

TRIRIGA Workflow Agent will not start on application server.


2015-07-09 09:34:36,075 INFO [com.tririga.platform.agent.AgentManager]
(WebContainer : 1) Start requested for WFAgent on xxxxx.
2015-07-09 09:34:36,310 WARN [com.tririga.platform.agent.AgentManager]
(HeartbeatThread) Agent is not startable on this host, it may already
be running: WFAgent[MID-297637996]


Cause

Root cause was that the application server was not resolving the host name on the box. This is generally a network DNS configuration issue.
Explicitly defining the instance_id and instance_name is our recommended way to define the servers. It makes it easier to identify the servers in the Admin console visually and also bypasses the need to have the specific IP or DNS defined


Resolving the problem

Set the instance_id and instance_name on both application and process server in the TRIRIGAWEB.properties.

Explicitly identify the application and process servers with unique instance_id and instance_name values in the TRIRIGAWEB.properties file.

Set the instance_id=1000 and instance_name=appserver on the application server
and
Set the instance_id=2000 and instance_name=procserver on the process server

Then go into the TRIRIGA Admin Console and set the hostnames to match the new instance names given.

Save and restart the agents.

Document information

More support for: IBM TRIRIGA Application Platform
IBM TRIRIGA Application Platform

Software version: 3.3, 3.3.1, 3.3.2, 3.4, 3.4.1, 3.4.2, 3.5

Operating system(s): Platform Independent

Reference #: 1962126

Modified date: 07 February 2016