| JUnit test class to expose the "All pipe instances are busy" error.
Run this class from two or more different computers (Linux and/or Windows)
so that multiple requests for the named pipe are hitting the server at the
same time. There are many factors that exacerbate the issue, although
using SQL Server 6.5, slow (higher latency) TCP/IP connections and adding
more computers hitting the server simultaneously seem to be the top three.
See also
INF: Multiple Named Pipes Connections May Cause Error 17832 on
Microsoft's knowledgebase web site.
author:
David D. Kilzer
version:
$Id: TestAllPipeInstancesAreBusy.java,v 1.2 2005/09/06 22:57:08 ddkilzer Exp $ |