On Tue, 08 Jun 1999, you wrote:
>I posted a few days ago a message on the same subject, but got no answer...
>I have the same symptoms when I look in the Apache log.
>
>The jservrunner is working fine. I am using the config files generated by
>configure. I do not have any CLASSPATH variable defined, but I declare all
>the correct pathes (triple-checked that !) in the config files, one per
>line.
>
>When I look into the Jserv log file, it gives a more accurate diagnostic,
>telling it cannot connect to
>127.0.0.1:8007.
Here is the difference between your case and mine: in your case jserv
actually is started. In my case the JServ classes simply can't be loaded,
and there is no jserv.log.
In your case you should check whether the port 8007 is already occupied
by another process or by a previously started JServ process. Maybe rebooting
the machine helps.
Anyway right now I have solved my problem. I simply exchanged the line
wrapper.classpath=$CLASSPATH
by several lines containing all entries of the classpath variable. For some
strange reason specifying the $CLASSPATH variable in jserv.properties
doesn't work on the one machine, while it indeed works on the other one...
and the error message in httpd.errors.log leaded me to the completely wrong
track by assuming that really the JServ classes aren't found ('Can't find
class org.apache.jserv.JServ) while it now seems as even the standard classes
weren't found at all.
Precise error messages are the key for quick problem solution.
bye
Sam Jordan
-- --------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
