well yes. but you know since i first had a similar problem about 3-4 months ago i've followed most threads where other people had similar problems. and in most cases i never saw a clear cut solution. i'm beginning to think it's the connectors that need to be put out of their misery.
-----Original Message----- From: John Turner [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 4:17 PM To: Tomcat Users List Subject: Re: Connectors for IIS/Tomcat SHOULD make sense I think you should take a 12 ga. shotgun and put that server out of its misery. John On Thu, 26 Jun 2003 04:13:24 +0800, Jason Bainbridge <[EMAIL PROTECTED]> wrote: > The saga continues... > > Can you add the below to your workers.properties? > > worker.ajp13.lbfactor=50 worker.ajp13.cachesize=10 > worker.ajp13.cache_timeout=600 worker.ajp13.socket_keepalive=1 > worker.ajp13.socket_timeout=300 > > Also try renaming your worker to something other than ajp13 it could be > confusing the server. > > I'm starting to run out of ideas, like I so often do with anything IIS > related.... > -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
