Paul Pree schrieb: > Thanks Rainer > I've attached a log recorded during one of these failing connects for > TestUser. We stopped IIS, set logging to trace, cleared the log, started > IIS, attempted one connect, then stopped. > > Unfortunately I don't have direct access to the failing site, but have > been trying to resolve this for some time now so hopefully have already > collected anything that might assist in pinpointing the problem. > Note that we copied the Windows account of a failing user, then started > stripping Windows groups. The starting point was over 150 groups. When > that user was dropped to 69 it started working. Adding back another > group brought back the failure. Other users with up to 90 groups could > connect, but some with 50 could not. Group complexity (maybe even name > length) definitely has an impact so it's not necessarily 'death at 70' > but each test users has a working number that fails with the addition of > one.
Yes, it looks like a header size problem. Look at the description of max_packet_size on http://tomcat.apache.org/connectors-doc/reference/workers.html You can set it to some bigger value than the default. We don't know though, how much you actually need (try and error). Be careful to also adjust the Connector in server.xml as described in the docs page. Remark: your isapi redirector is version 1.2.25 (that's what the log file says). I would recommend updating to 1.2.26, or even 1.2.27 (though that version was just released on Monday). Let us know, if max_packet_size plus packetSize fixes your problem. Regards, Rainer --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
