>From my experience, this sort of problem occurs when you are errantly
passing user reference values. I'm sure you've checked this, but I would
recommend checking again. Not even with Tango 2000 was I ever able to
blame the software for this sort of error, and I've seen it a few times
and even grew some grey hair over it. Caching or code problems always
turned out to be the problem.
Perhaps there is someone else who could also spend some time checking,
as it's very easy to miss a problem in your own code just to realize you
have a syntax problem or something similar. Also, if you are passing
user references via JavaScript, you may be passing cached values. Maybe
we'll hear from Ian Daniel regarding caching.
Your thread pool size isn't likely to affect user references or
variables, and I think you could be wasting this critical time bothering
with that setting. In a recent thread, someone had mentioned testing the
setting and found it to actually decrease performance of the server,
although I may be taking that out of context.
If the application is fairly simple I could have a look for you, but I'm
pretty busy with work tonight and may not be able to devote the time
required.
- Jake Stevens
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
