DataServices Processes Fail with "DataServices interface is not available"

Symptoms

Upon starting multiple DataService processes, DataServices processes end in Error status immediately after starting. Their stderr.log file shows “java.io.IOException: DataService interface is not available” although DataServices is operational. In addition, an “authentication failed” error is logged in the scheduler.log file.

Cause

When a logon request is successfully accepted by DataServices, RunMyJobs receives a response including the a session ID that can be used to launch DataServices job requests. These sessionIDs are valid for up to 20 minutes and should be reusable. BOBJ has a limited number of sessions. When they are exhausted, the error occurs.

Steps to reproduce:

Launch a large number of DataServices processes.

Workaround

Limiting the number of concurrently running DataServices processes , such as the use of Queue limits may mitigate the issue.

Affected version

RMJ 9.2.x

Resolution

This issue will be addressed in 9.2.9.2, 9.2.10.2 and 9.2.11.1

Reference 

RCORE-41674
RSC-599