Direct link to fix
APAR status
Closed as program error.
Error description
It takes longer than expected for IBM Workflow Server to getStatusLocal from the deployment manager. As a result, you might not be able to create a process instance and you see the following message in IBM Process Portal: "The process did not launch within 60 seconds."
Local fix
Problem summary
This issue occurs because the deployment manager searches all nodes in a cell for MBeans when a query scope is not specified, which might take a long time depending on the network and the number of nodes in a cell. Because the MBean being queried is only on the deployment manager, the query scope should be narrowed to the local deployment manager server. PRODUCT AFFECTED: IBM Business Automation Workflow
Problem conclusion
A fix that narrows the search scope to just the dgmr server, thereby improving performance, is planned for inclusion in a future release of Business Automation Workflow.
Temporary fix
Comments
APAR Information
APAR number
JR61952
Reported component name
BUS AUTO WORKFL
Reported component ID
5737H4100
Reported release
K00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-02-03
Closed date
2020-03-16
Last modified date
2020-03-16
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
BUS AUTO WORKFL
Fixed component ID
5737H4100
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"20.0.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 June 2020