AW: mod_jk release policy - was: JK 1.2.9-dev test results

Hi, I just want to describe our usecase because we make heavy use of the local_worker and local_worker_only flags right now. We use those flags for 'maintenance' mode and failover very successfuly. But please see our setup and usecase below. -Ursprüngliche Nachricht- Von: Mladen Turk

AW: AW: mod_jk release policy - was: JK 1.2.9-dev test results

release policy - was: JK 1.2.9-dev test results Hans Schmid wrote: Hi, I just want to describe our usecase because we make heavy use of the local_worker and local_worker_only flags right now. We use those flags for 'maintenance' mode and failover very successfuly. Cool

AW: Ready for mod_jk 1.2.6 release?

Hi, a mod_jk 1.2.6 release would be highly welcome. We are using cvs head in production for a couple of month now without problems. thanks, Hans -Ursprungliche Nachricht- Von: Henri Gomez [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 8. Juli 2004 10:01 An: Tomcat Developers List

AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors

maxSpareThreads=80 minSpareThreads=40 / -Ursprüngliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 22. April 2004 11:41 An: Tomcat Developers List Betreff: AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2

Any news on mod_jk 1.2.6 realease plan?

, Hans Schmid einsurance Agency AG Information Technology Bayerstrasse 33 80335 München Tel: +49-89-55292-860 Fax: +49-89-55292-855 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors

(It happen Should I file a Bugzilla Entry? (we have 3+ years Experience with the Tomcat 3.3 series and AJP13Connectors) Hans Schmid einsurance Agency AG Information Technology Bayerstrasse 33 80335 München Tel: +49-89-55292-860 Fax: +49-89-55292-855

AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors

Sorry, I forgot to mention, that we are using mod_jk 1.2.5 on the Apache side -Ursprüngliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 22. April 2004 11:25 An: Tomcat-Dev Betreff: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote

AW: AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors

] Gesendet: Donnerstag, 22. April 2004 11:46 An: Tomcat Developers List Betreff: Re: AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors Hans Schmid wrote: Sorry, I forgot to mention, that we are using mod_jk 1.2.5 on the Apache side I'm using the same config

AW: AW: AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors

-Ursprungliche Nachricht- Von: Henri Gomez [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 22. April 2004 12:38 An: Tomcat Developers List Betreff: Re: AW: AW: java.io.IOException: Read bytes failed in Tomcat 3.3.2 with Coyote Connectors Hans Schmid wrote: Hi Henri

AW: Bug report for Tomcat 3 [2004/02/15]

Hi, this does not look like a Tomcat 3 buglist. More like Jetspeed or Velocity? At least it is a completely different list as last week. Something got mixed up in Bugzilla? While speaking, would it be possible to set up an automated Bug report for Tomcat 5 as well? Thanks, Hans

AW: jk 1.2.4 LB bug?

Then post those log lines here. Thanks, Glenn Hans Schmid wrote: Hi, I noticed the following with mod_jk 1.2.4, Apache 1.3.26 and Tomcat 3.3.1a on Solaris 8 JDK 1.4.1_03. Maybe a LB bug (Loadfactors do not recover after startup of new tomcat/graceful Apache restart). Let me

Solved AW: jk 1.2.4 LB bug?

linking !!! Thanks very much. p.s. If anybody else is interested in our LB/failover setup I am glad to provide some info. Best regards, Hans -Ursprungliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 16. Juli 2003 15:15 An: Tomcat Developers List Betreff

jk 1.2.4 LB bug?

Hi, I noticed the following with mod_jk 1.2.4, Apache 1.3.26 and Tomcat 3.3.1a on Solaris 8 JDK 1.4.1_03. Maybe a LB bug (Loadfactors do not recover after startup of new tomcat/graceful Apache restart). Let me explain my scenario first: I want to gracefully upgrade our webapp without loosing

AW: java processes created by tomcat

See http://tomcatfaq.sourceforge.net/linx.html cheers, Hans -Ursprüngliche Nachricht- Von: siddharth [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 17. Juni 2003 12:13 An: [EMAIL PROTECTED] Betreff: java processes created by tomcat hello, I am running following servers on my

AW: [VOTE] minimal JSR 154 only distribution

Hi, I would like to have the possibility to not include jasper in our production system. We are using TC 3.3.2-dev plus Velocity. It does not really hurt us, but having fewer code is always better IHMO :) I really love the modularity og TC 3.3.x Bill, can you give me hints, how to patch TC

Nightly TC 3.3.x builds not working anymore?

Hi, the nightly build of Tomcat 3.3.x seems to have stopped at 08-Nov-2002. Any Idea, why? Cheers, Hans -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]

