> On Aug 5, 2025, at 11:54 AM, Daniel Schwartz wrote:
>
> Hello again Rob,
>
> I just read that article you referenced by Cockroach Labs. I found the
> statement:
>
> "If we make the pool too small (i.e. choose too few connections), we’ll
> introduce latency, as operations have to wait
Hello Niranjan,
I just replied to Rob Sargent regarding this. Did you see that reply?
Maybe I’m not using Glassfish correctly, but if I set the maximum pool size to
1, the system almost immediately outputs an error message saying that it is
unable to allocate any more connections and crashes.
Hello again Rob,
I just read that article you referenced by Cockroach Labs. I found the
statement:
"If we make the pool too small (i.e. choose too few connections), we’ll
introduce latency, as operations have to wait for an available connection to
open up before they can execute."
This im
On 8/5/25 09:43, Daniel Schwartz wrote:
Well, I guess that this is a top post. But this message is getting
longer with all the replies. I don’t think it is a memory leak. I’m
fairly sure that I’m closing every connection immediately after using
it. It seems that most of my database
ZjQcmQRYFp
Well, I guess that this is a top post. But this message is getting longer with
all the replies.
I don’t think it is a memory leak. I’m fairly sure that I’m closing every
connection immediately after using it. It seems that most of my database
queries are coming from web crawlers, and there a
Harri,
On 8/5/25 2:40 AM, Harri Pesonen wrote:
Chris's article is fine except that it does not use the try-with-
resources feature of Java language:
try (Connection conn = getConnection()) {
try (Statement stmt = conn.createStatement()) {
try (ResultSet rs = stmt.executeQuery(sql)) {
On 05/08/2025 07:03, 加治屋 一輝 wrote:
Thank you for your response, Mark. Based on your answer, I have confirmed the
settings.
Please confirm the settings for maxPostSize and maxFileSize.
The settings are as follows.
- maxPostSize: set on the Connector. Sets the maximum total size for all
non-file
