Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

WaitHandles error

46 views
Skip to first unread message

Grant Davidson

unread,
Aug 30, 2004, 10:59:01 AM8/30/04
to
Hi,
I have a quite large number of Subscription Classes spread
over two applications in one instance.
The first Application works okay, however the second
application generates the following event message(abridged)

<Description>
The number of WaitHandles must be less
than or equal to 64.
</Description>

First instinct is that this is a NS bug (or issue) and
that my solution would be to split the applications into
two different instances so that the total number of
subscriptionClasses per Instance is less than 64...but
it's just a guess. The events documentation says that a
4085 bug is an internal NS bug and to restart the
service..which doesn't make a difference. Does anyone know
or come across this before? Is their any major problem
with having two instances at the same time (apart from the
additional work needed for Subscriber management)?

Thanks in advance for any help,
Grant Davidson

Colin Meek [MSFT]

unread,
Sep 1, 2004, 2:34:46 PM9/1/04
to
This is a known issue with the product. You must restrict the number of
subscription classes and event classes combined to less than 64. The total
number of rule actions and notification classes is similarly restricted.

The restriction is imposed by .NET's WaitAll synchronization method, used in
the NS generator.

-Colin Meek [MSFT]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
--

"Grant Davidson" <anon...@discussions.microsoft.com> wrote in message
news:08d901c48ea1$e25c11a0$a401...@phx.gbl...

Joe Webb

unread,
Sep 1, 2004, 7:52:39 PM9/1/04
to
Any word on whether VS.NET 2005 with the Framework 1.2 will address this?

Thanks!
Joe Webb

Colin Meek [MSFT]

unread,
Sep 2, 2004, 1:40:03 AM9/2/04
to
The problem has been addressed for the Sql Server 2005 version of NS.

As far as I know, the .NET behavior will remain unchanged for 2005.

-Colin Meek [MSFT]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.

--
"Joe Webb" <jo...@webbtechsolutions.com> wrote in message
news:OpCjptH...@tk2msftngp13.phx.gbl...

Grant Davidson

unread,
Sep 3, 2004, 8:00:54 AM9/3/04
to
Thanks for the reply,
I'm coding around the issue.
Once again thanks,
Grant
>.
>
0 new messages