Failure to read socket: process-execution2

 Hi All,

 

We recently updated to Appian 16.3. We are facimng multiple issues on the environment. to find out the root cause for one of the issue, When I checked the logs: I saw the following error:

 

04:05:01,749 INFO [stdout] (Appian Engine Work Controller: process-execution2 3) 2017-04-27 04:05:01,749 [Appian Engine Work Controller: process-execution2 3] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Failure to read socket: process-execution2 (localhost:5028)
04:05:01,758 INFO [stdout] (Appian WorkPoller - 2 [ProcessExec02] (originally: default-threads - 15)) 2017-04-27 04:05:01,758 [Appian WorkPoller - 2 [ProcessExec02] (originally: default-threads - 15)] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Failure to read socket: process-execution2 (localhost:5028)
04:06:18,607 INFO [stdout] (Appian Engine Work Controller: process-execution2 3) 2017-04-27 04:06:18,607 [Appian Engine Work Controller: process-execution2 3] ERROR com.appiancorp.process.background.EngineWorkController - Cannot retrieve engine burdens: An IpcException has occurred while invoking the method: availableEngineWork on process-execution2 (localhost:5028)
04:06:18,645 INFO [stdout] (Appian WorkPoller - 2 [ProcessExec02] (originally: default-threads - 15)) 2017-04-27 04:06:18,624 [Appian WorkPoller - 2 [ProcessExec02] (originally: default-threads - 15)] ERROR com.appiancorp.ra.workpoller.WorkPoller - ProcessExec02: Error while trying to accept Work in Bulk: An IpcException has occurred while invoking the method: acceptWorkBulk on process-execution2 (localhost:5028)

 

Can anyone guide why we are seeing this error and how can we fix it?

 

Thanks

Rishu

  Discussion posts and replies are publicly visible

Parents Reply Children
  • 0
    Appian Employee
    in reply to rishub
    The error indicates that the app server is unable to communicate with the engines (in this case, process-execution02). In the vast majority of cases, this is because the engine is not running. However, in rare cases, this may be due to other problems, such as network issues. If checkengine is not showing any problems, I would recommend creating a Support Case.