> On Aug 4, 2025, at 8:11 PM, Daniel Schwartz <d...@danielgschwartz.com> wrote:
>
> Hello Rob,
>
> I don’t know what a “top post” is or why it should warrant an apology, but I
> appreciate your taking the time to reply. This looks interesting.
>
> I’m currently using Glassfish, which has built in connection pooling. I was
> having trouble with its crashing frequently with a message saying that it was
> unable to allocate any more connections. Then I learned that the default
> pool size was only 32 and that this is the maximum allowed number of
> concurrent connections, so I increased this to 1000, and now it runs fine.
> I am new at this, though, and any new info is helpful. Thanks.
>
> Dan Schwartz
1000 is a rather large number of open connections. For one thing they are quite
memory intensive. I suspect you are (still) leaking connections - not re-using
those with which you have completed a database task. You will likely hit the
same error if your system stays up for any length of time.
I recommend going back to Chris’s article to get this leak under control.
PS
This is a bottom post, wherein the new text follows the original.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
