Hello Eric, Thanx for your help.
https can be used with URLConnection in java 2. As I already mentioned, the same lines put in a sample app work fine. The sample app is not a servet - I also think that the problem is somewhere in Tomcat, though I am not running it with a security manager, so it should not block anything as far as I understand. I think it's about the classloading, but I am not sure. Is there any way I can log the classloading process? Thanx, David ----- Original Message ----- From: "Eric Emminger" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, September 09, 2003 8:55 PM Subject: Re: Please help! stuck with SSL problems > David > > David Bolshoy wrote: > > Hi all, > > > > I seem to be stuck with a strange SSL problem. I am trying to open a client SSL connection from inside Turbine service. > > I get the following error: > > java.net.SocketException: Default SSL context init failed: null > > > > The code is very simple: > > URL url = new URL(https://www.verisign.com); > > URLConnection connection = url.openConnection(); > > Are you sure https (note the 's') can be used with URLConnection? > > > This code works perfectly in a standalone sample app. I am running Blackdown JDK 1.4.1 (on RH 8), so JSEE is already inside my classpath. > > What is also strange, when I add -Djavax.net.debug=all , no debug output is ever seen! It seems like a classpath problem, but I am really not sure I have some other SSL implementation. > > Is the sample app also a servlet, or something else? Maybe Tomcat is > blocking with Catalina permissions. > > Eric > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
