Some more info on this.
The problem appears to occur if a client issues a ListDomainsRequest with
MaxNumberOfDomains set, and MaxNumberOfDomains is less than the actual
number of domains. For example, if there are 4 domains in M/DB, and you do
a ListDomains with MNOD=3, then the request times out; if you do MNOD=4, it
I can reproduce this using a console application written directly against
the .NET AWS SDK, i.e. the issue is not specific to SimpleDB Management
Tools. From the trace, it looks like M/DB isn't sending a response (e.g. it
doesn't print a BoxUsage line), so I think the problem is in M/DB rather
than in the AWS SDK.
The reason this affects SimpleDB Management Tools is that we send a
ListDomainsRequest with MNOD=1 as part of connectivity checking. So it
falls foul of this if there is more than one domain. I can provide Thomas
with a workaround by bumping up the MNOD on our connectivity check, but I'd
prefer not to have to do this as it's wasteful for other users who are
talking to a 'real' SimpleDB endpoint.
Hope this helps -- let me know if you need any more info.