Fixes are available
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
With 17.0.0.2, the following occurs when running a job with no id under WOLA and batchSMFLogging-1.0 feature enabled. However, this works when using BatchManger or the REST interface or the batchSMFLogging feature is removed. batch.container.controller.impl.WorkUnitThreadControllerImpl CWWKY0035I: An exception occurred while trying to persist job execution status and related data. java.lang.IllegalStateException: No match found .at java.util.regex.Matcher.group(Matcher.java:547) .at com.ibm.ws.jbatch.smflogging.internal.JBatchSMFLogging.getUs sSec tion(JBatchSMFLogging.java:1914) Will see FFDC files created like this: FFDC1015I: An FFDC Incident has been created: "com.ibm.jbatch.container.exception.BatchIllegalJobStatusTra nsit ionException: Job execution: 201 cannot be transitioned from Batch Status: COMPLETED to FAILED com.ibm.jbatch.container.services.impl.JPAPersistenceManager Impl $10 989"
Local fix
This message can be ignored as it is not causing the job to fail.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty- Batch * **************************************************************** * PROBLEM DESCRIPTION: When a SMF record is being collected * * for a java batch user that has no OMVS * * segment defined, a parsing error is * * encountered gathering USS information * * for the SMF record * **************************************************************** * RECOMMENDATION: * **************************************************************** Because it is valid for a z/OS user to have no OMVS segment defined, the USS information for the user will be null. The java batch SMF recording logic which gathers USS data as part of the records being produced did not account for this fact. The null values encountered causes the following parse exception as SMF gathers USS data, which will be seen in an FFDC record: java.lang.IllegalStateException: No match found .at java.util.regex.Matcher.group(Matcher.java:547) .at com.ibm.ws.jbatch.smflogging.internal.JBatchSMFLogging.getUssSec tion(JBatchSMFLogging.java:1914) .at com.ibm.ws.jbatch.smflogging.internal.JBatchSMFLogging.buildAndW riteJobEndRecord(JBatchSMFLogging.java:320) .at com.ibm.jbatch.container.execution.impl.RuntimeJobExecution.work Ended(RuntimeJobExecution.java:197) .at com.ibm.jbatch.container.controller.impl.WorkUnitThreadControlle rImpl.persistWorkUnitBatchAndExitStatus(WorkUnitThreadController Impl.java:297) .at com.ibm.jbatch.container.controller.impl.WorkUnitThreadControlle rImpl.endOfWorkUnit(WorkUnitThreadControllerImpl.java:269) .at com.ibm.jbatch.container.controller.impl.WorkUnitThreadControlle rImpl.executeWorkUnit(WorkUnitThreadControllerImpl.java:187) .at com.ibm.jbatch.container.controller.impl.WorkUnitThreadControlle rImpl£AbstractControllerHelper.runExecutionOnThread(WorkUnitThre adControllerImpl.java:480) .at com.ibm.jbatch.container.controller.impl.WorkUnitThreadControlle rImpl.runExecutionOnThread(WorkUnitThreadControllerImpl.java:89) .at com.ibm.jbatch.container.util.BatchWorkUnit.run(BatchWorkUnit.ja va:117) .at com.ibm.ws.context.service.serializable.ContextualRunnable.run(C ontextualRunnable.java:80) .at java.util.concurrent.Executors£RunnableAdapter.call(Executors.ja va:522) .at java.util.concurrent.FutureTask.run(FutureTask.java:277) .at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1160) .at java.util.concurrent.ThreadPoolExecutor£Worker.run(ThreadPoolExe cutor.java:635) .at java.lang.Thread.run(Thread.java:785)
Problem conclusion
The java batch SMF recording logic was updated to tolerate a non existent uid or gid value in the case that no OMVS segment is defined for a particular user. The SMF record for either uid or gid will be set to a known max negative value if not present. The fix for this APAR is currently targeted for inclusion in fix pack 18.0.0.2 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 number
PI90716
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-28
Closed date
2018-05-25
Last modified date
2018-05-25
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 PROF -
Fixed component ID
5655W6514
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022