E1: KER: Error "No available SFU connection! Increase maxSFUConnection INI setting" in Server Log and Call Object Kernels Go Zombie (Doc ID 648503.1)

Last updated on AUGUST 29, 2022

Applies to:

Symptoms

The value for parameter maxSFUConnection has been increased from 3 to 5 in section [DB SYSTEM SETTINGS] of the Enterprise Server JDE.INI file.   Users experience issues when they enter 2 orders the 3rd order fails.  Users logout and back in but the issue persists; 2 orders are entered, the third fails. 

After running the server program update and changing the SFU connections to 5, users test again and each user entering orders is able to enter 4 orders in a row but the 5th order fails.  The server JDE.LOG shows the error:

If a user runs a UBE, it updates 4 orders then stops with the same error in the log.   The value is increased to 300 and the Enterprise Server bounced.  With this change, users are able to get in 8 orders without issue.  It seems that the system is not reusing connections but instead needs a new one for each entry. 

With the parameter set to 300, users are logging out of E1 every 1-2 hours a day and also keeping batches small in order to continue processing the entire work day. 

Additional Symptoms:

• The number of active jobs and waiting jobs are increasing and can be seen in Server Manager Console. 
• Call Object Kernels go into zombie status.
• Connections are not being reused.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.