Fixes are available
APAR status
Closed as program error.
Error description
The application definition has mutiple subflow primitives. For example, a module called yourDocument_SP_Mediation. And the flow is demonstrated on below: yourDocument_SP_Mediation -> setCorrelationContext_SubFlow -> IPException_SubFlow3 -> IPAuditError_SubFlow When reaching the ServiceInvoke_auditError primitive in IPAuditError_SubFlow, CPU goes to 99%. There is no associated error in SystemOut. SystemErr has an entry "[3/09/12 11:08:00:467 EST] 0000008a SystemErr R FATAL ERROR: IXJXE0451E: [ERR 0400][ERR FORG0006] The argument type is not valid.; SystemID: unknown; Line#: 1; Column# 1". The ServiceInvoke_auditError primitive is defined to invoke Audit_InterfacePartner_JMS_Import component which is JMS binding in module yourDocument_SP_Mediation. And the JMS message will be sent to Audit_TS_JMS_Export (JMS binding) in module Audit_TS. And a Java component Audit_TS is wired to Audit_TS_JMS_Export to print the audit message. . But because the body is missing for the JMS Export binding, the jvm enters a loop. The CPU goes to 99%, the flow did not proceed beyond primitive ServiceInvoke_auditError in the IPAuditError_SubFlow, and never reaches IPAuditError_SubFlow.Trace3 in IPAuditError_SubFlow.
Local fix
When customer using JMS export binding with anytype as parameter. The body context may missing in request message.
Problem summary
**************************************************************** * USERS AFFECTED: Business Process Management Advanced users * **************************************************************** * PROBLEM DESCRIPTION: Message is missing when using JMS * * Export binding with an interface * * which using anytype as input * * parameter. * **************************************************************** * RECOMMENDATION: * **************************************************************** When using JMS Export with an interface which is using anytype as parameter, the message is incorrectly parsed by the export handler, thus resulting in the message body and context not propagating correctly and instead showing up as empty. The empty body can be verified by adding component folloing the JMS Export that prints the body.
Problem conclusion
The fix provided ensures that JMS Export with anytype as parameter is parsed correctly. Install/Dependency information is available in the readme.txt on FixCentral. When the user goes to the download files page in FixCentral, the readme will be available with the fix package as a separate download. The ifix can be downloaded from fix central
Temporary fix
Comments
APAR Information
APAR number
JR45031
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-05
Closed date
2013-02-27
Last modified date
2013-03-28
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 October 2021