Daniel, You have a leak - this we are certain of. You just don't yet know what causes it (it's clearly not a "standard use case" and the robots are likely triggering it).
If I have my bets it is an unhandled unchecked exception (I'd even guess that it is likely a NumberFormatException) while processing one of your operations. Since you are reluctant to move your code to "try-with-resources" handling of the resource objects (which would make the code easier to read and avoid this problem), you will continue to see the problem unless you ensure that you are catching all exceptions (e.g. Throwable) (which is a bad practice in general). The 388 connection cound is the existing leaked connections from previous operations since you last started the Glassfish server and pool. I did suggest you restart Glassfish after adjusting that parameter to reset the numbers and the systems. >From my testing, I am very confident that the different versions will not behave differently in the context of your application. Please have some confidence that we do know what we are talking about. Your problem is common and not unique. If I get some time, and with your permission, I might try to look at your server operations and see if I can trigger it for you... but if you share the code for all the operations (no need to share the DB queries, just the Java code), I bet we can find it quickly. However, us solving it for you avoids you benefiting from the learning experience. Robert On Mon, Aug 18, 2025 at 10:44 AM Daniel Schwartz <d...@danielgschwartz.com> wrote: > Chris, > > I thought it was you. I too have a job and family, and this is only a > side project, so my time also is limited. > > Anyway, I'm wondering if there really is a problem, or whether this is > just normal Glassfish behavior. Yesterday I changed the Glassfish settings > so that leak monitoring is activated, and today I got: > > NumPotentialConnLeak 0 count Aug 8, 2025 3:18:57 PM -- -- > Number of potential connection leaks > > Also, this value: > > NumConnUsed 388count Aug 4, 2025 2:47:24 AM Aug 18, 2025 > 2:34:54 PM High Water Mark: 390 count > Low Water Mark: 0 count > Provides connection usage statistics. The total number of connections that > are currently being used, as well as information about the maximum number > of connections that were used (the high water mark). > > Has remained unchanged at 388. > > There has been suspicion that my system has a memory leak, but all > indications are that this is not happening. > > I'm currently trying to upgrade to the current version of Glassfish to see > if this behaves differently, but haven't gotten it working yet. > > Dan > > > -----Original Message----- > From: Christopher Schultz <ch...@christopherschultz.net> > Sent: Monday, August 18, 2025 10:29 AM > To: users@tomcat.apache.org > Subject: Re: [EXTERNAL EMAIL] How to access a REST service > > Daniel, > > On 8/16/25 10:57 PM, Daniel Schwartz wrote: > > There was a Chris too, but I think he made his recommendation and > > left. > I'm still here, but I do have a job and a family. Rob, Robert and Chuck > were making plenty of noise so I decided to reduce the clutter. > > > I'm coming to think that his advice was the best, namely, to just live > > with the current situation as long as it is working. > I gave no such advice. I think you should chase this down until you > understand the cause and have it fixed. > > -chris > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >