Skip to Content
0
Former Member
Jul 08, 2016 at 09:35 AM

AL_RWJobLauncher.exe process went into hung state

287 Views

HI Experts,

Good day!!

AL_RWJobLauncher.exe process went into hung state and no BODS job was reflected on the Data Services Management Console. We manually tried to executed the job using the batch file, but the job failed to launch in DSMC due which effected the production environment for a whole day.

Workaround: We restarted the DI Service but AL_RWJobLauncher.exe still appear in the process list, so we manually killed the AL_RWJobLauncher.exe process on all job servers.

1) In Server Even Logs, we have found the error:

----------------------------------------------------------------------------------------

Error <RWSecureSocketError: in RWSecureSocket: end: SYSTEM_ERROR> while processing request <41> from client

14.2) 07-02-16 20:46:31 (1588:1592) JobServer: All request processing threads <100> are busy. The request from client is queued. Number of requests pending

to process <1>. (BODI-850280)

(14.2) 07-02-16 20:46:31 (1588:1592) JobServer: All request processing threads <100> are busy. The request from client is queued. Number of requests pending

to process <1>. (BODI-850280)

2) In IPS Server's tomcat logs, stdout.log files has below error:

------------------------------------------------------------------------------------------

BrokerCommFailure detected. No retry configured.

Job server is not accessible.Connection refused: connect

3 ) In which scenarios the JobServer's requsts will be in pending state?

How to increase the request processing thread count in DSConfig.txt?