Siebel Administration >  SMI-00081: Internal: Got error 1801210 when dequeueing a connection request (62)

SMI-00081: Internal: Got error 1801210 when dequeueing a connection request (62)

The error is most likely reported by a Siebel object manager server component. Upon encountering this error, it is continually reported in the log file (repetitive), causing it to grow and take on available disk space leading to performance degradation.

Cause

This behavior has been mostly noticed on Unix platforms when the number of Siebel object managers enabled exceeds a certain threshold (62 in this case). The log messages are generated in consequence of product defect (CR 10641052) where the /bin/ksh shell interpreter closes a tcp/ip socket used by one of the object manager processes. This process whose port is closed can no longer process any incoming requests and starts to report this error.

Diagnostic Steps

The error will manifest itself in the specific Siebel object manager log file or in the master Siebel log (<$Enterprise_Server>.<$Siebel_Server>.log) file. Identify if users have a significant number of Siebel object managers active, enabled and running on this server (the number equals that reported in the error message within parenthesis).

Solution

The following workarounds are suggested to overcome this product defect/error message:

Disable unused object managers so as to reduce the number of object managers being used [less than indicated number in error message].

In the event that this is not possible, user would have to edit the following shell script:$SIEBEL_ROOT/bin/siebmtshw
Instructions– Replace the first line from "#!/bin/ksh" to "#!/bin/sh" and restart the Siebel server services. This will allow the "sh" interpreter to be used as opposed to the "ksh" interpreter.