||unity-dev|| New connections failing after having a lot of users

Hi,

I'm not sure if this is caused by a bug in our application, or if it's a
problem with unity itself...but we got to about 100 concurrent users, and
Unity stopped sending a response to our createNamespace command.

Usually, we will send createNamespace, and get a upcOnCreateNamespace in
response, with a 'NAMESPACE_EXISTS' as the response code.

This time, our app would send a createNamespace command, but we would not
get any response about the namespace.

Here is a log from a network traffic capture. Lines beginning with 'S' are
sent by the server, lines with 'C' are sent by the client. the period at the
end of each line represents the null terminator. This was the entire traffic
from when we connected, then our app would hang (because it assumes it will
always get a response to createNamespace, and so it does not have timeouts
or anything like that)

S: <UPC><METH>upcSetClientID</METH><ARGS><ARG>1235</ARG></ARGS></UPC>.

S:
<UPC><METH>upcOnClientAttributeUpdate</METH><ARGS><ARG>null</ARG><ARG>null</ARG><ARG>1235</ARG><ARG>_IP</ARG><ARG>
216.27.176.249</ARG></ARGS></UPC>.

C:
<UPC><ROOMID>unity</ROOMID><METH>createNamespace</METH><ARGS><ARG><![CDATA[simadmin]]></ARG><ARG>true</ARG></ARGS></UPC>.

S:
<UPC><METH>upcOnClientAttributeUpdate</METH><ARGS><ARG>null</ARG><ARG>null</ARG><ARG>1235</ARG><ARG>_CONNECTTIME</ARG><ARG>1200605661372</ARG></ARGS></UPC>.


We are working on stress-testing our app with large numbers of users, is
there anything we should try the next time we organize a test like this?

Thanks!
-David R