I'm running into your exact same problem. Did going to the jdbc2 pool fix this?
Travis McCauley University of Virginia Library
At first, I wasn't calling Torque at all -- I was using Jetspeed's security manager. Once the problem cropped up, I tried calling Torque directly to get a connection to test, and made sure I was returning the connection then.
The test code didn't make it die any sooner, though.
I'm going to try the jdbc2 pool.
Keeney, Thomas wrote: Robert,
I wrote a similar cron job for Jetspeed/Torque awhile back. Check your code to make sure that connections retrieved for Torque are released after use. In older versions of Torque you have to release connections manually if you're retrieving connections from a database other than the default.
Otherwise, I'd suggest you post the source or more details so we can investigate further.
We have an application based on Jetspeed that periodically (every 5 minutes) updates the user list from another system. In testing, and for short terms, everything works perfectly. However, after about two days of continuous operation, the system can no longer make a connection to the local MySQL database, making it impossible for users to log in.
MySQL has a default limit of 100 connections. We have Torque configured to a limit of 10 connections at once.
It appears there's a leak in the Torque connection pool. Has anyone else run into this before? Any recommendations on where to start looking to fix it?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
