E1: BSSV: BSSV and Call Object Kernel (COK) Recycling and Kernel going zombie
(Doc ID 1202613.1)
Last updated on SEPTEMBER 10, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 8.98 to 9.1 [Release 8.98 to 9.1] Information in this document applies to any platform.
Symptoms
When a BSSV invokes a BSFN, the BSFN will be executed on a Call Object Kernel (COK) kernel. Now let us assume that the COK kernel to which BSSV had initially connected to has gone zombie or it has been kernel recycled.
Now if a new BSSV request is submitted, then that particular BSSV transaction will fail with an error - "JdeNetAssociatedKernelException: Kernel for associated message not exist error." A subsequent re-submission of the BSSV transaction will be successful.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!