Learn to troubleshoot when BackgroundProcessing Node type fails Test Connectivity.

Scenario 1

Test Connectivity fails on specifying Node type as BackgroundProcessing and Startup option as NodeClassification based on Startup.

Scenario 2

File Listener connection is unsuccessful and it impacts the case status and update details of the Claim cases.

Error

PFB failure on connection: Status Fail:Configuration Message Listener is not configured to run on current host [ipec2.internal] - update Listener Nodes list.

Scenario 3

Test Connectivity on File Listeners on BackgroundProcessing nodes fails with the following error after upgrade:

Status Fail:Configuration Message Listener is not configured to run on current host [ip-ec2.internal] - update Listener Nodes list.

However, Successful message displays on trying to test with WebUser or ALL nodes. On attempting to run the listener in Admin Studio with Node type as Background processing, it started on two nodes. However, an error occurred on one node.

Scenario 4

In the File Listener configuration, while setting up the listener to work on BackgroundProcessing node type as NodeClassification based startup, the following exception occurs:

Listener is not configured to run on current host [ip-.ap-southeast-2.compute.internal] - update Listener Nodes list.

Design time tries to validate the current node which is actually a Web-User node. Listener works well when it is configured to Run on all nodes.

Explanation

The reported behaviors are as per the expected product behavior when File Listener is configured to run on BackgroundProcessing node and Test connectivity is being attempted from the Web-User node.

Solution

Perform the following steps:

1. Use Startup option either as Run on all the nodes or Host based startup to perform Test Connectivity.
2. Provide the host ID of the corresponding Web node.

Related content

Creating a file listener