OnDemand Users Group

Support Forums => CMOD for z/OS Server => Topic started by: Ed_Arnold on November 29, 2013, 03:00:49 PM

Title: ARSSOCKD HANG PROBLEM
Post by: Ed_Arnold on November 29, 2013, 03:00:49 PM
I have had reports of ARSSOCKD hanging.

It appears to be caused by application of either of the following:

OA43472  PEAPAR of UA67692  <<-- Unresolved
OA43472  PEAPAR of UA67735  <<-- Unresolved


Until I update this thread or OA43472 is resolved I recommend you consider what it might take to back off those PTFs.

From OA43472:

A second problem is a JVM failure where a thread created         
by the JVM appears to be successfully created but never           
actually runs.  pthread_create() returns                         
successfully, and the populated pthread_t looks like a           
reasonable value, but the thread's start_routine never executes. 

Ed
Title: Re: ARSSOCKD HANG PROBLEM
Post by: Ed_Arnold on December 05, 2013, 06:23:52 PM
Further investigation shows this is not confined to just those with either of those two PE PTFs applied.

Current planning is that the final PTF for the PE's will include a fix for the hang problem and the fix for the PE...there'll really be two fixes within the final PTF.

Ed
Title: Re: ARSSOCKD HANG PROBLEM
Post by: Ed_Arnold on December 23, 2013, 12:56:10 PM
APAR OA43472 has closed.   PTFs are


PTF#     Reason Listed       Size-KB PUT Status Hiper FMID     
-------- ------------------- ------- --- ------ ----- ---------
UA71790  ORDERED                297       COR     YES HBB7780 
UA71791  ORDERED                274       COR     YES HBB7790


Ed