Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] extremely long running actions in adminUI

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] extremely long running actions in adminUI

Chronological Thread 
  • From: Shilen Patel <>
  • To: David Langenberg <>
  • Cc: Grouper Dev <>
  • Subject: Re: [grouper-dev] extremely long running actions in adminUI
  • Date: Fri, 10 Dec 2010 09:05:25 -0500

Hi David,

The first thing this makes me wonder about is whether there's a performance issue that we may need to fix. How long did it take to add the composite group using GSH? Since this would end up adding 40K+ membership records in the database and another 40K+ records in the temp change log, this definitely wouldn't be a quick operation.

In any case, I suppose we can have an option in the admin UI to first check the number of composite memberships that would end up being created and inform the user if that exceeds some configured amount. Would that help?


-- Shilen

On 12/9/10 12:31 PM, David Langenberg wrote:
Hi All,

Yesterday, I was trying to use the AdminUI on grouper 1.6.2 to create a
decent size composite group (40,000+ members). The two groups which make up
the members are both composite groups themselves left-hand membership around
60,000 members right-hand an additional 10,000-odd members. The final group
was a complement of LHS& RHS. The AdminUI after about 1.5 hours sent back
a blank page. Checking the group's status showed no members. Here's the
logs from the time period:

2010-12-08 13:15:25,797: [TP-Processor5] INFO -< davel
session: start (2ms)
2010-12-08 14:54:58,505: [TP-Processor1] ERROR
GrouperCapableAction.execute(?) -< davel java.lang.IllegalStateException:
Grouper session subject is null, probably since it is stopped. Dont use it
anymore, start another,,group name:
uc:applications:mail_forwarding:authorized, compositeType: complement, left
group name: uc:applications:mail_forwarding:eligible, right group name:

I eventually got it working using GSH, but was wondering if this kind of
error is known? If so, are there any plans to augment the admin UI to tell
the user that their request is too large/long running?



David Langenberg
Identity Management
The University of Chicago

Archive powered by MHonArc 2.6.16.

Top of Page