PQ28679: RESTART OF WEB SERVER FAILS WITH ' PTHREAD_CREATE FAILED . ERRNO=112 EDC5112I RESOURCE TEMPORARILY UNAVAILABLE . '

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Restart does not work with WebShpere Application Server.
  The following Scenarios have been reported in V1.1. They
  might also appear in V1.2.
  There could be other scenarios for which restart does not
  work.
  Scenario 1:
  When customer attempts to restart Web server(versus stop, start)
  with WebSphere Application Server 1.1, the restart processing
  fails with the following error in the Web server '-vv' trace
  log:
      pthread_create failed.  errno=112 EDC5112I Resource
      temporarily unavailable.
  For this particular customer, the Web server and Application
  Server actually restarted and some servlets such as
  HelloWorldServlet worked. However, a JDBC servlet did not.
  The browser kept spinning and did not return the expected data.
   Scenario2:
   Customer attempts to do a restart, but never receives
  IMW0098E Restart succeeded.
  IMW0235I Server is ready.
   .
  Restart..... complete.
   There is no pthread_create failure.
  Scenario 3:
     On a RESTART ABEND0C4 in  _cTterm and Web server
  terminates.
  KEYWORDS: WAS AppServer pthread
  Additional symptoms:
   The following symptoms have been seen running a standalone
  server with V1.2:
     When the Web server stops, you may receive a message:
  IEF142I IMWEBDPB IMWEBDPB - STEP WAS EXECUTED - COND CODE 0255
  . The Web server ended with RC=255. This problem is addressed
  in this APAR also.
  

Local fix

• Instead of restarting the Web server,  stop and then start the
  Web server.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users who want to restart the HTTP       *
  *                 server while a WebSphere Application Server  *
  *                 V1.1 or V1.2 is running.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a customer tried to restart the    *
  *                      HTTP Server with WebSphere Application  *
  *                      Server 1.1 or 1.2, he experienced       *
  *                      either of the following 2 scenarios:    *
  *                      1. Both servers restarted but           *
  *                      pthread_create failed and some          *
  *                      resources were temporarily unavailable. *
  *                      2. HTTP Server terminated with return   *
  *                      code 255. The Web server message        *
  *                      "IMW0098E Restart succeeded. IMW0235I   *
  *                      Server is ready." as well as the        *
  *                      Application Server ready message were   *
  *                      never received.                         *
  *                      Customers should not see scenario 1 any *
  *                      more because of the removal of the      *
  *                      thread limit in HTTP Server and         *
  *                      Application Server. This APAR addresses *
  *                      the problem in scenario 2.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The pthread_create failure is caused by the thread limit set by
  the HTTP Server. HTTP Server APAR PQ28276 and Application Server
  APAR PQ29395 now have removed the thread limit, so customers
  should not experience this problem any more if they have applied
  these 2 APARs. For more information on the removal of the thread
  limit, please refer to these 2 APARs.
  This APAR addresses the problem in scenario 2.
  The Application Server does a system.exit(exitStatus) when all
  of its auto start services are stopped. The value of exitStatus
  is 255 for restart. Auto start services are services that are
  automatically started at Application Server start up. The
  Application Server auto start service only includes
  servletservice, which is stopped when the servlet engine is shut
  down. Because the Application Server shuts down its servlet
  engine at restart, system.exit(255) is invoked. This terminates
  the HTTP Server process.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• Fully supported restart is a complicated issue. It requires
  complete cleanup, shutdown of the servlet engine, and the
  addition of destroy methods on classes that use static data. The
  destroy methods would reset the statics to their initial values
  and they would need to be called at an appropriate time. This
  will be implemented in Application Server V3.02 or higher.
  Application Server V1.1 and 1.2 now provide support for the
  toleration of restarting the HTTP Server and Application Server.
  That is:
  1. Only start and initialize the servlet engine when the
  Application Server first starts. Don't shut down the servlet
  engine and try to clean up resources at restart. Just detect
  that the servlet engine is already initialized and keep going.
  The resources will be cleaned up and garbage collected when the
  HTTP Server and Application Server are stopped.
  2. Don't allow any Application Server related properties to
  change during restart ( e.g. any changes in was.conf will not be
  picked up at restart ). This prevents inconsistent behavior
  before and after restart.
  
  The following COMPID's are affected by these changes:
  5697D4300 WAS W10 web release for LDGW on OS/390 R5 & R6.
  5697D4300 WAS 110 for OS/390 R7 & R8.
  5697D4300 WAS 120 for OS/390 R5 through R9.
  
  The code changes are stored in CMVC under defect PQ28679 and
  67824.
  
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UQ47011 UQ47012 UQ47013

Modules/Macros

• EJSJJST  EJSMADPT EJSMNATV EJSW10
  

Fix information

• Fixed component name

  DGW/WAS OS/390

• Fixed component ID

  5697D4300

Applicable component levels

• R110 PSY UQ47012

     UP00/09/19 P F009

• R120 PSY UQ47013

     UP00/09/20 P F009

• RW10 PSN

     UP

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.