Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Re: grouper web service crash

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Re: grouper web service crash

Chronological Thread 
  • From: "Kediyal, Prashant" <>
  • To: Chris Hyzer <>, Shilen Patel <>
  • Cc: "" <>
  • Subject: [grouper-users] Re: grouper web service crash
  • Date: Tue, 14 Apr 2015 12:27:52 +0000
  • Accept-language: en-US
  • Authentication-results:; dkim=none (message not signed) header.d=none;

Hi Chris,

We have been experiencing a lot of problems where grouper web service is crashing almost once or twice every week.

Eventually we get the problem where grouper is unable to checkout jdbc connections. 

I tried to read the code at and am unsure if the problem arises because connections aren’t getting closed; one of the typical error we see in the logs is:

2015-04-13 20:04:32,656: [TP-Processor19] WARN  WsStemLookup.retrieveStemIfNeeded(208) - < etc:wsusers:grouper-wsuser-ursa - > - Invalid query: WsStemLookup[


2015-04-13 20:04:32,661: [pool-1-thread-750] ERROR Member$ -  - Error updating member attributes: 

edu.internet2.middleware.grouper.internal.dao.GrouperDAOException: Problem in HibernateSession: HibernateSession: isNew: true, isReadonly: false, grouperTransactionType: READ_WRITE_NEW

        at edu.internet2.middleware.grouper.hibernate.HibernateSession._internal_hibernateSessionCatch(

        at edu.internet2.middleware.grouper.hibernate.HibernateSession.callbackHibernateSession(

        at edu.internet2.middleware.grouper.Member$


        at java.util.concurrent.ThreadPoolExecutor.runWorker(

        at java.util.concurrent.ThreadPoolExecutor$


Caused by: java.lang.NoSuchFieldError: INSTANCE

        at edu.internet2.middleware.grouper.hibernate.HibUtils.hibernateType(

        at edu.internet2.middleware.grouper.hibernate.HibUtils.hibernateTypes(

        at edu.internet2.middleware.grouper.hibernate.BySqlStatic.attachParams(

        at edu.internet2.middleware.grouper.hibernate.BySql.executeSql(

        at edu.internet2.middleware.grouper.Member$2$1.callback(

        at edu.internet2.middleware.grouper.hibernate.HibernateSession.callbackHibernateSession(

From: Chris Hyzer <>
Date: Tuesday, March 24, 2015 at 11:02 AM
To: Prashant Kediyal <>
Cc: "" <>
Subject: RE: grouper web service crash

I think add more memory.


There are limits in the config files for max number of records retrieved, that might help.


Hmmm, not sure why not check out JDBC connections, maybe need to change a database setting or a config settings to have a larger pool?





From: Kediyal, Prashant []
Sent: Tuesday, March 24, 2015 2:00 PM
To: Chris Hyzer
Subject: grouper web service crash


Hi Chris,


We had an incident where grouper web service crashed. Tomcat logs showed that there was an out of heap memory exception.

We suspect that this was caused because an application was retrieving 10’s of thousands of groups information. Is there any way we 

could have configured grouper to fail more gracefully?


Secondly, the same application had typos in some web service requests and we saw invalid query being logged. Later on, grouper crashed

again because it could not check out a jdbc connection from the pool — had to restart tomcat again.


Any advice?


Archive powered by MHonArc 2.6.16.

Top of Page