To: users@tomcat.apache.org
Subject: Re: Do I Need Network NameSpaces to Solve This
Tomcat+Connector/J Problem?
Eric,
On 12/30/21 19:03, Eric Robinson wrote:
If I want to ignore the vendor's recommendation and try connection
pooling anyway, is that something I can enable with a config file
setting, or do the
to me soon hopefully.
> -Original Message-
> From: Christopher Schultz
> Sent: Monday, January 3, 2022 9:10 AM
> To: users@tomcat.apache.org
> Subject: Re: Do I Need Network NameSpaces to Solve This
> Tomcat+Connector/J Problem?
>
> Eric,
>
> On 12/30/21 1
hursday, December 30, 2021 12:00 PM
To: Tomcat Users List
Subject: RE: Do I Need Network NameSpaces to Solve This
Tomcat+Connector/J Problem?
Chris,
Not pooling connections will very likely negatively affect performance.
When you say "they ... have an issue with connection pooling&qu
obinson >>> <mailto:eric.robin...@psmnv.com>>
>>>> Sent: Thursday, December 30, 2021 12:00 PM
>>>> To: Tomcat Users List >>> <mailto:users@tomcat.apache.org>>
>>>> Subject: RE: Do I Need Network NameSpaces to Solve This
>>>&g
0 PM
> >> To: Tomcat Users List >> <mailto:users@tomcat.apache.org>>
> >> Subject: RE: Do I Need Network NameSpaces to Solve This
> >> Tomcat+Connector/J Problem?
> >>
> >> Chris,
> >>
> >>> Not pooling connections will
0, 2021 12:00 PM
>> To: Tomcat Users List > <mailto:users@tomcat.apache.org>>
>> Subject: RE: Do I Need Network NameSpaces to Solve This
>> Tomcat+Connector/J Problem?
>>
>> Chris,
>>
>>> Not pooling connections will very likely neg
cember 30, 2021 12:00 PM
> To: Tomcat Users List
> Subject: RE: Do I Need Network NameSpaces to Solve This
> Tomcat+Connector/J Problem?
>
> Chris,
>
> > Not pooling connections will very likely negatively affect performance.
> >
> > When you say "they
Sent: Thursday, December 30, 2021 12:00 PM
> > To: Tomcat Users List
> > Subject: Re: Do I Need Network NameSpaces to Solve This
> > Tomcat+Connector/J Problem?
> >
> > But they do not get a corresponding database instance?
> >
>
> They do. Each tomcat ins
> José,
>
> > -Original Message-
> > From: José Cornado
> > Sent: Thursday, December 30, 2021 12:00 PM
> > To: Tomcat Users List
> > Subject: Re: Do I Need Network NameSpaces to Solve This
> > Tomcat+Connector/J Problem?
> >
> >
José,
> -Original Message-
> From: José Cornado
> Sent: Thursday, December 30, 2021 12:00 PM
> To: Tomcat Users List
> Subject: Re: Do I Need Network NameSpaces to Solve This
> Tomcat+Connector/J Problem?
>
> But they do not get a corresponding database instance?
But they do not get a corresponding database instance?
On Thu, Dec 30, 2021 at 10:51 AM Eric Robinson
wrote:
> José,
>
> > Is this setup going to be open to the world or just a big organization?
> A big
> > organization would put a cap on the number of users. Then maybe they
> > could divide
Chris,
> Not pooling connections will very likely negatively affect performance.
>
> When you say "they ... have an issue with connection pooling" do you mean
> that they have a technical problem, or do you mean that there is some ill-
> conceived policy against them?
>
> Oh, maybe they are
Chris,
> Stupid question: can your database (meaningfully) handle the number of
> connections you are making to it? Let's say you have 5000 connections per
> Tomcat instance to your database, and you want 500 Tomcat instances.
> That means 250 database connections. If every single one of
Stefan,
> A third option could be to add something between database client and
> server. Something on layer 4 like multiple HAProxy servers or simple NAT
> gateways. Or more complex on layer 7 specfic products like ProxySQL or
> MaxScale. They could even pool connections and reduce the load on
José,
> Is this setup going to be open to the world or just a big organization? A big
> organization would put a cap on the number of users. Then maybe they
> could divide those between the tomcat instances thus the db server.
>
It's a SaaS solution, where each customer organization gets its own
Mark,
> > My question is, is there a better way?
>
> I can only think of variations on a theme.
>
> The ~64k limit assumes client IP, server IP and server port remain constant.
> i.e. just client port is varying.
>
> That suggests there is a single IP for the database server and that it is
>
Hi Simon,
> I guess the database is not on the Tomcat host, otherwise you could connect
> via unix domain socket to avoid the limitations of TCP port numbers.
>
> Otherwise I think you could run a db proxy where your Tomcat clients
> connect locally via unix domain socket and the proxy relays
Eric,
On 12/29/21 19:23, Eric Robinson wrote:
-Original Message-
From: Mark Eggers
Sent: Wednesday, December 29, 2021 6:18 PM
To: users@tomcat.apache.org
Subject: Re: Do I Need Network NameSpaces to Solve This
Tomcat+Connector/J Problem?
Eric:
On 12/29/2021 1:04 PM, Eric Robinson
Eric,
On 12/29/21 16:04, Eric Robinson wrote:
We want to run a large number of tomcat instances on the same server
without virtualization or containerization. Each instance is executed
from its own folder tree and listens on its own unique TCP port. Each
instance will run code that connects
Am 30.12.2021 um 12:24 schrieb Mark Thomas:
On 29/12/2021 21:04, Eric Robinson wrote:
My question is, is there a better way?
I can only think of variations on a theme.
The ~64k limit assumes client IP, server IP and server port remain
constant. i.e. just client port is varying.
That
Is this setup going to be open to the world or just a big organization? A
big organization would put a cap on the number of users. Then maybe they
could divide those between the tomcat instances thus the db server.
On Thu, Dec 30, 2021 at 4:24 AM Mark Thomas wrote:
> On 29/12/2021 21:04, Eric
On 29/12/2021 21:04, Eric Robinson wrote:
My question is, is there a better way?
I can only think of variations on a theme.
The ~64k limit assumes client IP, server IP and server port remain
constant. i.e. just client port is varying.
That suggests there is a single IP for the database
Hi,
> We want to run a large number of tomcat instances on the same server
> without virtualization or containerization. Each instance is executed from
> its own folder tree and listens on its own unique TCP port. Each instance
> will run code that connects to a backend database server to send
> Your problem seems to be in the client-to-db server side of things. Not
> tomcat as a server.
>
In the context of this question, tomcat is the client.
> On Wed, Dec 29, 2021 at 2:11 PM Eric Robinson
> wrote:
>
> > We want to run a large number of tomcat instances on the same server
> >
> -Original Message-
> From: Mark Eggers
> Sent: Wednesday, December 29, 2021 6:18 PM
> To: users@tomcat.apache.org
> Subject: Re: Do I Need Network NameSpaces to Solve This
> Tomcat+Connector/J Problem?
>
> Eric:
>
> On 12/29/2021 1:04 PM, Eric Robinson wro
Eric:
On 12/29/2021 1:04 PM, Eric Robinson wrote:
We want to run a large number of tomcat instances on the same server without
virtualization or containerization. Each instance is executed from its own
folder tree and listens on its own unique TCP port. Each instance will run code
that
Your problem seems to be in the client-to-db server side of things. Not
tomcat as a server.
On Wed, Dec 29, 2021 at 2:11 PM Eric Robinson
wrote:
> We want to run a large number of tomcat instances on the same server
> without virtualization or containerization. Each instance is executed from
>
We want to run a large number of tomcat instances on the same server without
virtualization or containerization. Each instance is executed from its own
folder tree and listens on its own unique TCP port. Each instance will run code
that connects to a backend database server to send queries that
28 matches
Mail list logo
