Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 10317 invoked from network); 5 Sep 2003 03:19:49 -0000 Received: from unknown (HELO main.gmane.org) (80.91.224.249) by daedalus.apache.org with SMTP; 5 Sep 2003 03:19:49 -0000 Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19v797-0004H7-00 for ; Fri, 05 Sep 2003 05:20:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: tomcat-user@jakarta.apache.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19v702-0004E6-00 for ; Fri, 05 Sep 2003 05:11:02 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 19v6zY-0000wN-00 for ; Fri, 05 Sep 2003 05:10:32 +0200 From: "Bill Barker" Subject: Re: Tomcat as an in-process Servlet container? Date: Thu, 4 Sep 2003 20:21:10 -0700 Lines: 25 Message-ID: References: X-Complaints-To: usenet@sea.gmane.org X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: news X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I don't really understand the question. If you are using channelJni, then there is no address or port: The data is passed in-memory. "Carlos Cajina - Hotmail" wrote in message news:Law10-OE60b81IfpT8v00007fc6@hotmail.com... Hi everyone. I've followed the steps in http://www.greenfieldresearch.ca/technical/jk2_config.html for configuring Apache and Tomcat to communicate using JNI with good results, but there's just one thing that I can't figure out: When using channelSocket as the communication channel between the two servers is possible to use the workers2.properties file to configure the host:port where Apache is supposed to forward requests for non-static content, so a call to some http://host/webapp/index.jsp would be served transparently. Now, how do I do the same mapping when using channelJni? My main concern is to let user access any WebApp without having to type Tomcat's listening port. Regards, Carlos