APAR status
Closed as program error.
Error description
If audit settings are enabled in the Cloud Manager console and the configured endpoint is unreachable, the following error will be seen at the end of the previous container log for the management-apim pod and the container will be automatically be restarted: bhendi:error Unhandled promise rejection, error: Error: timeout of 15000ms exceeded bhendi:error - stack trace:: Error: timeout of 15000ms exceeded at createError (/app/node_modules/axios/lib/core/createError.js:16:15) at ClientRequest.handleRequestTimeout (/app/node_modules/axios/lib/adapters/http.js:303:16) at Object.onceWrapper (events.js:519:28) at ClientRequest.emit (events.js:400:28) at TLSSocket.emitRequestTimeout (_http_client.js:790:9) at Object.onceWrapper (events.js:519:28) at TLSSocket.emit (events.js:412:35) at TLSSocket.Socket._onTimeout (net.js:484:8) at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7) Promise { <rejected> Error: timeout of 15000ms exceeded at createError (/app/node_modules/axios/lib/core/createError.js:16:15) at ClientRequest.handleRequestTimeout (/app/node_modules/axios/lib/adapters/http.js:303:16) at Object.onceWrapper (events.js:519:28) at ClientRequest.emit (events.js:400:28) at TLSSocket.emitRequestTimeout (_http_client.js:790:9) at Object.onceWrapper (events.js:519:28) at TLSSocket.emit (events.js:412:35) at TLSSocket.Socket._onTimeout (net.js:484:8) at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7) { TypeError: Converting circular structure to JSON --> starting at object with constructor 'TLSSocket' | property 'parser' -> object with constructor 'HTTPParser' --- property 'socket' closes the circle at JSON.stringify (<anonymous>) at process.<anonymous> (/app/node_modules/bhendi/bhendi.js:149:60) at process.emit (events.js:412:35) at processPromiseRejections (internal/process/promises.js:245:33) at processTicksAndRejections (internal/process/task_queues.js:96:32)
Local fix
Address the connectivity issue to the configured audit endpoint or temporarily disable audit logging in the Cloud Manager settings.
Problem summary
Where http non-blocking auditing is enabled and there is an issue communicating with the configured http auditing endpoint, the apim pods may crash and restart.
Problem conclusion
Any failing asynchronous http calls to the audit endpoint are now caught correctly and will no longer cause the pod to crash. Fix is targeted for 10.0.1.7 and 10.0.5.0.
Temporary fix
Comments
APAR Information
APAR number
LI82564
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-16
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