Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Member Change Subject RuntimeException

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Member Change Subject RuntimeException


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Kumi Hagimoto <>, "" <>
  • Subject: RE: [grouper-users] Member Change Subject RuntimeException
  • Date: Tue, 8 Dec 2015 18:32:01 +0000
  • Accept-language: en-US

Can you send the full logs please including all relevant stacktraces?

Thanks,
Chris

-----Original Message-----
From:


[mailto:]
On Behalf Of Kumi Hagimoto
Sent: Friday, December 04, 2015 2:57 PM
To:

Subject: [grouper-users] Member Change Subject RuntimeException

Hello,

I'm getting the following RuntimeException with Member Change Subject in our
dev env. (Grouper 2.2.1, subject source ldap) The same code runs without an
error (on same subject change) in the production env (same version and subject
source).

==== Exception ====
There were 0 successes and 1 failures of changing members
subjects.java.lang.RuntimeException: Unexpected update attempt on effective
membership.,
Exception in update: edu.internet2.middleware.grouper.Membership,
edu.internet2.middleware.grouper.hibernate.ByObject@7d07e84d,
Problem in HibernateSession: HibernateSession (161bd431): notNew, notReadonly,
READ_WRITE_NEW, activeTransaction, session (1224575c),
Exception in update: edu.internet2.middleware.grouper.Membership,
ByObjectStatic, query: ', cacheable: null, cacheRegion: null, entityName:
ImmediateMembershipEntry, tx type: null,
, this subject: Subject id: pancakec, sourceId: ldap, new subject: Subject id:
pancake, sourceId: ldap, deleteOldMember: true, report? false,
Problem in HibernateSession: HibernateSession (7138a3eb): new, notReadonly,
READ_WRITE_NEW, notActiveTransaction, session (1224575c)
at
edu.internet2.middleware.grouper.Membership.onPreUpdate(Membership.java:2395)
...
==================

We have composite groups in dev but not in production, so the fact that we
only get error in dev makes sense. Any idea how I can resolve this? Is
there a way to call the Member Change Subject such that it only updates the
systemOfRecord-type memberships?

Thanks!
Kumi



Archive powered by MHonArc 2.6.16.

Top of Page