Re: suse 9.1, tomcat5.0.27, mod_jk2, apache 2.0.13 problems

2004-11-30 Thread dawg fan
2, apache 2.0.13 problems Date: Tue, 30 Nov 2004 06:48:11 +0200 > > On Tuesday 30 November 2004 06:29, dawg fan wrote: > > Hello, > > Hi, > > > We just reloaded many of our front-end servers to suse 9.1 from > > suse 8.2. This release of suse of course has the new 2.6 k

suse 9.1, tomcat5.0.27, mod_jk2, apache 2.0.13 problems

2004-11-29 Thread dawg fan
Hello, We just reloaded many of our front-end servers to suse 9.1 from suse 8.2. This release of suse of course has the new 2.6 kernel with a few other changes. That is the only change as we used the same tomcat 5.0.27, mod_jk2, and apache 2.0.13 configurations from the previous 8.2 server.

ajp1.3 errors while using tomcat 5.0.25, apache 2.0.49, modjk2

2004-08-17 Thread dawg fan
I get the following error in apache's error logs while testing tomcat under extreme load: [Tue Aug 17 14:15:25 2004] [error] channelApr.receive(): Error receiving message body -1 11 [Tue Aug 17 14:15:25 2004] [error] workerEnv.processCallbacks() Error reading reply [Tue Aug 17 14:15:25 2004] [err

unix sockets vs. channel sockets vs. apr sockets

2004-06-29 Thread dawg fan
Hello, Has anyone done any research into performance results from unix sockets vs. channel sockets vs. apr sockets? I am currently loading apache2, mod_jk2, and tomcat 5. I would like to know the difference in performance for the 3 sockets. I was using apache 1.3, mod_jk, and tomcat 4.1.30

RE: Tomcat 4.1.x Vs 5.0.x

2004-05-13 Thread dawg fan
>From personal experience in testing on Suse 8.2 and tomcat 4.1.30 using a load of >1000 concurrent connections pulling continuous pages from the webserver, the >following was found: - using ibm jdk and blackdown jdk (basically same thing) gave the fastest serve times for the first hour of testi

Re: ¿how configure tomcat to auto startup in =?iso-8859-1?q?linux??=

2004-05-04 Thread dawg fan
To make it automatically startup on boot in linux, setup a link in /etc/init.d/rc3.d. To do this, make your tomcat startup script live at /etc/init.d/tomcat. Then run "insserv tomcat" or "ln -s /etc/init.d/tomcat /etc/init.d/rc3.d/tomcat" as the root user. There are several other methods, bu