Re: Subject: Nightmare with Tomcat 4.1 and SSL configuration
I've been adding more logging to the SSL components in TC 5.x (at DEBUG or TRACE level, so it doesn't show up unless you ask :). Some of that will likely find its way back into future versions of TC 4.1.x. At the moment, yes, the logging of errors (especially ones that could be config related) is pretty sparse. <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Cosmin > > I was stuck on the same issue for sometime. Then I realised that I had not > put the jsse jar in the classpath. So I copied the 3 jars - jsse.jar, > jnet.jar, jcert.jar into %JAVA_HOME%\jre\lib\ext. After that the problem > went away. > > However, I would like to understand how I can configure tomcat to see the > logs. When I was getting I didn't find an easy way to figure out why the > error was coming. > > > This communication is for informational purposes only. It is not intended as > an offer or solicitation for the purchase or sale of any financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements made herein > do not necessarily reflect those of J.P. Morgan Chase & Co., its > subsidiaries and affiliates. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Subject: Nightmare with Tomcat 4.1 and SSL configuration
Cosmin I was stuck on the same issue for sometime. Then I realised that I had not put the jsse jar in the classpath. So I copied the 3 jars - jsse.jar, jnet.jar, jcert.jar into %JAVA_HOME%\jre\lib\ext. After that the problem went away. However, I would like to understand how I can configure tomcat to see the logs. When I was getting I didn't find an easy way to figure out why the error was coming. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightmare with Tomcat 4.1 and SSL configuration
The standalone SSL connector for 4.1.24 only works with Sun's 1.4.x JVM. There is support in the CVS for other vendors. You could try checking out the coyote_10 branch of jakarta-tomcat-connectors, and see if you have more luck. "Cosmin" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi there , > I've just registered to this list in hope that I could find some better > advice here . I am trying to configure a standalone installation of tomcat > to work with SSL . This at first doesn't seem like a bit headache . I have > followed the two similar howtos at the sun website and jakarta website and > have gotten the same result . > > The only wierd thing about setting it all up was using keytool . I am > using a FreeBSD 4.8 machine with Tomcat 4.1 and linux-jdk1.4 . At first > the linux-jdk1.4 keytool didn't seem to work ( telling me that /dev/random > has reached the end of file ... i looked and this was a blank file ) . So > I generated they key using the FreeBSD jdk1.4 ( suposedly of alpha quality > ) , exported it to a file then imported this file into a new keystore : > /root/.keystore using the linux-jdk1.4/bin/keytool . > > I then added the following to my server.xml : > > port="8443" minProcessors="5" maxProcessors="75" >enableLookups="false" >acceptCount="100" debug="0" scheme="https" secure="true" >useURIValidationHack="false" disableUploadTimeout="true"> >className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory" >clientAuth="false" protocol="TLS" > keystoreFile="/root/.keystore" >keystorePass="changeit"/> > > > Tried restarting . As I was watching with netstat the 8180 port opened for > a split second then closed . Tomcat seems to die the moment i try to start > it with the ssl connector uncommented . The moment i put comments arround > the SSL connector Tomcat starts up and works fine again . . . > > > Has anybody here , ever encountered this miserable problem ? I've been > stuck on it for 2 days and I don't even get an error message to start from > somewhere . no error logs are... WOOPS :) ... found a very relevant error > : > > Exception during startup processing > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) > Caused by: java.lang.InternalError: URLSeedGenerator file:/dev/random > reached end of file > at > sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedByte(SeedGenerat or.java:476) > at > sun.security.provider.SeedGenerator.getSeedBytes(SeedGenerator.java:137) > and it goes on > > so that /dev/random file is creating trouble here . Does anybody here have > a clue on how to fix this ? > > thanks in advance > > Cosmin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Nightmare with Tomcat 4.1 and SSL configuration
my 2cents would be to use apache on the front to do the SSL... -Original Message- From: Cosmin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 4 June 2003 7:22 AM To: [EMAIL PROTECTED] Subject: Nightmare with Tomcat 4.1 and SSL configuration Hi there , I've just registered to this list in hope that I could find some better advice here . I am trying to configure a standalone installation of tomcat to work with SSL . This at first doesn't seem like a bit headache . I have followed the two similar howtos at the sun website and jakarta website and have gotten the same result . The only wierd thing about setting it all up was using keytool . I am using a FreeBSD 4.8 machine with Tomcat 4.1 and linux-jdk1.4 . At first the linux-jdk1.4 keytool didn't seem to work ( telling me that /dev/random has reached the end of file ... i looked and this was a blank file ) . So I generated they key using the FreeBSD jdk1.4 ( suposedly of alpha quality ) , exported it to a file then imported this file into a new keystore : /root/.keystore using the linux-jdk1.4/bin/keytool . I then added the following to my server.xml : Tried restarting . As I was watching with netstat the 8180 port opened for a split second then closed . Tomcat seems to die the moment i try to start it with the ssl connector uncommented . The moment i put comments arround the SSL connector Tomcat starts up and works fine again . . . Has anybody here , ever encountered this miserable problem ? I've been stuck on it for 2 days and I don't even get an error message to start from somewhere . no error logs are... WOOPS :) ... found a very relevant error : Exception during startup processing java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Caused by: java.lang.InternalError: URLSeedGenerator file:/dev/random reached end of file at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedByte(SeedGenerat or.java:476) at sun.security.provider.SeedGenerator.getSeedBytes(SeedGenerator.java:137) and it goes on so that /dev/random file is creating trouble here . Does anybody here have a clue on how to fix this ? thanks in advance Cosmin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightmare with Tomcat 4.1 and SSL configuration
Hi there , I've just registered to this list in hope that I could find some better advice here . I am trying to configure a standalone installation of tomcat to work with SSL . This at first doesn't seem like a bit headache . I have followed the two similar howtos at the sun website and jakarta website and have gotten the same result . The only wierd thing about setting it all up was using keytool . I am using a FreeBSD 4.8 machine with Tomcat 4.1 and linux-jdk1.4 . At first the linux-jdk1.4 keytool didn't seem to work ( telling me that /dev/random has reached the end of file ... i looked and this was a blank file ) . So I generated they key using the FreeBSD jdk1.4 ( suposedly of alpha quality ) , exported it to a file then imported this file into a new keystore : /root/.keystore using the linux-jdk1.4/bin/keytool . I then added the following to my server.xml : Tried restarting . As I was watching with netstat the 8180 port opened for a split second then closed . Tomcat seems to die the moment i try to start it with the ssl connector uncommented . The moment i put comments arround the SSL connector Tomcat starts up and works fine again . . . Has anybody here , ever encountered this miserable problem ? I've been stuck on it for 2 days and I don't even get an error message to start from somewhere . no error logs are... WOOPS :) ... found a very relevant error : Exception during startup processing java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Caused by: java.lang.InternalError: URLSeedGenerator file:/dev/random reached end of file at sun.security.provider.SeedGenerator$URLSeedGenerator.getSeedByte(SeedGenerator.java:476) at sun.security.provider.SeedGenerator.getSeedBytes(SeedGenerator.java:137) and it goes on so that /dev/random file is creating trouble here . Does anybody here have a clue on how to fix this ? thanks in advance Cosmin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