AW: Nightly TC 3.3.x builds not working anymore?

: Henri Gomez [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 20. November 2002 10:41 An: Tomcat Developers List Betreff: Re: Nightly TC 3.3.x builds not working anymore? Hans Schmid wrote: Hi, the nightly build of Tomcat 3.3.x seems to have stopped at 08-Nov-2002. Any Idea, why

Re: Bug 13736

is now in the 3.3 nightly. Since you can reproduce this, it would be a big help if you could find a machine to test this on. - Original Message - From: Hans Schmid [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Saturday, October 19, 2002 5:59 AM Subject: AW: Bug 13736

AW: Bug 13736

Bill, Remy, I have seen this one once on our production system running Tomcat 3.3.1 with AJP1.3, Apache 1.3.27, mod_jk 1.1.0 This is on Sparc Solaris 8 running JDK 1.3.1_04. 11019 is our ajp13 port (which we uswe also as shutdown port. No AJP 1.2 port open) Our webservers use the lb_worker to

AW: [POLL] Tomcat 3.3.2 updates

Hi, since our application uses TopLink, we can not upgrade to xerces 2. There are hardcoded xerces 1 classes used directly from TopLink. So 2) is a showstopper for all people with 3rd party jars requiring xerces 1 MBeans are useful for us, but not required. We are already using mx4j and

[TC 5] XMLSchema validation and Xerces 2.1.0

it in Tomcat 4.1 as well Just a thought, Hans Schmid -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]

AW: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt

Hi I miss the following fix in there: Configuration: Bug No. Description 7520 Tomcat starts with title 3.3 instead of 3.3.1. Insert version string during build. Cheers, Hans -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17.

AW: startup.bat window

First, this is clearly a tomcat-user question. To find out, what is wrong, execute tomcat.bat run This will start tomcat in the same window. (TC 3.3.1 at least) I can't help you with the mySQL question though. Regards, Hans -Ursprüngliche Nachricht- Von: Bill Blackmon [mailto:[EMAIL

AW: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common Shm.java

Please see questions on shm and lb worker intermixed, -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 2. Mai 2002 05:18 An: [EMAIL PROTECTED] Betreff: cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/common Shm.java

AW: PROPOSAL: mod_jk2: Group/Instance

-Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 2. Mai 2002 19:35 An: Tomcat Developers List Betreff: Re: PROPOSAL: mod_jk2: Group/Instance On Thu, 2 May 2002, Bernd Koecke wrote: misunderstood it. After you said that my patch

AW: PROPOSAL: mod_jk2 autoconfig

See intermixed -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 29. April 2002 19:17 An: List Tomcat-Dev Betreff: PROPOSAL: mod_jk2 autoconfig Hi, I spent a lot of time on this - and I think this is a very good solution. Please send

AW: AW: PROPOSAL: mod_jk2 autoconfig

-Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 30. April 2002 16:39 An: Tomcat Developers List Betreff: Re: AW: PROPOSAL: mod_jk2 autoconfig On Tue, 30 Apr 2002, Hans Schmid wrote: I can not see how this works if you have

AW: Apache1.3/mod_jk (unix) Tomcat 4 No processor available, rejecting this connection

Hi, what about Tomcat 3.3 ? Does this correspond to Ajp13Connector maxThreads = the maxiumum number of Apache httpd processes in this case? Thanks, Hans -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Glenn Nielsen Gesendet: Freitag, 22.

