PI31165: java.util.concurrent.RejectedExecutionException when default executor is dynamically updated

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
Copy of: 8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16

APAR status

• Closed as program error.

Error description

• When dynamic updates are made to the Liberty default
  executor, the runtime behavior is that a new executor
  instance is created with the new configuration settings and
  this new executor instance receives any newly submitted
  work.  The old executor instance is shut down, which means
  that new work cannot be submitted to it but old work can
  still finish.  However, timing windows exist such that a
  thread may still hold a reference to the old executor and
  may attempt to submit work to it.  This thread will
  improperly receive a
  java.util.concurrent.RejectedExecutionException.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: java.util.concurrent.RejectedExecutionE *
  *                      xception when default executor is       *
  *                      dynamically updated                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When dynamic updates are made to the Liberty default executor,
  the runtime behavior is that a new executor instance is created
  with the new configuration settings and this new executor
  instance receives any newly submitted work.  The old executor
  instance is shut down, which means that new work cannot be
  submitted to it but old work can still finish.  However, timing
  windows exist such that a thread may still hold a reference to
  the old executor and may attempt to submit work to it.  This
  thread will improperly receive a
  java.util.concurrent.RejectedExecutionException.
  

Problem conclusion

• Code was added that allows work to still be submitted to the old
  executor instance even after the new instance is in place.  The
  old executor will quiesce when its work has completed and there
  are no more references to it.
  
  The fix for this APAR is
  currently targeted for inclusion in fix pack 8.5.5.4.  Please
  refer to the Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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:

Fix information

• Fixed component name

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP