Hi Jamie,
I upgraded yesterday to Resin 4, with your suggestions and it is working
perfectly. There also seems to be a marked performance boost which is nice.
Upgrading to 4 was a great suggestion, thanks!
The watchdog.conf file, does provide a very nice and efficient way to
start/stop resin instances, however I just couldn't get it config'd for my
uses with shared IPs, load balancing, many hosts, etc.
The big issue that I find now, is that when modifying resin.xml file, all
hosts attached to the load-balancer get restarted. Do you somehow segregate
your hosts in a way that allow you to add new hosts for load balancing
without restarting all of the hosts?
Thanks!
Joey
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Marketing -
IncorporateFast.com
Sent: Wednesday, September 29, 2010 1:34 PM
To: 'General Discussion for the Resin application server'
Subject: Re: [Resin-interest] Watchdog binding
Thanks Jamie,
I'm currently working with the following watchdog.conf, to specify
individual JVM's and specific users rights for each JVM. We also use the
security manager for enhanced security and we are running multiple hosts per
server.
http://caucho.com/resin-4.0/admin/starting-resin-watchdog.xtp#ISP watchdog
management
I've been dragging my feet on going to Resin 4, to let some bugs get washed
out. Do you use 4 in production environment?
We do use separate watchdogs to specify host.conf. In each host.conf file,
we specify the jvm-arg for client specific java security policy.
Any suggestions?
Thanks!
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Jamison Novak
Sent: Wednesday, September 29, 2010 12:57 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Watchdog binding
Just out of curiosity, is there a reason why you're trying to configure or
manipulate the watchdog? Are you attempting to isolate users by giving
multiple users their own watchdog processes (and child Resin processes)?
If all you want to do is emulate the Apache front-end + Resin back-end
paradigm with a pure Resin solution, you don't really need to do anything
special to the watchdog at all. Over-simplifying things, it's really just
there to help you start/stop/keep an eye on your Resin processes.
http://caucho.com/resin-4.0/admin/http-virtual-hosts.xtp#Server per virtual
host
In those two examples, the "Resin web-tier" essentially performs Apache's
role in this new configuration. When you start up the web-tier cluster,
that's the process that will bind to port 80 on an IP address to load
balance traffic to the individual Resin clusters on the back-end.
The "Back-end JVM" is where you'd actually configure and manage the
individual clusters/virtual hosts. These back-end JVMs can also bind to port
80 on different IP addresses than the web-tier, if you have some sites with
their own dedicated IPs.
If you think it would help beyond looking at the examples in their
documentation, I could provide you with a stripped down version of one of
the configs that we use. We have a mix of sites with dedicated and shared IP
addresses. The dedicated sites function independently of the web-tier, since
it's more efficient to send the traffic directly to the cluster than to send
it through the web-tier. The sites that share an IP address use the web-tier
for front-end request handling and load balancing to the cluster on the
back-end.
It's similar to, but not exactly like, the examples in the documentation. It
may help to see it another way if their docs are confusing you, though. Let
me know?
-Jamie
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Marketing -
IncorporateFast.com
Sent: Wednesday, September 29, 2010 12:19 AM
To: 'General Discussion for the Resin application server'
Subject: Re: [Resin-interest] Watchdog binding
Hi Jamie,
I'm using the watchdog.conf, and it seems to be acting a bit differently.
Couple of questions:
1.) When using watchdog.conf, can a resin load balancer be used? If so,
how/where?
2.) When using watchdog.conf, are unique IP's required?
3.) If load balancer is used, I can point to a loadbalancer.conf, but what
goes into the folder?
resin
resin
/usr/local/resin/conf/www.loadbalancer.conf
/resin/webapps/what_directory_goes_here
It seems like watchdog.conf requires unique IP. Right now I have many with
unique IP, but would like to setup some shared IPs as well. Appreciate your
help & time!
-Original Message-
From: resin-interest-boun...@caucho.com
[mailto:resin-interest-boun...@caucho.com] On Behalf Of Jamison Novak
Sent: Monday, September 27, 2010 11:34 PM
To: General Discussion for the Resin application server
Subject: Re: [Resin-interest] Watchdog binding
> Can a watchdog bind to a port already used by
