Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] exhausting hibernate JDBC connection pool

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] exhausting hibernate JDBC connection pool

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: "Michael R. Gettes" <>, Scott Koranda <>
  • Cc: grouper-users <>
  • Subject: RE: [grouper-users] exhausting hibernate JDBC connection pool
  • Date: Wed, 2 Nov 2016 04:39:53 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:n2aFshYwIBgmxVtEmpI4cV7/LSx+4OfEezUN459isYplN5qZpMyzbnLW6fgltlLVR4KTs6sC0LuM9fC6EjNfqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i760zceF13FOBZvIaytQ8iJ3p7xh7r5pMKbSj4LrQL1Wal1IhSyoFeZnegtqqwmFJwMzADUqGBDYeVcyDAgD1uSmxHh+pX4p8Y7oGx48sgs/M9YUKj8Y79wDfkBVGxnYCgJ45ihkBjITQKC4jMmFC05nwZUDhOPpEX/RJiq6gPirfc71SWHa4m+drszRSjqzKBxQRnkgW9TLD0+6mjRhsVYg6dSoRbnrBt6ld36eoaQYbBeb7HQZ5dSbmpbX90bH3hECYOtfYYVJ+saNqBFt4T7oR0DoQboVlrkP//m1jId3iy+5qY9yel0VFiehAE=
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

We fixed this in august and it was supposed to be in a patch but it appears a
patch was never made. Sorry about that.

I just made one (patch 30). Yes, now that loader jobs are threaded, it uses
more connections, finishes faster.

Michael / Scott (not an "Office" reference) or anyone, if you think the
params in the default need to be changed let me know


-----Original Message-----

On Behalf Of Michael R. Gettes
Sent: Tuesday, November 01, 2016 7:35 PM
To: Scott Koranda
Cc: grouper-users
Subject: Re: [grouper-users] exhausting hibernate JDBC connection pool

Scott, while I can’t answer the why questions you ask I can share my recipe
after spending some time with Shilen at TechX and pushed me to really figure
this out. Here is what we use to manage about 64K course groups for last,
current and next semester. I run 2 loader jobs every morning and processing
takes about 1 hour on a 2 CPU VM with 12G (we run loader jobs on 2 instances
of Grouper against an Oracle DB on SSD disk). I hope this helps.

hibernate.c3p0.max_size = 40
hibernate.c3p0.min_size = 5
hibernate.c3p0.idle_test_period = 300
hibernate.c3p0.timeout = 1800
hibernate.c3p0.max_statements = 50
hibernate.c3p0.acquireIncrement = 1


> On Nov 1, 2016, at 17:33, Scott Koranda
> <>
> wrote:
> Hi,
> I am helping manage a large Grouper deployment that manages a
> number of groups for a campus, including groups that represent
> course offerings ("course groups").
> November 1 marks a "transition" from one set of course groups
> to another. The result is a large amount of work for 3 loader
> jobs that manage the course groups.
> In the past earlier versions of Grouper, all running on the
> same VM (no changes in the available resources have happened),
> have ridden out this transition without issue.
> Today, however, using Grouper version 2.3 was different. We
> saw that the loader consumed all of the available JDBC
> connections. The default was set in
> hibernate.c3p0.max_size = 16
> This caused a number of loader jobs, including maintenance
> jobs like CHANGE_LOG_changeLogTempToChangeLog, to be starved.
> Stopping the loader and changing to
> hibernate.c3p0.max_size = 32
> made the issue go away.
> My question is what might be different in Grouper version 2.3
> that caused all of the JDBC connections to be consumed where
> previously they were not?
> I am wondering if code has changed that causes the Grouper
> loader to be more "aggressive" in how it processes "a lot of
> work"?
> I also note that we did not see this issue on the dev system.
> That VM, however, has less CPU cores and memory available to
> it, so I am wondering if that constrained the loader in some
> way and prevented it from scaling up and exhausting the JDBC
> connections?
> I appreciate any input the Grouper team has.
> Thanks,
> Scott K

Archive powered by MHonArc 2.6.19.

Top of Page