Symptom
- Data Services scheduled jobs are not getting triggered
- Data Services scheduled jobs that used to finish take longer to execute or appear to hang until the server host is restarted
- Restarting the Job Server temporarily resolves issue
- Error: "Exception thrown when trying to communicate with Job Server: <JobServer_Name>. Read timed out" when executing Job
- Server Eventlog shows Job Server is restarting repeatedly without intervention
- JobServer: -------------------------------------------------- (BODI-850035)
(14.2) JobServer: Job Server Started... (BODI-850036) - "ADDRINUSE at RWSocket::bind" occurs if the Job Server is still running and unresponsive
- JobServer: -------------------------------------------------- (BODI-850035)
- Server Eventlog shows message
- JobServer: All request processing threads <100> are busy. The request from client <x.x.x.x> is queued. Number of requests pending to process <##>. (BODI-850280)
. Read timed out" when executing Job on the job server. - SAP Data Services 4.x"> Read more...
Environment
SAP Data Services 4.x
Product
SAP Data Services all versions
Keywords
data services, Sending notification, BODI-850170, BODI-850105, schedule, trigger, ADDRINUSE at RWSocket::bind, Read timed out , KBA , EIM-DS-SVR , Administration/Server , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview