PI46300: A call to the Batch REST interface to restart a job fails when t he job was previously started via the JobOperator.

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

• This problem surfaces as an Error 500 when the REST call is
  made. In the logs an FFDC listing for a
  java.lang.IllegalStateException and a
  com.ibm.ws.jbatch.rest.bridge.BatchContainerAppNotFoundExcep
  tion detailing a failure to load application context can be
  seen. When the application context in the
  IllegalStateException is listed it has both the EJB and WEB
  prefixes.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A call to the Batch REST interface to   *
  *                      restart a job fails when the job was    *
  *                      previously started via the              *
  *                      JobOperator.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This problem surfaces as an Error 500 when the REST call is
  made. In the logs an FFDC listing for a
  java.lang.IllegalStateException and a
  com.ibm.ws.jbatch.rest.bridge.BatchContainerAppNotFoundException
  detailing a failure to load application context can be seen.
  When the application context in the IllegalStateException is
  listed it has both the EJB and WEB prefixes.
  

Problem conclusion

• This problem was fixed by altering the application context used
  to remove the extraneous qualifiers.
  
  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

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