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.
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.
Limiting the number of concurrently running DataServices processes , such as the use of Queue limits may mitigate the issue.
This issue will be addressed in 18.104.22.168, 22.214.171.124 and 126.96.36.199
Please sign in to leave a comment.