Gregor Schneider wrote:
Hi guys,
just a quickone:
I'm having a server here running 4 different domains, luckily having a
bunch of IP-adresses on said host available.
On my test-server, I just had one IP-adress, thus I created one
HTTP-Connector (without the adress-param), below an Engine and inside
the Engine 4 different Host-Elements.
Working like charm.
None of those domains requires SSL.
Now me being lazy, I'm wondering:
Should I just run this configuration on our Prod-server? Although
DNS-entries for said domains all point to different IP-adresses,
Tomcat doesn't bother since it's just reading the headers and routing
to the correct host.
So what would you do? Be lazy? Set up the config perfectly? What's the
benfit setting up a HTTP-Connector for each IP-Adress?
Your input very welcome!
From a non-Tomcat specialist, simply going by the docs and the little I
have learned here :
As I understand, when you use the standard HTTP Connector, the Connector
is the one who creates the threads that will handle requests. It is
also the one which keeps the TCP connection queue when there are more
requests pending than the maximum number of living threads can handle.
So if you have 4 Connectors, you will be having 4 independent number of
min and max threads, and 4 independent settings for the number of TCP
connections to be queued up.
Having 4 connectors would also allow you to set different other
Connector-specific settings, in case you need them.
Now whether all that would ultimately be an advantage or a disadvantage,
that is beyond my faculties of analysis.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
