Hello,
I am trying to setup a scenario where I would like to have more
than one lbworker active. I can't get it to work.
My question before I investigate further:
Is it possible to have multiple lbworkers defined in mod_jk1 (Tomcat 3.3.1),
each serving 2 or more Tomcats with different webapps?
Sorry,
my fault, it works perfect (another copy/paste)
Thanks,
Hans
-Ursprüngliche Nachricht-
Von: Hans Schmid [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 6. Juni 2003 08:44
An: Tomcat-User
Betreff: More than one lbworker possible with mod_jk 1.2.3 ?
Hello,
I am trying
Hello,
I am trying to setup a scenario where I would like to have more
than one lbworker active. I can't get it to work.
My question before I investigate further:
Is it possible to have multiple lbworkers defined in mod_jk1 (Tomcat 3.3.1),
each serving 2 or more Tomcats with different webapps?
of a single global one.
If we decide to leave it as it is, we might consider to change the $HOME to
$TOMCAT_HOME for consistency.
What do you think?
Regards,
Hans
Hans Schmid
einsurance Agency AG
Information Technology
Bayerstrasse 33
80335 München
Tel: +49-89-55292-860
Fax: +49-89-55292-855
Hi,
I just ran into a problem with loadbalancing in mod_jk when using
the version which comes with TC 4.0.2.
I am currently using Tomcat 3.3 on Solaris 8 behind Apache 1.3.19
connectted via mod_jk 1.1.0 comming with TC 3.3.
I built mod_jk.so from the 4.0.2 connector package and replaced my
Hi,
We try to make a workaround for the following problems:
1.) memory management
2.) application update
3.) do not kill active sessions
Perhaps someone can comment on the startegy and answer some questions.
Our environment:
Tomcat 3.3 final with mod_jk Apache 1.3.19 on Solaris 2.7 Sparc
Our
: Hans Schmid [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 28, 2001 4:25 AM
To: Tomcat-User
Subject: TC3.3 updating a webapp without killing sessions
Hi,
We try to make a workaround for the following problems:
1.) memory management
2.) application update
3.) do not kill
Hi,
I found the following in the archives and it solved my problems:
Best Regards,
Hans
-Ursprungliche Nachricht-
Von: Andrea Barbieri [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 23. Juli 2001 12:42
An: [EMAIL PROTECTED]
Betreff: Re: mod_jk info...
I tried to put your option but is
?
Don't know, I will investigate.
2.) Is this a Bug I shall report?
Yes, and please attache the workers.properties in question.
Thanks.
Larry
-Original Message-
From: Hans Schmid [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 12:57 PM
To: Tomcat-User
8007 created?
2.) Is this a Bug I shall report?
Since I have a work around by putting this space in front of my first
worker, I can live with this.
Is this a Bug I should put into Bigzilla?
Hans Schmid
einsurance Agency AG
Information Technology
Bayerstraße 33
80335 München
Tel: +49-89-55292
: 5448524541442C4F43414C33544F524147450E435050002B 01
#
# Problematic Thread: prio=5 tid=0xe9ea0 nid=0x13 runnable
#
Thanks a lot for your help,
Hans Schmid
einsurance Agency AG
Information Technology
Bayerstraße 33
80335 München
Tel: +49-89-55292- 860
Fax: +49-89-55292- 855
eMail: [EMAIL PROTECTED
this:
Context path=/examples ... cookies=false ...
So is it supported in Tomcat 3.3-b1 ?
If not is it planned or do I need to upgrade to Tomcat 4 to get this
feature?
Thanks for your Help.
Best Regards,
Hans Schmid
einsurance Agency AG
Information Technology
Bayerstraße 33
80335
/* DECLINE
JkMount /*.php4 DECLINE
with a best match served first.
I have a rought patch that does this, but it's realy uggly..
This way it would be very simple to handle Apache/Php/Tomcat in one server
Has anybody something like this?
Your comment would be highly appreciated,
Hans Schmid
einsurance
13 matches
Mail list logo