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. Regards Paul -----Original Message----- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: Friday, 7 November 2008 9:46 AM To: Tomcat Users List Subject: Re: ISAPI_REDIRECT issue Paul Pree schrieb: > Hi All > > Apologies in advance if I'm not getting this right - I'm a newbie to the > list..... > > I have an issue using ISAPI_REDIRECT through IIS to Tomcat. > > For most Windows users the redirection works fine, but for users with > large group memberships (approx 70+) they are not redirected and nothing > is logged in the ISAPI log. > > I've been working with Microsoft and from the IIS side all appears well. > > They believe it is an HTTP Header size issue. > > > > Environment: > > Windows 2003 32 bit > > Tomcat 5.5.25 > > Java JDK 1.5.0_16 > > ISAPI Redirect v 1.2.26 (Precompiled DLL for win32) > > I believe that the HTTP header is fixed at 8k. Can anyone give me a tip > on how this can be increased? I've seen reference to it being possible, > but just not how. Is it a parameter I set in Tomcat on the 8009 > connector? Is it something I can set in the uri properties file (I think > not)? Do I need to download the source and adjust it in there and build > my own DLL? First we should check, whether it is really a header size issue. We should be able to verify that by logging a failing request done by one of those users with log_level trace. Please do not log a lot of requests, because trace log level produces very much output. Especially it logs the packets which get send to the backend, so we can see, whether the headers are to big. I hope you have a system, where you can do such a test? 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]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
