Fixes are available
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.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
When JVM restarts and JobScheduler EJB's are not started yet prior to performing a context.lookup() an exception occurs
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server and the batch function of WebSphere * * Application Server V8.5. * **************************************************************** * PROBLEM DESCRIPTION: Occasionally, after the JVM hosting the * * JobSchedulerMDB is restarted an error * * occurs * * Login failure during job submission: * * java.lang.RuntimeException: * * JobSchedulerMDB.SecureSubmitter: caught * * exception java.lang. * * NullPointerException * **************************************************************** * RECOMMENDATION: * **************************************************************** This is the error seen: "Login failure during job submission: java.lang.RuntimeException: JobSchedulerMDB.SecureSubmitter: caught exception java.lang. NullPointerException" The issue here is that the JobScheduler EJB's are occasionally not given enough time start up after being restarted. If a job is submitted before they are started the errors mentioned above will occur.
Problem conclusion
Added a check to see if the JobScheduler EJBs have started yet. This will check three times allowing the EJB's to start before the job is submitted. Three is the standard amount of retries typically used. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
An interim fix is available upon request.
Comments
APAR Information
APAR number
PI28981
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-11-04
Closed date
2015-01-27
Last modified date
2015-05-27
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022