I was thinking about this, and did reset it to 10. I'll watch and see if anything happens.
Someone on the Eclipse email list replied. I'll hope he can help. Dan -----Original Message----- From: Robert Turner <rtur...@e-djuster.ca.INVALID> Sent: Sunday, August 17, 2025 8:56 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: [EXTERNAL EMAIL] How to access a REST service IIRC, the setting is the number of seconds before reporting a connection as leaked. So, because most of your connections should be very short-lived, it should probably work. I would typically suggest a larger number as applications often have more variability in their use of connections (so something more like 10 seconds, or a few minutes if the application generates reports). Applications could even have different pools with different settings for use in different use cases. Unfortunately I cannot really help with the Glassfish migration as I have literally only used it over that past couple of days to assist with your issue. Good luck there. That might be a better topic for a Glassfish mailing list as opposed to this one. The suggestions I made were just general ones for migrating any text configuration from one version to another. Robert On Sun, Aug 17, 2025, 20:44 Daniel Schwartz <d...@danielgschwartz.com> wrote: > Okay, I have changed it to "1". Does this seem reasonable? I don't > know what would be a good setting. > > I have found some documentation on the Eclipse website, but it's a bit > confusing. But I am having contact with someone in that group. Maybe > he can help. I tried to duplicate the configuration I have for > version 4.1, but this doesn't seem to work for version 7.0.25. > > -----Original Message----- > From: Robert Turner <rtur...@e-djuster.ca.INVALID> > Sent: Sunday, August 17, 2025 8:19 PM > To: Tomcat Users List <users@tomcat.apache.org> > Subject: Re: [EXTERNAL EMAIL] How to access a REST service > > Yes, 0 is the default (in both versions) which means leak detection is > disabled. That is likely why Glassfish has never reported a leak. > > > > You should be able to update your 4.1 config using the UI or the > asadmin tool. > > I don't know how well copying the setup works between the versions. I > know I was able to copy bits from the 7.0.25 configuration to the 4.1 > configuration because the UI was having issues for me in 4.1. > > I would treat the version 7 migration separately and often it's better > to start with the new out of box configuration and apply only your > changes to the new system as often system defaults are changed, or new > features configured by default. You risk potentially having a less > modern config if you copy the whole config over. > > One way to do this is compare your config to the baseline 4.1 config > (diff is your friend here), and then only apply the changes to the new > system, keeping in mind that you may need to adapt and update > configuration between versions. > > Robert > > On Sun, Aug 17, 2025, 20:04 Daniel Schwartz <d...@danielgschwartz.com> > wrote: > > > Hi Robert, > > > > I just checked. The Connection Leak timeout is set to 0. This > > evidently is the default. > > > > I have been trying to upgrade to the latest version of Glassfish, 7.0.25, > > on my local PC. Am working on this. I tried to copy the setup I have > for > > 4.1, but am finding that the > > the instructions for setting up connection pooling are different. > > > > Dan > > > > -----Original Message----- > > From: Robert Turner <rtur...@e-djuster.ca.INVALID> > > Sent: Sunday, August 17, 2025 2:13 PM > > To: Tomcat Users List <users@tomcat.apache.org> > > Subject: Re: [EXTERNAL EMAIL] How to access a REST service > > > > So, a quick question Dan: > > > > Have you enabled Glassfish JDBC pool leak detection? (On the > > advanced page, under connection settings, the value for "Connection > > leak > > timeout") > > > > If this has not been set to a non zero value, Glassfish will not > > report connection leaks. > > > > Turn this on, reset your Glassfish server.... And then give it some > > time and check your stats and logs again... > > > > Robert > > > > On Sun, Aug 17, 2025, 12:08 Daniel Schwartz > > <d...@danielgschwartz.com> > > wrote: > > > > > Rob, > > > > > > A few years ago, I tried to upgrade to the then current version of > > > Glassfish and couldn’t get it to work. I’m considering trying > > > again with the current version. > > > > > > Dan > > > > > > From: Rob Sargent <rsarg...@xmission.com> > > > Sent: Sunday, August 17, 2025 12:04 PM > > > To: Tomcat Users List <users@tomcat.apache.org> > > > Cc: Tomcat Users List <users@tomcat.apache.org> > > > Subject: Re: [EXTERNAL EMAIL] How to access a REST service > > > > > > > On Aug 17, 2025, at 9:45 AM, Daniel Schwartz > > > > <d...@danielgschwartz.com > > > <mailto:d...@danielgschwartz.com>> wrote: > > In my previous > > > posting, at the very end, I mentioned that I’m using jdk1.8.0_144 > > > with Glassfish > > 4.1. > > > That version of Glassfish won’t with anything > > > NkdkJdXPPEBannerStart Be Careful With This Message From (Rob > > > Sargent <rsarg...@xmission.com>)< > > > https://godaddy1.cloud-protect.net/email-details/?k=k1&payload=536 > > > 16 > > > c7 > > > 465645f5fb70309feed1540f62bf005f376466654632bc67d49f0bed3805175f30 > > > 0a > > > 50 > > > 1ae2f740bb4af833d74c3785a23f41bdf314722f11baa7ef211e0e17b2cde5c1e0 > > > 34 > > > c3 > > > 7a2e487e93b6e168f982896f75359bfa9bc33e0f6f0964ba443f713b7ada4fb6ad > > > 18 > > > 28 > > > 6a887356573683c9e4aef9025af8cb762ba72c9b9122add03ebdc078d6874c9afe > > > 71 > > > d0 > > > 9f54b8c08dee1776b2dc2f9ae1fe71e47d4d8c5b63ac920101f367cead12d29f0f > > > 1c > > > fd > > > a17e934d5e1c8141ebeab30754937d86c5c118a22612f7381978a5a78f914c7321 > > > 0b > > > 92 > > > 23f440e75ce7478819bda3bac4d72b9c5c7c950c13f1b5c8968d6 > > > > > > > Learn More< > > > https://godaddy1.cloud-protect.net/email-details/?k=k1&payload=536 > > > 16 > > > c7 > > > 465645f5fb70309feed1540f62bf005f376466654632bc67d49f0bed3805175f30 > > > 0a > > > 50 > > > 1ae2f740bb4af833d74c3785a23f41bdf314722f11baa7ef211e0e17b2cde5c1e0 > > > 34 > > > c3 > > > 7a2e487e93b6e168f982896f75359bfa9bc33e0f6f0964ba443f713b7ada4fb6ad > > > 18 > > > 28 > > > 6a887356573683c9e4aef9025af8cb762ba72c9b9122add03ebdc078d6874c9afe > > > 71 > > > d0 > > > 9f54b8c08dee1776b2dc2f9ae1fe71e47d4d8c5b63ac920101f367cead12d29f0f > > > 1c > > > fd > > > a17e934d5e1c8141ebeab30754937d86c5c118a22612f7381978a5a78f914c7321 > > > 0b > > > 92 > > > 23f440e75ce7478819bda3bac4d72b9c5c7c950c13f1b5c8968d6 > > > > > > > Potential Impersonation > > > The sender's identity could not be verified and someone may be > > > impersonating the sender. Take caution when interacting with this > > message. > > > > > > NkdkJdXPPEBannerEnd > > > > > > > > > > > > > > > > > > > On Aug 17, 2025, at 9:45 AM, Daniel Schwartz > > > > <d...@danielgschwartz.com > > > <mailto:d...@danielgschwartz.com>> wrote: > > > > > > > > > > > > > > In my previous posting, at the very end, I mentioned that I’m > > > > using > > > jdk1.8.0_144 with Glassfish 4.1. That version of Glassfish won’t > > > with anything later than 1.8. > > > > > > > > > > > > > > Dan > > > > > > > > > > > > Are these specs for glassfish and java requirements? A new jdk is > > > an easy install and a current glassfish would be a real security > > enhancement. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > -- > > > - > > > > > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org<mailto: > > > users-unsubscr...@tomcat.apache.org> > > > > > > For additional commands, e-mail: users-h...@tomcat.apache.org<mailto: > > > users-h...@tomcat.apache.org> > > > > > > > > > > > >
