I've been up and down for three blasted days total trying to get Resin installed successfully. I've gotten to the point of near abandonment.
Tomcat, I have no problem with. But when I shut down Tomcat, and attempt to load up my newly installed Resin via httpd.exe, I get a bundle of inexplicable madness. Can anyone explain the following:
C:\resin-3.0.9>httpd.exe
Can't find
java executable in C:\j2sdk1.4.2_03\bin
Couldn't start "(null)" -classpath ".;C:\resin-3.0.9;C:\tomcat\Tom5.0\common\lib\servlet-api.jar;C:\j2sdk1.4.2_03\xerces-2_6_1\xml-apis.jar;C:\j2sdk1.4.2_03\xerces-2_6_1\xerc
esImpl.jar;C:\j2sdk1.4.2_03\xerces-2_6_1\xercesSamples.jar; C:\j2sdk1.4.2_03\jre\lib\ext;C:\tomcat\Tom5.0\webapps\icds\WEB-INF\source;C:\resin-3.0.9\classes;C:\resin-3.0.9\lib
\resin.jar;C:\tomcat\Tom5.0\common\lib\servlet-api.jar;C:\j2sdk1.4.2_03\xerces-2_6_1\xml-apis.jar;C:\j2sdk1.4.2_03\xerces-2_6_1\xercesImpl.jar;C:\j2sdk1.4.2_0
3\xerces-2_6_1\xercesSamples.jar; C:\j2sdk1.4.2_03\jre\lib\ext;C:\tomcat\Tom5.0\webapps\icds\WEB-INF\source" -Dresin.home="C:\resin-3.0.9" -Djava.util.logging.manager=com.cauc
ho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl com.caucho.server.resin.Resin -socketwait 3112.
I am fairly certain it is the first line that is of main concern, since I have altered my classpath and always the first line appears saying it can't find the executable in my java bin... Meanwhile, Tomcat is pleased with my paths (of thought and the like). What more could Resin possibly want from me?
Thank you to anyone with input.