APAR status
Closed as program error.
Error description
The webhook state for a webhook subscription id can get stuck in online_pending when the send task associated with that webhook encounters a 500 database error. The 500 database error will not be in the logs with the default level of tracing; however, the following exception can be found in the task manager pod logs: apim:webhook:audit [<request_id>] Mark send task failed as as webhook subscription does not exist for webhook url /api/cloud/webhooks/<webhook_id> for task <task_id>
Local fix
Problem summary
A database error was causing a send tasks to be marked as permanently failed. As a result no new events are sent to gateways or portal and user actions in the manager are not reflected on the gateways or portal.
Problem conclusion
The issue was fixed by a better handling of database errors. <span style="background-color:rgb(255, 255, 255)">Fixed in 10.0.1.7, 10.0.5.0</span>
Temporary fix
Comments
APAR Information
APAR number
LI82572
Reported component name
API CONNECT ENT
Reported component ID
5725Z2201
Reported release
A0X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-03-28
Closed date
2022-07-12
Last modified date
2022-09-08
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
API CONNECT ENT
Fixed component ID
5725Z2201
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 September 2022