AW: mod_jk suggestion, add request logging option

Hi, what about adding 'port' to the list. For lb workers the worker would be the real one used not 'loadbalancer', right? I think it would be really helpful to have this log level. Cheers, Hans -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag

AW: AW: mod_jk suggestion, add request logging option

-Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Glenn Nielsen Gesendet: Donnerstag, 21. Februar 2002 19:28 An: Tomcat Developers List Betreff: Re: AW: mod_jk suggestion, add request logging option Hans Schmid wrote: Hi, what

Loadbalancer problems in mod_jk 4.0.3 [was Native Connector problems]

::map_uri_to_worker Thanks a lot for looking into this, Best Regards, Hans -Ursprungliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 13. Februar 2002 08:23 An: Tomcat Developers List Betreff: AW: Native Connector problems Hi, I just ran into a problem

AW: Native Connector problems

Hi, I just ran into a problem with the loadbalancing stuff. I built mod_jk.so from the 4.0.2 connector package and replaced my mod_jk.so (TC3.3 Version) with this one in apache/libexec (1.3.19). By just changing a link back and forth between the two versions, I tested our TC3.3 based

WG: TC3.3 updating a webapp without killing sessions

keep in mind the requirement to be able to update Webapps in a farm of Tomcats without killing active sessions. Thanks, Hans -Ursprüngliche Nachricht- Von: Hans Schmid [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 28. November 2001 18:21 An: Tomcat Users List Betreff: AW: TC3.3

AW: tomcat in the production environment

Hi Kandasamy. we are using Tomcat 3.3 on our production site. Solaris 2.7 Sparc, 2 processors, JDK 1.3.1_01 mod_jk ajp1.3 behind two Apache 1.3.19 with a HW loadbalancer in front. And still our single Tomcat 3.3 instance is not the bottleneck. Currently it is our Oracle machine :) BTW. we make

WG: worker.properties swallows my first worker (mod_jk)

in question. Thanks. Larry -Original Message- From: Hans Schmid [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 06, 2001 12:57 PM To: Tomcat-User Subject: worker.properties swallows my first worker (mod_jk) Hello, This is about mod_jk in Tomcat 3.3b1 on Solaris with Apache 1.3.19

[PATCH] Tomcat 3.3 m3 mod_jk-howto.html (new Bug #1809)

Hello, I just installed Tomcat3.3-m3 with ajpv13 behind Apache 1.3.19 on Win2000. While setting up mod_jk with ajp1.3, I noticed a bug in the mod_jk-howto.html It states: Add the following block to your TOMCAT_HOME/conf/server.xml file. Connector

[PATCH] JSP examples TC 3.3 latest

Hi folks, there is still a little bug in the TC 3.3 JSP examples after my patch has been applied. The JSP-Servlet-JSP example does not show the Source code (with IE 5.5) Instead an Error 500 pops up. Reason: Wrong directory name referenced in jts.html (jsp/jsptoservlet instead of

AW: AW: [PATCH REPOST] Tomcat 4.0 JSP Examples view Source

[EMAIL PROTECTED] Gefion Software http://www.gefionsoftware.com Thanks for clarification, Best Regards, Hans Hans Schmid

AW: AW: [PATCH REPOST] Tomcat 4.0 JSP Examples view Source

Hi Pierre, see below: -Ursprüngliche Nachricht- Von: Pierre Delisle [mailto:[EMAIL PROTECTED]] Gesendet am: Samstag, 2. Dezember 2000 01:39 An: [EMAIL PROTECTED] Betreff: Re: AW: [PATCH REPOST] Tomcat 4.0 JSP Examples view Source Hans Schmid wrote: Pierre, at least we

[PATCH REPOST] Tomcat 4.0 JSP Examples view Source

Hi there, I sent a patch to display the source code in the JSP examples and did not get any feedback either. Probably because US folk was in turkey mode :) and busy working on Tomcat 3.2 thereafter. Good work!! What it does: JSP Examples in Tomcat 4.0 have a 'View Source' button. All but the