Grouper Users - Open Discussion List

[Chris Hyzer <>]

Can you set your log level (with log4j.properties) to WARN globally, and send 
(just me) all the logs from the restart of Tomcat, to when you reproduce the 
error?

e.g. have something like this:

log4j.rootLogger  = WARN, grouper_error

And remove or comment out the other stuff below so it doesn't make it more 
restrictive in some packages...

If you are able to browse the groups/folders via the UI, then you are 
connecting to a database.  If the grouper.hibernate.properties is correct, 
then you are connecting to the right database...  hmmm

Thanks,
Chris

> -----Original Message-----
> From: Thomas M Goerger 
> [mailto:]
> Sent: Thursday, September 18, 2008 3:24 PM
> To: Chris Hyzer
> Cc: 
> 
> Subject: RE: [grouper-users] Hibernate problems
>
> Yesterday, we were getting an error of
>
> 2008-09-16 15:34:50,309:
> [edu.internet2.middleware.grouper.internal.dao.hib3.Hib3MemberDAO]
> could
> not insert:
> [edu.internet2.middleware.grouper.internal.dao.hib3.Hib3GroupDAO]
>
> Today, that error is not to be seen, for some reason.  It doesn't
> appear
> that the sources.xml is the problem, since Grouper can list all the
> group members and memberships just fine.  Just does not want to add
> Groups
> or Stems for some reason.  We did try rebooting the tomcat server to
> commit the deletion of a whitespace character in the password field of
> the
> hibernate properties file that I thought might be causing the problem.
> Didn't fix anything, unfortunately.
>
> ***********************************************************************
> **********
> * Tom Goerger                                  Email/Unix System
> Administrator  *
> *
> *
> * University of Minnesota                      Email:  
> 
> *
> * Operations, Infrastructure and Architecture  Phone:  4-5804
> *
> * Internet Services                            Office: 750 University
> Park Plaza*
> *
> *
> ***********************************************************************
> **********
>
> On Thu, 18 Sep 2008, Chris Hyzer wrote:
>
> > The grouper.hibernate.properties is what hibernate uses.
> > The other DB connection might be in sources.xml if you have a JDBC
> source (which it sounds like you don't).
> > Is there nothing else in the logs?  Might want to look up and down
> for anything with a related timestamp, and forward it along.
> > Also, might want to just try restarting the app server to rule out a
> caching problem...
> >
> > Let me know if you make any progress, and we can try more ideas.
> >
> > Kind regards,
> > Chris
> >
> > > -----Original Message-----
> > > From: Thomas M Goerger 
> > > [mailto:]
> > > Sent: Thursday, September 18, 2008 3:11 PM
> > > To: 
> > > 
> > > Subject: [grouper-users] Hibernate problems
> > >
> > > Hi,
> > >
> > > We're seeing some problems creating groups on our production
> instances.
> > > The error seen is:
> > >
> > > Error: Could not create folder. Error is 'cannot create child stem:
> > > Problem in HibernateSession: HibernateSession: isNew: false,
> > > isReadonly:
> > > false, grouperTransactionType: READ_WRITE_NEW'.
> > >
> > > Seems like there must be a permission problem somewhere, but I'm
> not
> > > certain as to where.
> > >
> > > A little background.  We've got three servers that the webapp is
> > > running
> > > on.  So we don't have to install ant on each of these servers and
> do a
> > > fresh webapp build on each, I've built the webapp on a test server
> in
> > > my
> > > home directory, and then passed this webapp to each of our web
> servers.
> > > One of our sys admins then exploded the war file in order to tweak
> each
> > > server with its corresponding ldap connection.  Now, I've still got
> an
> > > instance of the 1.1 webapp running on our test server pointed at
> the
> > > same
> > > database, and it can still create folders and groups just fine.
> Must
> > > be
> > > somewhere in the transition that some connection was not brought
> over
> > > properly.
> > >
> > > Is there any file integral to the Hibernate connection that might
> not
> > > have
> > > kept its connection when it was brought over to the production
> > > instance?
> > > I've checked out the Hibernate properties files, and didn't see
> > > anything
> > > amiss there.  What other files might Hibernate depend on to make
> its
> > > connection to the database?  Is there any local file that it might
> > > point
> > > to that might have its permissions set improperly, something like
> that?
> > > There must be something small that is being missed.  The whole
> > > interface
> > > is working except for the group/stem creation.  Adding members,
> ldap
> > > search and everything else is functioning normall.  Any help is
> greatly
> > > appreciated.
> > >
> > > Thanks!
> > >
> > >
> ***********************************************************************
> > > **********
> > > * Tom Goerger                                  Email/Unix System
> > > Administrator  *
> > > *
> > > *
> > > * University of Minnesota                      Email:  
> > > 
> > > *
> > > * Operations, Infrastructure and Architecture  Phone:  4-5804
> > > *
> > > * Internet Services                            Office: 750
> University
> > > Park Plaza*
> > > *
> > > *
> > >
> ***********************************************************************
> > > **********
> >