download the source and read through it
to find out how things are being done.
- -chris
>> -Original Message- From: Christopher Schultz
>> Sent: Friday, March 27, 2020 1:42
>> PM To: users@tomcat.apache.org Subject: Re: Does Tomcat/Java get
>> around the problem o
> -Original Message-
> From: André Warnier (tomcat/perl)
> Sent: Saturday, March 28, 2020 5:35 PM
> To: users@tomcat.apache.org
> Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
> client source ports?
>
> On 27.03.2020 21:39, Eric Robinson wrot
On 27.03.2020 21:39, Eric Robinson wrote:
FYI, I don't have 1800 tomcat instances on one server. I have about 100
instances on each of 18 servers.
When one of these (attempted) connections fails, do you not get some error message which
gives a clue as to what the failure is due to ?
(should
Sent: Friday, March 27, 2020 1:42 PM
> To: users@tomcat.apache.org
> Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
> client source ports?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> André,
>
> On 3/27/20 11:01, André Warnier (tomcat/p
; Sent: Thursday, March 26, 2020 2:06 PM
>>>> To: users@tomcat.apache.org Subject: Re: Does Tomcat/Java get
>>>> around the problem of 64K maximum client source ports?
>>>>
>>>> Hi Eric,
>>>>
>>>> On 26.03.20 18:58, Er
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 3/27/20 13:37, john.e.gr...@wellsfargo.com.INVALID wrote:
> A few random thoughts.
>
> First, this is really a MySQL driver thing, not a Tomcat thing.
> If you want to know why the driver does what it does, look at the
> driver source.
Chris, André, Eric, etc,
A few random thoughts.
First, this is really a MySQL driver thing, not a Tomcat thing. If you want to
know why the driver does what it does, look at the driver source. There is
actually a Socket constructor that allows you to specify the local port. I
don't know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric,
On 3/26/20 13:58, Eric Robinson wrote:
> Many people say the maximum number of client ports is 64K.
> However, TCP connections only require unique sockets, which are
> defined as...
>
> local_IP:local_port -> remote_ip:remote_port
>
>
On 27.03.2020 14:27, André Warnier (tomcat/perl) wrote:
On 26.03.2020 20:42, Eric Robinson wrote:
-Original Message-
From: Olaf Kock
Sent: Thursday, March 26, 2020 2:06 PM
To: users@tomcat.apache.org
Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
client source
On 26.03.2020 20:42, Eric Robinson wrote:
-Original Message-
From: Olaf Kock
Sent: Thursday, March 26, 2020 2:06 PM
To: users@tomcat.apache.org
Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
client source ports?
Hi Eric,
On 26.03.20 18:58, Eric Robinson wrote
> -Original Message-
> From: Olaf Kock
> Sent: Thursday, March 26, 2020 2:06 PM
> To: users@tomcat.apache.org
> Subject: Re: Does Tomcat/Java get around the problem of 64K maximum
> client source ports?
>
> Hi Eric,
>
> On 26.03.20 18:58, Eric Robinson wrot
Hi Eric,
On 26.03.20 18:58, Eric Robinson wrote:
> Greetings,
>
> Many people say the maximum number of client ports is 64K. However, TCP
> connections only require unique sockets, which are defined as...
>
> local_IP:local_port -> remote_ip:remote_port
>
> Theoretically, it is possible for a
12 matches
Mail list logo
