RE: jk2 load balancing problem (only fail-over)

2002-11-15 Thread Milt Epstein 
On Fri, 15 Nov 2002, Turner, John wrote:

> The Coyote connector speaks JK...there's no reason to use
> Ajp13Connector if you don't want to,
[ ... ]

Other than the apparent isSecure()/getScheme() bug with
CoyoteConnector when using AJP :-).

>  though I haven't seen anyone
> post a working conf specifically using load-balanced JK with
> org.apache.coyote.tomcat4.CoyoteConnector.
>
> It's worth a shot.
>
> John
>
>
> > -Original Message-
> > From: Nick Wesselman [mailto:nick@;digivis.com]
> > Sent: Friday, November 15, 2002 3:53 AM
> > To: Tomcat Users List
> > Subject: Re: jk2 load balancing problem (only fail-over)
> >
> >
> > So there's no production quality code to let me load balance
> > using the
> > Coyote connector?
> >
> > Should I use mod_jk and the older Ajp13 connector instead?
> >
> > Nick
> >
> > On Friday, November 15, 2002, at 01:52 AM, Bill Barker wrote:
> >
> > > Load balancing is still not implemented fully in Jk2 (it's still a
> > > Beta).
> > > It has very nice fail-over code however.  I'm sure that the
> > Jk2 team
> > > would
> > > welcome any patches.
> > >
> > > "Nick Wesselman" <[EMAIL PROTECTED]> wrote in message
> > > news:2303332D-F84E-11D6-8322-000393452A4C@;digivis.com...
> > >> I'm trying to set up jk2 load balancing for 2 Virtual
> > Hosts in Apache
> > >> with 2 Tomcats each. I have it mostly working, except it doesn't
> > >> actually load balance the Tomcats... however it will do
> > fail-over just
> > >> fine if I kill one VM.
> > >>
> > >> All my server.xml's have the correct jvmRoute set for the Engine.
> > >>
> > >> Any help on how to fix or debug this?
> > >>
> > >> Nick Wesselman
> > >>
> > -
> > >>
> > >> Environment:
> > >> RedHat 7.2
> > >> Apache 2.0.43
> > >> Tomcat 4.1.12
> > >> mod_jk2
> > >>
> > >> workers2.properties (names obfuscated to protect the innocent):
> > >> [logger]
> > >> level=DEBUG
> > >>
> > >> [config:]
> > >> file=/usr/local/apache2/conf/workers2.properties
> > >> debug=0
> > >> debugEnv=0
> > >>
> > >> [uriMap:]
> > >> info=Maps the requests. Options: debug
> > >> debug=0
> > >>
> > >> [logger.file:0]
> > >> level=DEBUG
> > >> file=/usr/local/apache2/logs/jk2.log
> > >>
> > >> [shm:]
> > >> info=Scoreboard. Required for reconfiguration and status with
> > >> multiprocess servers
> > >> file=/usr/local/apache2/logs/jk2.shm
> > >> size=100
> > >> debug=0
> > >> disabled=0
> > >>
> > >> [workerEnv:]
> > >> info=Global server options
> > >> timing=1
> > >> debug=0
> > >>
> > >> [status:]
> > >> info=Status worker, displays runtime information
> > >>
> > >> [uri:/jkstatus/*]
> > >> group=status:
> > >>
> > >> [lb:vhost1]
> > >> debug=0
> > >>
> > >> [channel.socket:vhost1_vm1]
> > >> port=8015
> > >> host=127.0.0.1
> > >> debug=0
> > >> group=vhost1
> > >> tomcatId=vhost1_vm1
> > >> lb_factor=1
> > >>
> > >> [channel.socket:vhost1_vm2]
> > >> port=8019
> > >> host=127.0.0.1
> > >> debug=0
> > >> group=vhost1
> > >> tomcatId=vhost1_vm2
> > >> lb_factor=1
> > >>
> > >> [uri:www.vhost1.com]
> > >> info=blah
> > >>
> > >> [uri:www.vhost1.com/*.jsp]
> > >> group=vhost1
> > >> info=blah
> > >>
> > >> [lb:vhost2]
> > >> debug=0
> > >>
> > >> [channel.socket:vhost2_vm1]
> > >> port=8015
> > >> host=127.0.0.1
> > >> debug=0
> > >> group=vhost2
> > >> tomcatId=vhost2_vm1
> > >> lb_factor=1
> > >>
> > >> [channel.socket:vhost2_vm2]
> > >> port=8019
> > >> host=127.0.0.1
> > >> debug=0
> > >> group=vhost2
> > >> tomcatId=vhost2_vm2
> > >> lb_factor=1
> > >>
> > >> [uri:www.vhost2.com]
> > >> info=blah
> > >>
> > >> [uri:www.vhost2.com/*.jsp]
> > >> group=vhost2
> > >> info=blah
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> > > For additional commands, e-mail:
> > > <mailto:tomcat-user-help@;jakarta.apache.org>
> >
> >
> > --
> > To unsubscribe, e-mail:
> <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:tomcat-user-help@;jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
>

Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

RE: jk2 load balancing problem (only fail-over)

2002-11-15 Thread Turner, John 

The Coyote connector speaks JK...there's no reason to use Ajp13Connector if
you don't want to, though I haven't seen anyone post a working conf
specifically using load-balanced JK with
org.apache.coyote.tomcat4.CoyoteConnector.

It's worth a shot.

John


> -Original Message-
> From: Nick Wesselman [mailto:nick@;digivis.com]
> Sent: Friday, November 15, 2002 3:53 AM
> To: Tomcat Users List
> Subject: Re: jk2 load balancing problem (only fail-over)
> 
> 
> So there's no production quality code to let me load balance 
> using the 
> Coyote connector?
> 
> Should I use mod_jk and the older Ajp13 connector instead?
> 
> Nick
> 
> On Friday, November 15, 2002, at 01:52 AM, Bill Barker wrote:
> 
> > Load balancing is still not implemented fully in Jk2 (it's still a 
> > Beta).
> > It has very nice fail-over code however.  I'm sure that the 
> Jk2 team 
> > would
> > welcome any patches.
> >
> > "Nick Wesselman" <[EMAIL PROTECTED]> wrote in message
> > news:2303332D-F84E-11D6-8322-000393452A4C@;digivis.com...
> >> I'm trying to set up jk2 load balancing for 2 Virtual 
> Hosts in Apache
> >> with 2 Tomcats each. I have it mostly working, except it doesn't
> >> actually load balance the Tomcats... however it will do 
> fail-over just
> >> fine if I kill one VM.
> >>
> >> All my server.xml's have the correct jvmRoute set for the Engine.
> >>
> >> Any help on how to fix or debug this?
> >>
> >> Nick Wesselman
> >> 
> -
> >>
> >> Environment:
> >> RedHat 7.2
> >> Apache 2.0.43
> >> Tomcat 4.1.12
> >> mod_jk2
> >>
> >> workers2.properties (names obfuscated to protect the innocent):
> >> [logger]
> >> level=DEBUG
> >>
> >> [config:]
> >> file=/usr/local/apache2/conf/workers2.properties
> >> debug=0
> >> debugEnv=0
> >>
> >> [uriMap:]
> >> info=Maps the requests. Options: debug
> >> debug=0
> >>
> >> [logger.file:0]
> >> level=DEBUG
> >> file=/usr/local/apache2/logs/jk2.log
> >>
> >> [shm:]
> >> info=Scoreboard. Required for reconfiguration and status with
> >> multiprocess servers
> >> file=/usr/local/apache2/logs/jk2.shm
> >> size=100
> >> debug=0
> >> disabled=0
> >>
> >> [workerEnv:]
> >> info=Global server options
> >> timing=1
> >> debug=0
> >>
> >> [status:]
> >> info=Status worker, displays runtime information
> >>
> >> [uri:/jkstatus/*]
> >> group=status:
> >>
> >> [lb:vhost1]
> >> debug=0
> >>
> >> [channel.socket:vhost1_vm1]
> >> port=8015
> >> host=127.0.0.1
> >> debug=0
> >> group=vhost1
> >> tomcatId=vhost1_vm1
> >> lb_factor=1
> >>
> >> [channel.socket:vhost1_vm2]
> >> port=8019
> >> host=127.0.0.1
> >> debug=0
> >> group=vhost1
> >> tomcatId=vhost1_vm2
> >> lb_factor=1
> >>
> >> [uri:www.vhost1.com]
> >> info=blah
> >>
> >> [uri:www.vhost1.com/*.jsp]
> >> group=vhost1
> >> info=blah
> >>
> >> [lb:vhost2]
> >> debug=0
> >>
> >> [channel.socket:vhost2_vm1]
> >> port=8015
> >> host=127.0.0.1
> >> debug=0
> >> group=vhost2
> >> tomcatId=vhost2_vm1
> >> lb_factor=1
> >>
> >> [channel.socket:vhost2_vm2]
> >> port=8019
> >> host=127.0.0.1
> >> debug=0
> >> group=vhost2
> >> tomcatId=vhost2_vm2
> >> lb_factor=1
> >>
> >> [uri:www.vhost2.com]
> >> info=blah
> >>
> >> [uri:www.vhost2.com/*.jsp]
> >> group=vhost2
> >> info=blah
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:   
> > <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
> > For additional commands, e-mail: 
> > <mailto:tomcat-user-help@;jakarta.apache.org>
> 
> 
> --
> To unsubscribe, e-mail:   
<mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:tomcat-user-help@;jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>

Re: jk2 load balancing problem (only fail-over)

2002-11-15 Thread Nick Wesselman 
So there's no production quality code to let me load balance using the 
Coyote connector?

Should I use mod_jk and the older Ajp13 connector instead?

Nick

On Friday, November 15, 2002, at 01:52 AM, Bill Barker wrote:

Load balancing is still not implemented fully in Jk2 (it's still a 
Beta).
It has very nice fail-over code however.  I'm sure that the Jk2 team 
would
welcome any patches.

"Nick Wesselman" <[EMAIL PROTECTED]> wrote in message
news:2303332D-F84E-11D6-8322-000393452A4C@;digivis.com...
I'm trying to set up jk2 load balancing for 2 Virtual Hosts in Apache
with 2 Tomcats each. I have it mostly working, except it doesn't
actually load balance the Tomcats... however it will do fail-over just
fine if I kill one VM.

All my server.xml's have the correct jvmRoute set for the Engine.

Any help on how to fix or debug this?

Nick Wesselman
-

Environment:
RedHat 7.2
Apache 2.0.43
Tomcat 4.1.12
mod_jk2

workers2.properties (names obfuscated to protect the innocent):
[logger]
level=DEBUG

[config:]
file=/usr/local/apache2/conf/workers2.properties
debug=0
debugEnv=0

[uriMap:]
info=Maps the requests. Options: debug
debug=0

[logger.file:0]
level=DEBUG
file=/usr/local/apache2/logs/jk2.log

[shm:]
info=Scoreboard. Required for reconfiguration and status with
multiprocess servers
file=/usr/local/apache2/logs/jk2.shm
size=100
debug=0
disabled=0

[workerEnv:]
info=Global server options
timing=1
debug=0

[status:]
info=Status worker, displays runtime information

[uri:/jkstatus/*]
group=status:

[lb:vhost1]
debug=0

[channel.socket:vhost1_vm1]
port=8015
host=127.0.0.1
debug=0
group=vhost1
tomcatId=vhost1_vm1
lb_factor=1

[channel.socket:vhost1_vm2]
port=8019
host=127.0.0.1
debug=0
group=vhost1
tomcatId=vhost1_vm2
lb_factor=1

[uri:www.vhost1.com]
info=blah

[uri:www.vhost1.com/*.jsp]
group=vhost1
info=blah

[lb:vhost2]
debug=0

[channel.socket:vhost2_vm1]
port=8015
host=127.0.0.1
debug=0
group=vhost2
tomcatId=vhost2_vm1
lb_factor=1

[channel.socket:vhost2_vm2]
port=8019
host=127.0.0.1
debug=0
group=vhost2
tomcatId=vhost2_vm2
lb_factor=1

[uri:www.vhost2.com]
info=blah

[uri:www.vhost2.com/*.jsp]
group=vhost2
info=blah






--
To unsubscribe, e-mail:   

For additional commands, e-mail: 



--
To unsubscribe, e-mail:   
For additional commands, e-mail:

Re: jk2 load balancing problem (only fail-over)

2002-11-14 Thread Bill Barker 
Load balancing is still not implemented fully in Jk2 (it's still a Beta).
It has very nice fail-over code however.  I'm sure that the Jk2 team would
welcome any patches.

"Nick Wesselman" <[EMAIL PROTECTED]> wrote in message
news:2303332D-F84E-11D6-8322-000393452A4C@;digivis.com...
> I'm trying to set up jk2 load balancing for 2 Virtual Hosts in Apache
> with 2 Tomcats each. I have it mostly working, except it doesn't
> actually load balance the Tomcats... however it will do fail-over just
> fine if I kill one VM.
>
> All my server.xml's have the correct jvmRoute set for the Engine.
>
> Any help on how to fix or debug this?
>
> Nick Wesselman
> -
>
> Environment:
> RedHat 7.2
> Apache 2.0.43
> Tomcat 4.1.12
> mod_jk2
>
> workers2.properties (names obfuscated to protect the innocent):
> [logger]
> level=DEBUG
>
> [config:]
> file=/usr/local/apache2/conf/workers2.properties
> debug=0
> debugEnv=0
>
> [uriMap:]
> info=Maps the requests. Options: debug
> debug=0
>
> [logger.file:0]
> level=DEBUG
> file=/usr/local/apache2/logs/jk2.log
>
> [shm:]
> info=Scoreboard. Required for reconfiguration and status with
> multiprocess servers
> file=/usr/local/apache2/logs/jk2.shm
> size=100
> debug=0
> disabled=0
>
> [workerEnv:]
> info=Global server options
> timing=1
> debug=0
>
> [status:]
> info=Status worker, displays runtime information
>
> [uri:/jkstatus/*]
> group=status:
>
> [lb:vhost1]
> debug=0
>
> [channel.socket:vhost1_vm1]
> port=8015
> host=127.0.0.1
> debug=0
> group=vhost1
> tomcatId=vhost1_vm1
> lb_factor=1
>
> [channel.socket:vhost1_vm2]
> port=8019
> host=127.0.0.1
> debug=0
> group=vhost1
> tomcatId=vhost1_vm2
> lb_factor=1
>
> [uri:www.vhost1.com]
> info=blah
>
> [uri:www.vhost1.com/*.jsp]
> group=vhost1
> info=blah
>
> [lb:vhost2]
> debug=0
>
> [channel.socket:vhost2_vm1]
> port=8015
> host=127.0.0.1
> debug=0
> group=vhost2
> tomcatId=vhost2_vm1
> lb_factor=1
>
> [channel.socket:vhost2_vm2]
> port=8019
> host=127.0.0.1
> debug=0
> group=vhost2
> tomcatId=vhost2_vm2
> lb_factor=1
>
> [uri:www.vhost2.com]
> info=blah
>
> [uri:www.vhost2.com/*.jsp]
> group=vhost2
> info=blah





--
To unsubscribe, e-mail:   
For additional commands, e-mail: