PI46281: NullPointerException in batch JobOperatorImpl after dynamic serv er configuration change involving batch or its dependencies.

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
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 using the batch features, after making a change to the
  server configuration causing a restart of one or more
  components
  of the batch feature, a NullPointerException in the
  com.ibm.jbatch.container.api.impl.JobOperatorImpl class may
  be seen.
  
  This might be seen, for example, when using the
  javax.batch.operations.JobOperator API provided by the
  "batch-1.0" feature.
  
  For example, here is an exception stack trace when the
  "start" method of JobOperator is invoked.
  
  ERROR: java.lang.NullPointerException
  javax.batch.operations.JobStartException:
  java.lang.NullPointerException
  at
  com.ibm.jbatch.container.api.impl.JobOperatorImpl.start(JobO
  peratorImpl.java:178)
  at
  com.ibm.jbatch.container.api.impl.JobOperatorImplSuspendTran
  .start(JobOperatorImplSuspendTran.java:156)
  at
  
  Typically this would be occur after a (subsequent)
  CWWKY0008I message appears in messages.log, after the
  configuration change.
  
  This message appearing a second time in messages.log (the
  first time corresponding to the initial activation of the
  feature),
  would indicate that the batch kernel component had
  reinitialized (after a configuration change involving the
  batch components themselves or components which are part of
  the
  batch dependency tree).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the batch features within the      *
  *                  Libery profile of IBM WebSphere Application *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: NullPointerException in batch           *
  *                      JobOperatorImpl after dynamic           *
  *                      modification of server config forcing   *
  *                      restart of batch components.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the batch features, after making a change to the
  server configuration causing a restart of one or more
  components
  of the batch feature, a NullPointerException in the
  com.ibm.jbatch.container.api.impl.JobOperatorImpl class may be
  seen.
  
  This might be seen, for example, when using the
  javax.batch.operations.JobOperator API provided by the "batch-
  1.0" feature.
  
  Here is an exception stack trace when the "start" method of
  JobOperator is invoked.
  
  ERROR: java.lang.NullPointerException
  javax.batch.operations.JobStartException:
  java.lang.NullPointerException
   at
  com.ibm.jbatch.container.api.impl.JobOperatorImpl.start(JobOpera
  torImpl.java:178)
   at
  com.ibm.jbatch.container.api.impl.JobOperatorImplSuspendTran.sta
  rt(JobOperatorImplSuspendTran.java:156)
   at
  
  Typically this would be occur after a (subsequent) CWWKY0008I
  message appears in messages.log, after the configuration
  change.
  
  This message appearing a second time in messages.log (the first
  time corresponding to the initial activation of the feature),
  would indicate that the batch kernel component had reinitialized
  (after a configuration change involving the batch components
  themselves or components which are part of the
  batch dependency tree).
  

Problem conclusion

• The dependency on the BatchSecurityHelper was changed from
  OPTIONAL to MANDATORY.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Recycling the server after such a server configuration change
  should bypass this problem.
  

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

  LIBERTY PROFILE

• Fixed component ID

  5724J0814

Applicable component levels

• R850 PSY

     UP