Yesterday I put a new a context consisting of a few JSP, Beans and 
servlets into production on my TC5.019 being integrated with IIS using 
JK2.04 all of it running on a Windows 2000 machine.

The result was that Tomcat refused display JSP located in another context 
letting the browser hang forever when requesting the pages. After Googling 
a bit around I tried to remove any reference to the load balander in my 
workers2.properties file at which point the pages would display again. 
Hitting the above mentioned pages using port 8080 worked just fine for 
what reason it seems to be the IIS integration being mucked up.

I know this may sound kinda weird and would therefore like to ask whether 
anyone have had a similar experience?

After removing the load balancer reference these have started to appear in 
my jk2.log file:
[jk_channel_apr_socket.c (488)]  channelApr.receive(): Error receiving 
message body -1 0
[jk_workerEnv.c (492)]  workerEnv.processCallbacks() Error reading reply
[jk_worker_ajp13.c (546)]  ajp13.service() ajpGetReply recoverable error 
120000

They dont seem do to any harm but nevertheless I would like to get rid of 
them as well as understand why they appear?

Best regard Thomas

<FONT SIZE=1 FACE="Arial">_______________
Vi goer opmaerksom paa, at denne e-mail kan indeholde fortrolig information. Hvis du 
ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om 
fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit 
system uden at videresende eller kopiere den.
Selv om e-mailen og ethvert vedhaeftet bilag efter vores overbevisning er fri for 
virus og andre fejl, som kan paavirke computeren eller it-systemet, hvori den modtages 
og laeses, aabnes den paa modtagerens eget ansvar. Vi paatager os ikke noget ansvar 
for tab og skade, som er opstaaet i forbindelse med at modtage og bruge e-mailen.
_______________
Please note that this message may contain confidential information. If you have 
received this message by mistake, please inform the sender of the mistake by sending a 
reply, then delete the message from your system without making, distributing or 
retaining any copies of it.
Although we believe that the message and any attachments are free from viruses and 
other errors that might affect the computer or IT system where it is received and 
read, the recipient opens the message at his or her own risk. We assume no 
responsibility for any loss or damage arising from the receipt or use of this message.
</FONT>

Reply via email to