grouper-users - RE: [grouper-users] no open GrouperSession detected from gsh
Subject: Grouper Users - Open Discussion List
List archive
- From: Chris Hyzer <>
- To: Colin Hudler <>, "" <>
- Subject: RE: [grouper-users] no open GrouperSession detected from gsh
- Date: Thu, 26 Jan 2012 16:45:17 +0000
- Accept-language: en-US
Maybe Shilen could respond in more detail, but a workaround could be to make
a file called badMemberships.gsh with these two lines:
GrouperSession.startRootSession();
FindBadMemberships.main(new String[]{"-all"});
And then run: gsh.sh badMemberships.gsh
Now sure about why daily report is failing...
Thanks,
Chris
-----Original Message-----
From:
[mailto:]
On Behalf Of Colin Hudler
Sent: Thursday, January 26, 2012 11:31 AM
To:
Subject: [grouper-users] no open GrouperSession detected from gsh
Grouper 1.6.3. When I run gsh.sh -findbadmemberships -all, it always says:
"Checking Composite Memberships
<..after a few minutes..>
There is no open GrouperSession detected. Make sure to start a grouper
session (e.g. GrouperSession.start() ) before calling this method"
Then it exits.
I've hit a dead end debugging it. I can see that the callstack at the
point it dies:
main
GrouperSession.staticGrouperSession(boolean) line: 755
GrouperSession.staticGrouperSession() line: 724
Composite._getGroup(String) line: 287
Composite.getOwnerGroup() line: 180
FindBadMemberships.foundError(Composite) line: 264
FindBadMemberships.checkComposites() line: 169
FindBadMemberships.checkAll(PrintStream) line: 150
FindBadMemberships.main(String[]) line: 114
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line:
not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 597
GrouperShell.handleSpecialCase(String[]) line: 188
GrouperShell.main(String[]) line: 128
GrouperShellWrapper.main(String[]) line: 16
The last call into staticGrouperSession() comes from
FindBadMemberships.foundError(), when it apparently triggers a
permissions check. However, I know there's a grouper session, right?
Could it get this far without one? Debugging shows multiple successful
uses of staticGrouperSession() during initialization, even with
exceptionOnNull == true.
Debugging reveals that GrouperSession grouperSession =
staticGrouperSession.get() is indeed null, but only when it was called
from FindBadMemberships.foundError(), rather than (say) various calls
through GrouperCheckConfig.
The problem also appears in the shell if I invoke
FindBadMemberships.checkAll(System.out) without at least storing a
grouper session in some variable. Unfortunately, I can't work around it
always, I suspect this is also killing our loader grouper reports.
Any ideas?
- [grouper-users] no open GrouperSession detected from gsh, Colin Hudler, 01/26/2012
- RE: [grouper-users] no open GrouperSession detected from gsh, Chris Hyzer, 01/26/2012
- Re: [grouper-users] no open GrouperSession detected from gsh, Shilen Patel, 01/30/2012
- RE: [grouper-users] no open GrouperSession detected from gsh, Chris Hyzer, 01/26/2012
Archive powered by MHonArc 2.6.16.