Re: MOD_JK (Apache+Tomcat)

2003-12-30 Thread Hari Om
Thanks Jerry, My Apache and Tomcat are working independently.ie when I run http://my.domain.name:8080/kuki or http://my.domain.name:8080/examples ...it works just great problem only occurs when I use connector MOD_JK. Any related informaiton is appreciated.. HARI OM Hello, I am

MOD_JK (Apache+Tomcat)

2003-12-30 Thread HARI OM
Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO which I build from the source and put in /modules directory. When I run my Tomcat first and then Apache and then acceess http://My.domian.name/kuki it does not work... it says Page

Re: MOD_JK (Apache+Tomcat)

2003-12-30 Thread HARI OM
any update on this? - Original Message - From: HARI OM [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, December 30, 2003 10:16 AM Subject: MOD_JK (Apache+Tomcat) Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO

Re: MOD_JK (Apache+Tomcat)

2003-12-30 Thread Jerry Ford
] To: [EMAIL PROTECTED] Sent: Tuesday, December 30, 2003 10:16 AM Subject: MOD_JK (Apache+Tomcat) Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO which I build from the source and put in /modules directory. When I run my Tomcat first

MOD_JK (Apache+Tomcat)

2003-12-29 Thread Hari Om
Hello, I am using APache 2.0.47 and Tomcat 4.1.27 on SuSE Linux 8.1 I am working on the Connector MOD_JK.SO which I build from the source and put in /modules directory. When I run my Tomcat first and then Apache and then acceess http://My.domian.name/kuki it does not work... it says Page

Re: MOD_JK (Apache+Tomcat)

2003-12-29 Thread Jerry Ford
Hari: You're trying to do too much too soon. Get the Apache - Tomcat connection through mod_jk to work before you try to get your own webapp to work. Use the Tomcat example servlets to verify that mod_jk is correctly installed and functional. If you can run the servlets through Apache

Number of processes and relationship to mod_jk, Apache, tomcat

2003-10-28 Thread Andrew Panagos
I am trying to understand the relationship between applications in Tomcat, the number of Tomcat processes, Apache mod_jk and the number of threads. For instance on a system I have the following Apache 1.3.28, Tomcat 4.1.27, Java 1.4.2_02 I use the follow commands to see what is listening to

Re: Number of processes and relationship to mod_jk, Apache, tomcat

2003-10-28 Thread Christopher Schultz
Andrew, I am trying to understand the relationship between applications in Tomcat, the number of Tomcat processes, Apache mod_jk and the number of threads. Apache: lsof -i tcp:80 | wc -l This gives me 12 processes listening to port 80 (I checked these are related to the number of Apache

mod_jk (Apache-Tomcat) problem

2003-10-21 Thread Robert Hall
Hi, I'm new to this list and hoping someone can help with the following problem. We have a JBoss (3.2.1) install w/embedded Tomcat (4.1.24) fronted by Apache 1.3.27 running on Solaris. The problem: mod_jk is setting the Content-Length header value to 0 for Content-Type of text/html when an HTML

mod_jk (Apache + Tomcat)

2003-10-09 Thread Mariano Cristóbal
I have configured apache 2.0.47 + tomcat 4.1.27 with mod_jk 2.0.2 on a Red Hat 6.2 distribution. It seems to work fine but in the error_log file I obtain the following message: [error] mod_jk child init 1 0 I dont know what is the problem. Thanks

mod_jk, apache, tomcat and solaris 8

2003-06-06 Thread John Sheehan
Hi We are having problems with load balancing of apache and tomcat on solaris. We have 4 solaris servers, 2 with apache 2.0.45 installed and 2 with Tomcat 4.1.24. We are using mod_jk on the apache servers to connect to the two tom cat servers and get them to load balance and failover, the idea

mod_jk/apache + tomcat 3.2.1 keep connections open after Browser closes

2001-03-13 Thread Mario Oschwald
Hi, we are writing a chat application that uses a continous stream of data via a JspWriter to the browser. To detect if a client closes the connection by killing her Browserwindow we catch the IOexception thrown if a JspWriter.flush() method fails due to a loss of connection. Now this works