home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky u3b.misc:32 comp.unix.wizards:3903 comp.unix.questions:11035
- Newsgroups: u3b.misc,comp.unix.wizards,comp.unix.questions
- Path: sparky!uunet!stanford.edu!agate!spool.mu.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsi!mbg
- From: mbg@cbnewsi.cb.att.com (mitchell.b.germansky)
- Subject: ---<<< Wollongong 3B2 TCP select() bug?? >>>---
- Organization: AT&T
- Date: Mon, 14 Sep 1992 15:27:34 GMT
- Message-ID: <1992Sep14.152734.15441@cbnewsi.cb.att.com>
- Followup-To: poster
- Keywords: Wollongong WIN TCP/IP select() ShareBase IDM Britton-Lee Teradata NCR
- Lines: 27
-
- my project has encountered what seems to be a problem in wollongong's
- tcp/ip on a 3b2. if you have any experience in resolving this,
- please get in touch with me.
-
- we have a 3b2 connected over ethernet to a sharebase database
- machine (aka britton-lee idm, teradata, ncr). we are using
- Wollongong Integrated Networking WIN/3B: Release 3.2A on 3b2
- unix 3.2.3
-
- we have noticed a predictable 2 second delay every 20 database
- transactions. examining the process stack trace during this 2
- second interval revealed that the process was asleep in a tcp/ip
- library select() call. we believe that this problem is really
- independent of the database and will write some tcp code to attempt
- to reproduce the select() delay. the sharebase performance is
- constant even for the transaction that blocks for the 2 seconds.
-
- we have heard rumors that other people have had similar problems.
- we are wondering if there are any workarounds or perhaps even a
- patch available.
-
- if you have any suggestions, please contact me via email or phone.
- thx!!
-
- --
- Mitch Germansky 908-805-7841
- att!suntoss!mbg mbg@suntoss.utoss.290davidson.att.com
-