You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Peter Flynn <pf...@imbolc.ucc.ie> on 2000/10/20 11:10:26 UTC

Nearly there

mod_jserv.log says

[19/10/2000 16:35:01:431] (ERROR) wrapper: printing debugging information (command line, env)
[19/10/2000 16:35:01:443] (ERROR) wrapper: argument[ 0] /opt/IBMJava2-13/jre/bin/java
[19/10/2000 16:35:01:443] (ERROR) wrapper: argument[ 1] org.apache.jserv.JServ
[19/10/2000 16:35:01:444] (ERROR) wrapper: argument[ 2] /etc/httpd/conf/jserv/jserv.properties
[19/10/2000 16:35:01:444] (ERROR) wrapper: environment[ 0] PATH=/bin:/usr/bin:/usr/local/bin
[19/10/2000 16:35:01:444] (ERROR) wrapper: environment[ 1] CLASSPATH=/usr/lib/apache/ApacheJServ.jar:/home/httpd/classes/servlet-2.0.jar:/opt/xerces-j/xerces.jar:/opt/xerces-j/xercesSamples.jar:/opt/xalan-j/xalan.jar:/opt/xalan-j/bsf.jar:/opt/xalan-j/bsfengines.jar:/opt/cocoon/bin/Cocoon.jar:/opt/cocoon/bin/fop.jar

but presumably you have to guess what the error was (some file not
found? Nope, all the ones referenced are there, and the classes are in
the path). 

It is presumably trying to execute /opt/IBMJava2-13/jre/bin/java,
which is indeed where java lives; and org/apache/jserv/JServ.class is
indeed in /usr/lib/apache/ApacheJServ.jar, which is first in the
classpath; and /etc/httpd/conf/jserv/jserv.properties is in place and
appears to be correct, because that's where it got the binary and
classpath from.

So it is possible to find out what exactly it thinks the error is?

///Peter