Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 55193 invoked from network); 26 Feb 2004 23:13:02 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 26 Feb 2004 23:13:02 -0000 Received: (qmail 64114 invoked by uid 500); 26 Feb 2004 23:12:06 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 64017 invoked by uid 500); 26 Feb 2004 23:12:05 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 63965 invoked from network); 26 Feb 2004 23:12:05 -0000 Received: from unknown (HELO fox.essential.com.au) (203.8.163.157) by daedalus.apache.org with SMTP; 26 Feb 2004 23:12:05 -0000 Received: by fox.essential.com.au with Internet Mail Service (5.5.2657.72) id ; Fri, 27 Feb 2004 09:41:50 +1030 Message-ID: From: Kent Boogaart To: "'tomcat-user@jakarta.apache.org'" Subject: RE: JK2 config problem [RESOLVED] Date: Fri, 27 Feb 2004 09:41:49 +1030 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hmmm, I didn't forget the attachments but this mail list must not support attachments . . . So here is my original workers2.properties file: //////////////////////////////////////////////////// [logger] level=DEBUG [shm] file=d:/tomcat41/temp/shm.txt size=1048576 # dev communication channel [channel.socket:203.8.163.164:8009] info=channel for dev # dev worker [ajp13:203.8.163.164:8009] channel=channel.socket:203.8.163.164:8009 # sys test communication channel [channel.socket:203.8.163.166:8010] info=channel for sys test # sys test worker [ajp13:203.8.163.166:8010] channel=channel.socket:203.8.163.166:8010 # map all dev requests to dev worker [uri:203.8.163.164/*] info=map all group=ajp13:203.8.163.164:8009 # map all sys test requests to sys test worker [uri:203.8.163.166/*] info=map all group=ajp13:203.8.163.166:8010 //////////////////////////////////////////////////// And here is the simplified one: //////////////////////////////////////////////////// [logger] level=DEBUG [shm] file=d:/tomcat41/temp/shm.txt size=1048576 # dev communication channel [channel.socket:localhost:8009] info=channel for dev # dev worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # sys test communication channel [channel.socket:localhost:8010] info=channel for sys test # sys test worker [ajp13:localhost:8010] channel=channel.socket:localhost:8010 # map all dev requests to dev worker [uri:203.8.163.164/*] info=map all group=ajp13:localhost:8009 # map all sys test requests to sys test worker [uri:203.8.163.166/*] info=map all group=ajp13:localhost:8010 //////////////////////////////////////////////////// Regards, Kent -----Original Message----- From: Subir Sengupta [mailto:subir@walmart.com] Sent: Friday, 27 February 2004 6:08 AM To: Tomcat Users List Subject: RE: JK2 config problem [RESOLVED] Did you forget the attachment? -----Original Message----- From: Kent Boogaart [mailto:kb@essential.com.au] Sent: Wednesday, February 25, 2004 7:30 PM To: 'tomcat-user@jakarta.apache.org' Subject: JK2 config problem [RESOLVED] Typical - as soon as I post I figure it out. All I had to do was alter the second IIS site so that the 'jakarta' virtual directory points to the same location as the first site (D:\tomcat41\bin\native\). With that modification, the existing workers2.properties file correctly forwards requests based on the host IP. In fact, the workers2.properties file can be simplified even further to be more readable. A simplified version is attached. Hope this info is useful to others . . . Regards, Kent Hello all, Here's my problem: I would like to have two Tomcat processes running on the one machine, each with a my web-app available via the default context ("/"). Furthermore, I would like each site to be available via IIS. I have tried for days to get this up and running but with no luck. I could not find any substantial documentation on workers2.properties configuration anywhere. Therefore I have been cross-referencing with JK1 configuration and with the JK2 source code. Following is my set up. Tomcat 1 -------- Directory: D:\tomcat41\ Name: Development The jk2.properties for this tomcat contains: channelSocket.port=8009 The workers2.properties for this tomcat (which is shared for all Tomcats) is attached. As you can see, I have tried to resolve requests from the different IP addresses to the different Tomcats. The server.xml file for this tomcat contains this connector definition: Tomcat 2 -------- Directory: D:\tc_system_test\ Name: System test The jk2.properties for this tomcat contains: channelSocket.port=8010 The server.xml file for this tomcat contains exactly the same connector definition as Tomcat 1 except the port is 8010 instead of 8009. IIS Site 1 (Development) ------------------------ IP: 203.8.163.166 jakarta virtual dir points to: D:\tomcat41\bin\native\ IIS Site 2 (System Test) ------------------------ IP: 203.8.163.164 jakarta virtual dir points to: D:\tc_esm_system_test\bin\native\ Symptons -------- When I navigate to the development site via http://203.8.163.166/ it works and I get my default page. When I navigate to the system test site via http://203.8.163.164/ I get a "zero size reply" error. If I go directly to Tomcat everything works OK. Looking at the ISAPI logs I can see that the development site logs this: HttpFilterProc started Virtual Host redirection of 203.8.163.166 : 80 [/index.jsp] is a servlet url - should redirect to ajp13:203.8.163.166:8009 check if [/index.jsp] is pointing to the web-inf directory HttpExtensionProc started HttpExtensionProc got a worker for name ajp13:203.8.163.166:8009 channelSocket.receive(): Error receiving message body -1 53 workerEnv.processCallbacks() Error reading reply ajp13.service() ajpGetReply recoverable error 120000 handler.response() Header[0] [Content-Type] = [text/html;charset=ISO-8859-1] handler.response() Header[1] [Content-Length] = [61] handler.response(): status=200 headers=2 Into jk_ws_service_t::head Into jk_ws_service_t::write HttpExtensionProc service() returned OK System test, on the other hand, contains this in the log: HttpFilterProc started In HttpFilterProc Virtual Host redirection of 203.8.163.164 : 80 HttpFilterProc [/index.jsp] is a servlet url - should redirect to ajp13:203.8.163.164:8010 HttpFilterProc check if [/index.jsp] is pointing to the web-inf directory It repeats these four lines 9 or 10 times and never reaches the HttpExtensionProc. Looking at the code I can see that the threadPool registry entry affects how the HttpExtensionProc is executed. I tried changing it from the existing value of 5 (which does not use a pool) to 10 (which should use the pool). It had no effect. Can anyone shed some light on this? I hope I have been clear in my explanation of the problem. If not, I would be happy to clarify. Thanks heaps for any help. Kent --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org