Grouper Users - Open Discussion List

["RL 'Bob' Morgan" <>]

> Yup. You need to run something like
>
>    java -cp <location of hsqldb.jar> \
>        org.hsqldb.Server \
>        -database.0 <location of grouper database> \
>        -dbname.0 grouper \
>        -user sa
> ...
> (presuming localhost, of course). Note that <location of grouper 
> database> is the pathname of the .script file, exclusive of '.script'. 
> So, if you've got a database in '/opt/registries/grouper-demo.script', 
> put '/opt/registries/grouper-demo' as the -dbname.0 parameter value.

I guess in the qs case this would be

  grouper-qs/grouper/dist/run/grouper.script

which contains 1MB or so of sql.  So I did the above command, and indeed 
hsqldb now appears to be running on port 9001.  Unfortunately when trying 
the web login as GrouperSystem I get the same error page result as before, 
even after restarting tomcat (ie, "GrouperSystem is not recognised at 
...").

So, I tried modifying log4j.properties to have

log4j.logger.edu.internet2.middleware.subject           = DEBUG, stdout, 
rfile
log4j.logger.edu.internet2.middleware.subject.provider  = DEBUG, stdout, 
rfile

so as to get some debug output (and also set a proper log file), and upon 
subsequent tomcat restart grouper fails to initialize, apparently with an 
error of:

2005-10-07 16:59:34,229 ERROR [/grouper]: Error configuring application 
listener of class 
edu.internet2.middleware.grouper.ui.GrouperSessionAttributeListener
java.lang.NoClassDefFoundError: 
javax/servlet/http/HttpSessionAttributeListener

After this, even when setting log4j.properties back to its original state 
grouper fails to initialize.  I was able to start from scratch again by 
reloading the war file, but I find myself unable to touch 
log4j.properties without breaking the whole thing.  So, time to go home 
...

 - RL "Bob"