The workflow agent status has changed because the JMS is unavaiable

shreeharinair

I am seeing this issue suddenly in our environment . None of our auto activity is working now .

2013-01-22T09:30:49.964000          3172[3376]          01015d8d80000007          [DM_WORKFLOW_I_AGENT_STATUS_CHANGE]info:  "The workflow agent status has changed because the JMS is unavaiable. The workflow agent is currently checking for available JMS.."

when i tried ,

http://localhost:9080/DmMethods/servlet/DoMethod

it is showing "Documentum Java Method Server" which means that  the JMS is running fine.

Please see the full logs

2013-01-22T09:30:38.729000          3172[3180]          0000000000000000          [DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: dm_Finance, Host Name: usac-cdev121 :V4 IP)"2013-01-22T09:30:38.729000          3172[3180]          0000000000000000          [DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: dm_Finance, Host Name: usac-cdev121 :V6 IP)"2013-01-22T09:30:38.729000          3172[3180]          0000000000000000          [DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: dm_Finance_s, Host Name: usac-cdev121 :V4 IP)"2013-01-22T09:30:38.744000          3172[3180]          0000000000000000          [DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: dm_Finance_s, Host Name: usac-cdev121 :V6 IP)"2013-01-22T09:30:38.744000          3172[3180]          0000000000000000          [DM_SERVER_I_START]info:  "Sending Initial Docbroker check-point "2013-01-22T09:30:38.994000          3172[3320]          01015d8d80000003          [DM_DOCBROKER_I_PROJECTING]info:  "Sending information to Docbroker located on host (usac-cdev121) with port (1490).  Information: (Config(Finance), Proximity(1), Status(Open))."2013-01-22T09:30:39.744000          3172[3180]          0000000000000000          [DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent master (tid : 3376, session 01015d8d80000007) is started sucessfully."2013-01-22T09:30:39.744000          3172[3180]          0000000000000000          [DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (tid : 3512, session 01015d8d8000000a) is started sucessfully."2013-01-22T09:30:40.776000          3172[3180]          0000000000000000          [DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (tid : 1472, session 01015d8d8000000b) is started sucessfully."2013-01-22T09:30:41.776000          3172[3180]          0000000000000000          [DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (tid : 4084, session 01015d8d8000000c) is started sucessfully."Tue Jan 22 09:30:47 2013 [INFORMATION] [AGENTEXEC 3452] Detected during program initialization: Version: 6.7.1000.0038  Win322013-01-22T09:30:49.964000          3172[3376]          01015d8d80000007          [DM_WORKFLOW_I_AGENT_STATUS_CHANGE]info:  "The workflow agent status has changed because the JMS is unavaiable. The workflow agent is currently checking for available JMS.."

Imran_Yusubov

1. Check dm_jms_config, there should be three links something like this, http://<server_name>:<port>/servlet.....

Make sure that all of the server name has a correct value.

2. Do the same for dm_server_config as well.

If the entries are not correct,update them using api.And make sure that when you ping to the server with the value shown in urls <server name> it can be reached. Check the urls in a web browser and make sure that there is nothing bloking them, such as firewall or etc.