Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] After error, change log temp to change log job no longer runs

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] After error, change log temp to change log job no longer runs


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Peter DiCamillo <>, "" <>
  • Subject: RE: [grouper-users] After error, change log temp to change log job no longer runs
  • Date: Tue, 4 Oct 2011 04:49:10 +0000
  • Accept-language: en-US

Stop it, ps and make sure the java isn't running, and start again. There is
nothing stored about its state, and it should start. After 50 seconds after
the minute do a jstack on the pid and see if it is hung somewhere.

Thanks,
Chris

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


[mailto:]
On Behalf Of Peter DiCamillo
Sent: Tuesday, October 04, 2011 12:19 AM
To:

Subject: [grouper-users] After error, change log temp to change log job no
longer runs

I've been working on putting the Grouper change log into production with
Grouper 1.6.3. It was working well until one run of the change log temp
to change log job got an out of heap space error message. I can increase
the heap space. But the problem I'm having now is that the change log
temp to change log job no longer runs. I restarted the Grouper Loader,
but there are no longer any log entries for the change log temp to
change log job. When it was working, there were log entries like this:

> 2011-09-20 00:08:00,021 INFO log.EventLog:
> [f2d8dde7cad54711ae047d3eaa3cf641,'GrouperSystem','application'] session:
> start (4ms)
> 2011-09-20 00:08:50,025 INFO log.EventLog:
> [bfdef815f6864b8fb0035266892959a6,'GrouperSystem','application'] session:
> start (5ms)
> 2011-09-20 00:09:00,019 INFO log.EventLog:
> [320b955fc07b41d695b3d86c210234d8,'GrouperSystem','application'] session:
> start (4ms)
> 2011-09-20 00:09:50,015 INFO log.EventLog:
> [886d80b1bcf74ad7b16dad3d5fb8f3c3,'GrouperSystem','application'] session:
> start (4ms)

where the ones at :50 are the change log temp to change log job and the
ones at :00 are our local consumer. This line appears in the log:

> 2011-09-20 15:34:57,402 ERROR loader.GrouperLoaderJob: Error on job:
> CHANGE_LOG_changeLogTempToChangeLog

then the traceback with "Caused by: java.lang.OutOfMemoryError: Java
heap space." Now when I run the Grouper Loader, all I get is this, just
the local consumer:

> 2011-09-20 23:29:00,025 INFO log.EventLog:
> [ec74b4c71bef4a63bf90b755b7c3b263,'GrouperSystem','application'] session:
> start (4ms)
> 2011-09-20 23:30:00,017 INFO log.EventLog:
> [31f8113e88604ee1b63afadc3bf80e4a,'GrouperSystem','application'] session:
> start (3ms)
> 2011-09-20 23:31:00,017 INFO log.EventLog:
> [2fda2e9e68d7499f88362d333d046515,'GrouperSystem','application'] session:
> start (4ms)

even though the properties files are unchanged. Also, I checked the size
of the temp entry table in the database, and the size increases when
changes are made, but never decreases.

Is that fact that the change log temp to change log job failed stored
somewhere? Is there something I have to reset so it will run again?

Peter




Archive powered by MHonArc 2.6.16.

Top of Page