A question about configuration of "workers.properties"

I have 2 questiuons.

1.
I see many examples as follow:
[code]
worker.list=worker1,worker2
# Set properties for worker1
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
# Set properties for worker2
worker.worker2.type=ajp13
worker.worker2.host=localhost
worker.worker2.port=8109
[/code]

But can I configure all workers to access the same port as follow?
[code]
worker.list=worker1,worker2
# Set properties for worker1
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
# Set properties for worker2
worker.worker2.type=ajp13
worker.worker2.host=localhost
worker.worker2.port=8009
[/code]

2.
Here is another configuration:
[code]
###################################
# Define the Template
###################################
worker.template.connection_pool_timeout=300
worker.template.socket_keepalive=True
worker.template.lbfactor=1
worker.template.type=ajp13
worker.template.ping_timeout=10000
worker.template.ping_mode=A
worker.template.retries=20
worker.template.activation=A
worker.template.recovery_options=7
worker.template.socket_timeout=120
[/code]

a) Is the parameter 'socket_timeout' unnecessary?
b) Here I used 'connection_pool_timeout'. What and how should I do by Tomcat
(server.xml)?


--
View this message in context: http://old.nabble.com/A-question-about-configuration-of-%22w orkers.properties%22-tp26774675p26774675.html
Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com.


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: A question about configuration of "workers.properties"

thomas2004 wrote:
> I have 2 questiuons.

I'll just give my opinion on the first one.

>
> 1.
> I see many examples as follow:
> [code]
> worker.list=worker1,worker2
> # Set properties for worker1
> worker.worker1.type=ajp13
> worker.worker1.host=localhost
> worker.worker1.port=8009
> # Set properties for worker2
> worker.worker2.type=ajp13
> worker.worker2.host=localhost
> worker.worker2.port=8109
> [/code]
>
> But can I configure all workers to access the same port as follow?
> [code]
> worker.list=worker1,worker2
> # Set properties for worker1
> worker.worker1.type=ajp13
> worker.worker1.host=localhost
> worker.worker1.port=8009
> # Set properties for worker2
> worker.worker2.type=ajp13
> worker.worker2.host=localhost
> worker.worker2.port=8009
> [/code]
>

What would be the point ?
Normally, the point of having more than one worker, is when you have
more than one Tomcat back-ends, and you want to distribute the requests
between them (either by load-balancing, or just by selecting one or the
other based on the request URL).

If you configure different workers, but all of them point to the same
back-end host and port, then all the requests anyway will go to the same
Tomcat, and to the same Connector within Tomcat.
It is at best an increase in the overhead.
At worst, by doing this, you probably ruin the mod_jk calculation of how
many connections to Tomcat it should manage and keep alive.





------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org