I discovered my problem. The tomcat rpm for fedora core 2 was built with gcj, and it doesn't work with another jdk. I'll remove it and try to install from jpackage.org or apache.jakarta.org.
Thank you very much for your help. On Sat, 2004-08-21 at 10:54, Rob Scala wrote: > This is interesting. Here's what I got: > > Standalone java.version: 1.4.1_02 > Tomcat java.version: 3.4.0 > > 3.4 is also the version of gcc on my machine. > > It seems like there are two versions of java, but there is only one > executable on my machine called "java" (version 1.4.1_02). I wonder if > the 3.4 version goes by another name? > > So I tried setting PATH and JAVA_HOME, but it gave the same result. It > seems that the rpm installation of tomcat hard coded some things - there > is no catalina.sh. > > > On Sat, 2004-08-21 at 09:21, QM wrote: > > On Fri, Aug 20, 2004 at 10:36:22PM -0400, Rob Scala wrote: > > : When running a stand-alone program, it works fine, but within tomcat I > > : get an exception: "Protocol handler not found: https". > > : > > : I note that Security.getProviders() returns different provider lists. > > : With the stand-alone program, it gets the expected list: SUN, SunJSSE, > > : SunRsaSign, SunJCE, and SunJGSS. The same code in tomcat lists only one > > : provider: GNU. > > > > Any chance you're not using the JDK you think you are? > > > > Have a JSP print out the value of the system property "java.version" and > > see whether that matches the expected 1.4.1. > > > > Then: > > - search your system for other versions of the "java" binary > > - check what's the runtime $PATH of the Tomcat scripts > > - check for the $JAVA_HOME environment variable > > > > etc. > > > > > > -QM -- Rob Scala Scala Systems - custom software development http://www.scalasystems.com 860-443-5702 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
