PI10656: EJB COMMUNCATION FROM ENDPOINT TO SCHEDULER DOES NOT RECOVER FROM PREVIOUS FAILURE

8.0.0.4: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 4
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
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.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
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
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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• EJB communcation from Endpoint to Scheduler does not recover
  from previous failure
  
  Endpoint logs shows the following exception when trying to
  reach the scheduler:
  
  java.security.PrivilegedActionException: java.lang.Exception:
  Could not access JobScheduler EJB
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of WebSphere Extended Deployment      *
  *                  Compute Grid V8 and the batch function of   *
  *                  WebSphere Application Server V8.5 who use   *
  *                  the parallel job manager function.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: EJB communication from endpoint to      *
  *                      scheduler does not recover after a      *
  *                      failure; therefore, all subsequent      *
  *                      job submissions fail until the          *
  *                      endpoint servers are recycled.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The list of available schedulers for the endpoint to call was
  not being reset when new schedulers were added or others
  recovered.  Therefore, if the initial list of
  available schedulers was exhausted due to a communications
  failure, the endpoint to scheduler communications would never
  recover.
  

Problem conclusion

• The code has been updated to refresh the list of available
  schedulers when new ones are added or others recover.
  The fix for this APAR is currently targeted for inclusion in
  fixpack 8.0.0.4. Please refer to the Recommended Updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?uid=swg27022998
  

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

  WXD COMPUTE GRI

• Fixed component ID

  5725C9301

Applicable component levels

• R800 PSY

     UP