Re[2]: Tomcat as an in-process Servlet container?
Hello Carlos! CCH> My confusion comes from the fact that when using channelSocket to connect Apache and Tomcat I can type the URL of any WebApp without specifying Tomcat's listening port because the CCH> mapping/forwarding is handled in the config files, but after configuring ChannelJni to handle Apache-Tomcat communication I'm forced to include the port number (8080) in the URL to access the CCH> WebApps, otherwise I get an Internal Server Error. I'm totally out of your discussion but just from a single glance at your post it looks like by typing 8080 you access Tomcat directly bypassing Apache HTTPD. To be sure you may want to disable Tomcat http capabilities at all by commenting out the configuration element in Tomcat config that specifies the 8080 port. Hope my comment has not fallen totally out of context, WBR, Anton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat as an in-process Servlet container?
Howdy Bill. My confusion comes from the fact that when using channelSocket to connect Apache and Tomcat I can type the URL of any WebApp without specifying Tomcat's listening port because the mapping/forwarding is handled in the config files, but after configuring ChannelJni to handle Apache-Tomcat communication I'm forced to include the port number (8080) in the URL to access the WebApps, otherwise I get an Internal Server Error. I wonder wether I'm missing something in my configuration because, as I stated, my main concern is to let user access any WebApp without having to type Tomcat's listening port. Thanks for taking time to answer. Best regards, Carlos "Bill Barker" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > 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" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > 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 > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Tomcat as an in-process Servlet container?
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" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat as an in-process Servlet container?
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
Tomcat as an in-process Servlet container?
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. Everything works fine but there's just one thing that I can't figure out: When using channelSocket as the communication channel between the two 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? Regards, Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
