SBL-SMI-00122

Applies to:

Siebel System Software - Version: 7.5.2 [16008] to 7.8 [19038] - Release: V7 to V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (MidMarket)
Version: 7.5.2.100 [15252] MME
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2

This document was previously published as Siebel SR 38-1264811081.

Symptoms

SBL-SMI-00122Hi
I am seeing following errors on Object Manager logs:

"GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp 9(285) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 285) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp 9(640) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 640) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog    GenericError    1    2004-04-27 22:17:42    (smimtpool.cpp 50(1483) err=2100122 sys=0) SMI-00122: Internal: Error 28758 from SessionHandleMessage()"

I need to understand what it means.

Cause

.

Solution

Message 1

For the benefit of other readers:

The customer was seeing the following error messages in the Object Manager log files:

"GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp 9(285) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 285) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp 9(640) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 640) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

GenericLog    GenericError    1    2004-04-27 22:17:42    (smimtpool.cpp 50(1483) err=2100122 sys=0) SMI-00122: Internal: Error 28758 from SessionHandleMessage()"

The “GEN-28758” error message is usually related to failing connections. Bug ID 10448885 has been raised requesting more informative message when this behavior happens.

The customer executed the environment verification tool (evt) on this environment, and it requested to change some TCP parameters and the SERVER_INACTIVE_CONN_TIMEOUT variable.

Please refer to "Environment Verification Tool (EVT) Overview (Doc ID 477105.1)" on My Oracle Support for further information regarding this tool and "What is true benefit, if any, of changing TCP registry parameters as recommended by EVT? (Doc ID 499134.1)" for details about TCP parameters change.

After these, the customer re-started the Siebel Server machine and the messages have gone away.

Thank you.

Applies to:

Siebel System Software - Version: 7.5.3 [16157] to 8.1.1.4 [21225] - Release: V7 to V8
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9i
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1228086491.

*** Checked for relevance on 04-May-2011 ***

Symptoms

SBL-SMI-00122Users are getting session timeout message randomly. The error in the task log is:
SBL-SMI-00122: Internal: Error 28758 from SessionHandleMessage()

We need to fix this ASAP.

Cause

Environment specific 

Solution

Customer determined the timeouts appear to be related to the application object manager parameter, SISNAPI Connection Maximum Idle Time (alias ConnIdleTime) which had been set to 0 and timing out after 30 seconds

Under 7.5.2, the behavior for ConnIdleTime = 0 or -1 meant, no timeouts.

Under 7.5.3, setting ConnIdleTime
- between 0 and including 30 = 30 seconds timeout.
- by setting it to -1, this means there is no timeout which is not something you want either especially if a firewall is present.

It is recommended where there is a firewall between the application and web server, and firewall timeout is set: the value should be set to a value slightly less than the firewall timeout value.
Therefore, if firewall has a timeout value of 3600 seconds (1 hour), then the ConnIdleTime parameter should be less than 3600 seconds. The recommended value for the ConnIdleTime parameter is between 300 seconds and 3600 seconds.

Your setting will be based on your business needs.

In summary:
1- Set it ONLY for Application ObjMgr's and EAIOBJMgr's
2- Set it ONLY when Resonate is being used for load balancing Siebel Server's
3- Do NOT set it for components that belong to "System Management" group.
4- Value should always be less than firewall timeout.
5- Optimal value lies between 300 and 3600

More information can be found on ConnIdleTime in BookShelf's Server Administration Guide for 7.5.3