-Original Message-
From: Robert Turner
Sent: Monday, August 11, 2025 10:12 PM
To: Tomcat Users List
Subject: Re: How to access a REST service
One additional set of suggestions for this project or for the future
(inline):
On Mon, Aug 11, 2025, 21:53 Daniel Schwartz wrote:
>
> DGS: A
I just saw this.
From: Rob Sargent
Sent: Monday, August 11, 2025 10:17 PM
To: Tomcat Users List
Cc: Tomcat Users List
Subject: Re: [EXTERNAL EMAIL] RE: How to access a REST service
> On Aug 11, 2025, at 7:54 PM, Daniel Schwartz
> mailto:d...@danielgschwartz.com>> wrote: > > Rob,
> > > The s
Robert,
See my replies.
Dan
-Original Message-
From: Robert Turner
Sent: Tuesday, August 12, 2025 11:09 PM
To: Tomcat Users List
Subject: Re: [EXTERNAL EMAIL] RE: How to access a REST service
Dan,
On Tue, Aug 12, 2025 at 10:38 PM Daniel Schwartz
wrote:
>
> DGS: For "Idle Timeout"
Dan,
On Tue, Aug 12, 2025 at 10:38 PM Daniel Schwartz
wrote:
>
> DGS: For "Idle Timeout", does this mean that after 300 seconds, if the
> connection hasn't been active, then it is made available for other
> connection requests. This would be my interpretation, but I'm not sure.
>
This normall
Hello Rob,
More remarks marked with DGS.
Dan
From: Rob Sargent
Sent: Tuesday, August 12, 2025 4:47 PM
To: Tomcat Users List
Cc: Tomcat Users List
Subject: Re: How to access a REST service
> On Aug 12, 2025, at 2:29 PM, Daniel Schwartz
> mailto:d...@danielgschwartz.com>> wrote: > > Hello
>
Robert,
See my replies.
Dan
-Original Message-
From: Robert Turner
Sent: Tuesday, August 12, 2025 5:06 PM
To: Tomcat Users List
Subject: Re: [EXTERNAL EMAIL] RE: How to access a REST service
Dan,
On Tue, Aug 12, 2025 at 4:43 PM Daniel Schwartz
wrote:
> Hello again, Robert,
>
> The
Dan,
On Tue, Aug 12, 2025 at 4:43 PM Daniel Schwartz
wrote:
> Hello again, Robert,
>
> The Glassfish Pool setup page shows the following defaults:
>
>Idle Timeout: 300 Seconds
>Maximum time that connection can remain idle in the pool
>
>Max Wait Time: 6 Milliseconds
>Amount o
> On Aug 12, 2025, at 2:29 PM, Daniel Schwartz wrote:
>
> Hello Felix,
>
> See my replies marked with DGS.
>
> Dan
>
> DGS: I explained this in a previous email. Each user interaction requires
> either 3 or 4 database queries. That’s how my system works. There’s no way
> around this.
Hello again, Robert,
The Glassfish Pool setup page shows the following defaults:
Idle Timeout: 300 Seconds
Maximum time that connection can remain idle in the pool
Max Wait Time: 6 Milliseconds
Amount of time caller waits before connection timeout is sent
Not knowing exactly w
Hello Felix,
See my replies marked with DGS.
Dan
From: Felix Schumacher
Sent: Tuesday, August 12, 2025 2:47 PM
To: users@tomcat.apache.org
Subject: Re: How to access a REST service
Am 08.08.25 um 18:21 schrieb Daniel Schwartz:
Hello Robert,
From your and other people's replies, I'm learn
Am 08.08.25 um 18:21 schrieb Daniel Schwartz:
Hello Robert,
From your and other people's replies, I'm learning that tracking down memory
leaks can be quite daunting and possibly beyond me.
I'm aware of the try-with-resources instruction and will look into it. I wrote
this code before learn
inline...
On Tue, Aug 12, 2025 at 1:46 PM Daniel Schwartz
wrote:
>
> DGS: I was going by what the person at Omnifish had told me. I just
> checked, and you can't set the maximum pool size to 1. The minimum is 8.
> So I did this and within seconds the system stopped working and I got the
> foll
Chris,
More replied labeled DGS below.
-Original Message-
From: Christopher Schultz
Sent: Tuesday, August 12, 2025 11:19 AM
To: users@tomcat.apache.org
Subject: Re: [EXTERNAL EMAIL] RE: How to access a REST service
Daniel,
On 8/11/25 9:38 PM, Daniel Schwartz wrote:
> Chris,
>
> Again
Daniel,
On 8/11/25 9:38 PM, Daniel Schwartz wrote:
Chris,
Again, see my replies marked DSG.
Dan
-Original Message-
From: Christopher Schultz
Sent: Monday, August 11, 2025 3:21 PM
To: users@tomcat.apache.org
Subject: Re: [EXTERNAL EMAIL] RE: How to access a REST service
Daniel,
On 8
Mark,
On 8/6/25 9:26 PM, Mark Gordon wrote:
My company just upgraded from jdk 8.5 and tomcat 8.5. We upgraded to jdk
24 and tomcat 11. We have used hotswapagent for years. Now I can't seem
to get it to work with jdk17+ and tomcat 11.
Is anyone using this? And if so, do you have any advice
Application should not crash if you fail to get database connection from pool.
Instead it should wait until the configured timeout is reached, and then it
will throw exception, which is SQLException if I recall correctly.
At that point you code will catch the exception and log it, but it will not
16 matches
Mail list logo
