[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1746.0. "mismatched session sequence numbers" by GIDDAY::WALKER () Wed Feb 12 1997 22:43

Hello,

Could someone please give me an explanation for the following messages:

net3100: Operation failed because a network software occured.

Listener task: mismatched session sequence numbers.


Customer is seeing these messages several times a day.
All clients (about 6) are disconnected and PATHWORKS must be restarted to
recover.
Customer is running 5.0g ECO1.

Looking in COMET I see many queries/escalations about these messages but no
good explanation about what they are or how they can be resolved.

Can anyone help?

Thanks,
Richard Walker.
T.RTitleUserPersonal
Name
DateLines
1746.1CPEEDY::HORGANCraicailte indiadh damhsa agus cricta�l!Mon Feb 17 1997 16:3211
Mismatched sequence number messages are usually caused by not having enough
knb sessions configured in the kernel.  The knb sessions configured
need to be much more than the number of clients connecting.  This is because
when you configure sessions, you are actually configuring control blocks and 
there are multiple control blocks used when sessions are established.  If you 
have a lot of lients connecting simultaneously (like when the server comes back
up after a problem), you can easily exceed the number of knb control blocks
available.  When you installed eco1 was the kernel tuned correctly or did the
customer go back to the defaults?

Julia