Page History
...
If you'd like to try and do some debugging yourself, you can change the DSpace logger settings to
DEBUG
which will sometimes provide you with more information about the error. To turn on debugging, visit the[dspace]/config/log4j.properties
file and do the following:To enable DEBUG logging in the
dspace.log
file, change thelog4j.rootCategory
andlog4j.logger.org.dspace
settings toDEBUG
rather thanINFO
.(XMLUI Only) To enable DEBUG logging in the
cocoon.log
file, change thelog4j.logger.org.apache.cocoon
setting toDEBUG
rather thanINFO
.NOTE: You'll need to restart Tomcat after enabling DEBUG mode in the
log4j.properties
file.WARNING: Make sure to turn off debugging once you are finished. Leaving debugging turned on will cause the log files to grow very large very quickly!
Depending on where you got your Java runtime environment, you may have the
jps
command.jps -v
can show you the options actually used to run your Servlet container, which can be useful in debugging startup issues. A plainjps
command will list process IDs of running JREs, which you can use with your favorite process monitoring tools.jps
can only show processes which your user account is allowed to inspect, so you should run it as the user which runs the container, or as a superuser.
Report the Error and Describe How You Encountered It
...