Re: Location of JSSE .jar files in Tomcat 3.3?
I tried placing the JSSE jar files (all 3 of them) into $TOMCAT_HOME/lib/common, and that didn't work either. Basically, I have a SOAP application (bean) that attempts to open an SSL connection using https in the URL. The following error occurs in our logs: === Mon Nov 26 12:04:22 MST 2001 Exception establishing SSL connection java.net.MalformedURLException: unknown protocol: https === The following is the stdout.log file that Tomcat produced. Again, I'm find with installing the JSSE jars into $JAVA_HOME/jre/lib/ext, but I'd like to understand why this would be required... Thanks much for the help, Greg Bailey [EMAIL PROTECTED] --- stdout.log --- 2001-11-26 12:04:22 - DecodeInterceptor: Charset from session ISO-8859-1 2001-11-26 12:04:23 - DecodeInterceptor: Charset from session ISO-8859-1 [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: null; targetException=java.lang.IllegalArgumentException: Error opening socket: null] at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:324) at org.apache.soap.rpc.Call.invoke(Call.java:205) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1835) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1803) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1786) at com.ilink.websoap.SOAPBean.setHostName(SOAPBean.java:363) at com.ilink.websoap.VVLInterface.setHostName(VVLInterface.java:1402) at auth_1._jspService(auth_1.java:123) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(Unknown Source) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(Unknown Source) at org.apache.jasper.runtime.PageContextImpl.forward(Unknown Source) at logout_1._jspService(logout_1.java:63) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) at org.apache.tomcat.core.ContextManager.service(Unknown Source) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConnection(Unknown Source) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Unknown Source) at java.lang.Thread.run(Thread.java:498) Larry Isaacs [EMAIL PROTECTED] wrote: Subject: RE: Location of JSSE .jar files in Tomcat 3.3? Date: Tue, 20 Nov 2001 14:29:39 -0700 From: Larry Isaacs [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Tomcat 3.3 has more levels of classloaders that Tomcat 3.2.3, which is likely why this issue appears. Class visibility between classloaders may not allow the JSSE jars to function in lib/apps. They may need to be in the same classloader as some other jar. I haven't yet played using JSSE except for enabling SSL support. This worked with the jars in jre/lib/ext or lib/common. I assume you get some form of class not found error. If you have a stacktrace, I could tell more. Cheers, Larry -Original Message- From: Greg Bailey [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 4:14 PM To: [EMAIL PROTECTED] Cc: Greg Bailey Subject: Location of JSSE .jar files in Tomcat 3.3? Hi, I'm in the process of attempting to update our web environment from Tomcat 3.2.3 to Tomcat 3.3, and one of our applications (a SOAP one) failed to find JSSE classes. The 3 files jcert.jar, jnet.jar, and jsse.jar are all located in /var/tomcat/lib/apps, since they would potentially be shared by more than one web application. This worked in 3.2.3, and the only way I'm able to get this to work (so far) in 3.3 is to put these 3 jar files into /opt/IBMJava2-13/jre/lib/ext. My question is: why is this necessary? Shouldn't classes found in $TOMCAT_HOME/lib/apps be available to web applications? Thanks much for any insight into this-- Greg Bailey [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto
RE: Location of JSSE .jar files in Tomcat 3.3?
With the JSSE jars in lib/common, what is left in $JAVA_HOME/jre/lib/ext? One impact of moving just the JSSE jars to lib/common is that the jars that remain in jre/lib/ext can no longer see the classes in the JSSE jars. I'm not sure if some other jar(s) need to move with them to lib/common to retain visibility between them. If these other jar(s) can't leave jre/lib/ext, then the JSSE jars would have to be in jre/lib/ext. Cheers, Larry -Original Message- From: Greg Bailey [mailto:[EMAIL PROTECTED]] Sent: Monday, November 26, 2001 2:17 PM To: [EMAIL PROTECTED] Cc: Larry Isaacs; Greg Bailey Subject: Re: Location of JSSE .jar files in Tomcat 3.3? I tried placing the JSSE jar files (all 3 of them) into $TOMCAT_HOME/lib/common, and that didn't work either. Basically, I have a SOAP application (bean) that attempts to open an SSL connection using https in the URL. The following error occurs in our logs: === Mon Nov 26 12:04:22 MST 2001 Exception establishing SSL connection java.net.MalformedURLException: unknown protocol: https === The following is the stdout.log file that Tomcat produced. Again, I'm find with installing the JSSE jars into $JAVA_HOME/jre/lib/ext, but I'd like to understand why this would be required... Thanks much for the help, Greg Bailey [EMAIL PROTECTED] --- stdout.log --- 2001-11-26 12:04:22 - DecodeInterceptor: Charset from session ISO-8859-1 2001-11-26 12:04:23 - DecodeInterceptor: Charset from session ISO-8859-1 [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: null; targetException=java.lang.IllegalArgumentException: Error opening socket: null] at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTT PConnection.java:324) at org.apache.soap.rpc.Call.invoke(Call.java:205) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1835) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1803) at com.ilink.websoap.SOAPBean.doSimpleSOAPCall(SOAPBean.java:1786) at com.ilink.websoap.SOAPBean.setHostName(SOAPBean.java:363) at com.ilink.websoap.VVLInterface.setHostName(VVLInterface.java:1402) at auth_1._jspService(auth_1.java:123) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.facade.RequestDispatcherImpl.doForward(Unknown Source) at org.apache.tomcat.facade.RequestDispatcherImpl.forward(Unknown Source) at org.apache.jasper.runtime.PageContextImpl.forward(Unknown Source) at logout_1._jspService(logout_1.java:63) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java) at org.apache.tomcat.facade.ServletHandler.doService(Unknown Source) at org.apache.tomcat.core.Handler.invoke(Unknown Source) at org.apache.tomcat.core.Handler.service(Unknown Source) at org.apache.tomcat.facade.ServletHandler.service(Unknown Source) at org.apache.tomcat.core.ContextManager.internalService(Unknown Source) at org.apache.tomcat.core.ContextManager.service(Unknown Source) at org.apache.tomcat.modules.server.Ajp13Interceptor.processConne ction(Unknown Source) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Unknown Source) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( Unknown Source) at java.lang.Thread.run(Thread.java:498) Larry Isaacs [EMAIL PROTECTED] wrote: Subject: RE: Location of JSSE .jar files in Tomcat 3.3? Date: Tue, 20 Nov 2001 14:29:39 -0700 From: Larry Isaacs [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Tomcat 3.3 has more levels of classloaders that Tomcat 3.2.3, which is likely why this issue appears. Class visibility between classloaders may not allow the JSSE jars to function in lib/apps. They may need to be in the same classloader as some other jar. I haven't yet played using JSSE except for enabling SSL support. This worked with the jars in jre/lib/ext or lib/common. I assume you get some form of class not found error. If you have a stacktrace, I could tell more. Cheers, Larry -Original Message- From: Greg Bailey [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 4:14 PM To: [EMAIL PROTECTED] Cc: Greg Bailey Subject: Location of JSSE
Location of JSSE .jar files in Tomcat 3.3?
Hi, I'm in the process of attempting to update our web environment from Tomcat 3.2.3 to Tomcat 3.3, and one of our applications (a SOAP one) failed to find JSSE classes. The 3 files jcert.jar, jnet.jar, and jsse.jar are all located in /var/tomcat/lib/apps, since they would potentially be shared by more than one web application. This worked in 3.2.3, and the only way I'm able to get this to work (so far) in 3.3 is to put these 3 jar files into /opt/IBMJava2-13/jre/lib/ext. My question is: why is this necessary? Shouldn't classes found in $TOMCAT_HOME/lib/apps be available to web applications? Thanks much for any insight into this-- Greg Bailey [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Location of JSSE .jar files in Tomcat 3.3?
Tomcat 3.3 has more levels of classloaders that Tomcat 3.2.3, which is likely why this issue appears. Class visibility between classloaders may not allow the JSSE jars to function in lib/apps. They may need to be in the same classloader as some other jar. I haven't yet played using JSSE except for enabling SSL support. This worked with the jars in jre/lib/ext or lib/common. I assume you get some form of class not found error. If you have a stacktrace, I could tell more. Cheers, Larry -Original Message- From: Greg Bailey [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 20, 2001 4:14 PM To: [EMAIL PROTECTED] Cc: Greg Bailey Subject: Location of JSSE .jar files in Tomcat 3.3? Hi, I'm in the process of attempting to update our web environment from Tomcat 3.2.3 to Tomcat 3.3, and one of our applications (a SOAP one) failed to find JSSE classes. The 3 files jcert.jar, jnet.jar, and jsse.jar are all located in /var/tomcat/lib/apps, since they would potentially be shared by more than one web application. This worked in 3.2.3, and the only way I'm able to get this to work (so far) in 3.3 is to put these 3 jar files into /opt/IBMJava2-13/jre/lib/ext. My question is: why is this necessary? Shouldn't classes found in $TOMCAT_HOME/lib/apps be available to web applications? Thanks much for any insight into this-- Greg Bailey [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
