Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
I have followed your procedure which has been stated on
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html to use SSL or https
with JSSE implementation.
Below is configuration for my server.xml
Connector SSLEnabled=true acceptCount=100 clientAuth=false
disableUploadTimeout=true enableLookups=false
maxThreads=25
port=8443 keystoreFile=${user.home}/.keystore
keystorePass=my_password
protocol=org.apache.coyote.http11.Http11NioProtocol
scheme=https
secure=true sslProtocol=TLS /
where my_password for obvious reasons I do not provide to you.
As a matter of fact, I have generated two trusted certificate entries with
keytool:
keytool -list -keystore .keystore
Escriba la contrase±a del almacÚn de claves:
Tipo de almacen de claves: JKS
Proveedor de almacen de claves: SUN
Su almacen de claves contiene 2 entradas
root, 24/10/2012, trustedCertEntry,
Huella digital de certificado (MD5):
E2:FF:EB:EF:B5:FA:85:2F:B4:85:FC:1B:1E:0E:94:37
tomcat, 24/10/2012, trustedCertEntry,
Huella digital de certificado (MD5):
E2:FF:EB:EF:B5:FA:85:2F:B4:85:FC:1B:1E:0E:94:37
But when I put https://localhost:8443/ on my explorer page, this crashes
(tomcat server is running).
Any idea what is the problem?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Max Threads - Worker Threads clarification
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vicky, On 10/25/12 12:22 AM, vicky007aggar...@yahoo.co.in wrote: In my environment i am using Apache 2.2 Tomcat 6.0 version . @ Both of these are multi-threaded right? Tomcat is always multi-threaded capable but you could always configure it to only have 1 request-processing thread. Depending on which connector you use, you may only be able to handle 1 HTTP connection at a time. Apache httpd can be multi-threaded, depending on which MPM (multi-processing-module) you are using. Read the httpd documentation to see the differences. They are important enough to understand that I'm not going to give you a one-sentence description of them here: you really need to read the httpd documentation. @ what does apache prefork means? Read the docs. @ is there a way to check apache or tomcat is multi-threaded or only documentation is the way out ? Read the docs. At Apache level:- MaxClients - this is no. Of connections an apache can accept, so does this is for apache as a whole or is it refers to each child process of apache? Sorry, you're going to have to read the docs: that's what they are there for. @ so commection_pool_size doesnt need to be set if i want all my requests to be redirected to tomcat in case of multithreaded apache . Default value is one . Right ? The default value depends upon the httpd configuration, and mod_jk usually picks the right value. I wouldn't set it at all. £ Lc = number of connections each load balancer can handle Tc = L * Lc £ As per your above comment , can i consider Lc value as the Maxclients value ? It depends upon your configuration, but generally speaking, yes, MaxClients is the value for Lc. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCJZqgACgkQ9CaO5/Lv0PD63gCfZrYuENbphDRT9Re6qcKXWVcm KaQAnjS3VmOr0sphX2NxBVUAF9b+RZ/A =AZ3h -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
Hi Christopher:
What I tried to mean is that Internet explorer fails. I have attached image
file with the error generated(Internet Explorer error.gif).
By the way below is what Tomcat generates as log, once I started Tomcat and
after executing https://localhost:8443/ on my Internet Explorer:
25/10/2012 12:00:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un
rendimiento óptimo en entornos de desarrollo no ha sido hallada en
java.library.path:
C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program
Files (x86)\ATI
Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program
Files (x86)\Liquid Technologies\Liquid XML Studio
2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program
Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files
(x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files
(x86)\CVSNT\;.
25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-nio-8443]
25/10/2012 12:00:58 PM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector
INFO: Using a shared selector for servlet write/read
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 679 ms
25/10/2012 12:00:58 PM org.apache.catalina.core.StandardService startInternal
INFO: Arrancando servicio Catalina
25/10/2012 12:00:58 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\docs de la aplicación web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\examples de la aplicación
web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\host-manager de la
aplicación web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\manager de la aplicación
web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\ROOT de la aplicación web
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-nio-8443]
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 488 ms
Regards.
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Thursday, October 25, 2012 11:21:15 AM
Subject: Re: Implementing SSL and error invocating https://localhost:8443/
(Tomcat 7.0 on Windows 7)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel,
On 10/25/12 10:35 AM, Gabriel Huerta Araujo wrote:
I have followed your procedure which has been stated on
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html to use SSL
or https with JSSE implementation.
Below is configuration for my server.xml Connector
SSLEnabled=true acceptCount=100 clientAuth=false
disableUploadTimeout=true enableLookups=false maxThreads=25
port=8443 keystoreFile=${user.home}/.keystore
keystorePass=my_password
protocol=org.apache.coyote.http11.Http11NioProtocol
scheme=https secure=true sslProtocol=TLS /
where my_password for obvious reasons I do not provide to you.
As a matter of fact, I have generated two trusted certificate
entries with keytool:
keytool -list -keystore .keystore Escriba la contrase±a del almacÚn
de claves:
Tipo de almacen de claves: JKS Proveedor de almacen de claves: SUN
Su almacen de claves contiene 2 entradas
root, 24/10/2012, trustedCertEntry, Huella digital de certificado
(MD5): E2:FF:EB:EF:B5:FA:85:2F:B4:85:FC:1B:1E:0E:94:37 tomcat,
24/10/2012, trustedCertEntry, Huella digital de certificado (MD5):
E2:FF:EB:EF:B5:FA:85:2F:B4:85:FC:1B:1E:0E:94:37
But when I put https://localhost:8443/ on my explorer page, this
crashes (tomcat server is running).
What do you mean this crashes? Please be specific.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using
RE: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
Gabriel
unless you are using a cert from entrust, verisign or thawte you cannot
generate a certificate which will be trusted as a CA level cert by all versions
for all supported browsers
Buena Suerte,
Martin
__
Porfavor..no altere ni interruptir esta communicacion..Gracias
Date: Thu, 25 Oct 2012 12:02:22 -0500
From: huert...@hildebrando.com
To: users@tomcat.apache.org
Subject: Re: Implementing SSL and error invocating https://localhost:8443/
(Tomcat 7.0 on Windows 7)
Hi Christopher:
What I tried to mean is that Internet explorer fails. I have attached image
file with the error generated(Internet Explorer error.gif).
By the way below is what Tomcat generates as log, once I started Tomcat and
after executing https://localhost:8443/ on my Internet Explorer:
25/10/2012 12:00:57 PM org.apache.catalina.core.AprLifecycleListener init
INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un
rendimiento óptimo en entornos de desarrollo no ha sido hallada en
java.library.path:
C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program
Files (x86)\ATI
Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program
Files (x86)\Liquid Technologies\Liquid XML Studio
2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program
Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files
(x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files
(x86)\CVSNT\;.
25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-nio-8443]
25/10/2012 12:00:58 PM org.apache.tomcat.util.net.NioSelectorPool
getSharedSelector
INFO: Using a shared selector for servlet write/read
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 679 ms
25/10/2012 12:00:58 PM org.apache.catalina.core.StandardService startInternal
INFO: Arrancando servicio Catalina
25/10/2012 12:00:58 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\docs de la aplicación web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\examples de la aplicación
web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\host-manager de la
aplicación web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\manager de la aplicación
web
25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Despliegue del directorio C:\Tomcat7.0\webapps\ROOT de la aplicación web
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-nio-8443]
25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 488 ms
Regards.
- Original Message -
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Sent: Thursday, October 25, 2012 11:21:15 AM
Subject: Re: Implementing SSL and error invocating https://localhost:8443/
(Tomcat 7.0 on Windows 7)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriel,
On 10/25/12 10:35 AM, Gabriel Huerta Araujo wrote:
I have followed your procedure which has been stated on
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html to use SSL
or https with JSSE implementation.
Below is configuration for my server.xml Connector
SSLEnabled=true acceptCount=100 clientAuth=false
disableUploadTimeout=true enableLookups=false maxThreads=25
port=8443 keystoreFile=${user.home}/.keystore
keystorePass=my_password
protocol=org.apache.coyote.http11.Http11NioProtocol
scheme=https secure=true sslProtocol=TLS /
where my_password for obvious reasons I do not provide to you.
As a matter of fact, I have generated two trusted certificate
entries with keytool:
keytool -list -keystore .keystore Escriba la contrase±a del almacÚn
de claves:
Tipo de almacen de claves: JKS Proveedor de almacen de claves: SUN
Su almacen de claves contiene 2 entradas
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
Ok Martin: You are right I am using a certificate generated for getacert (http://getacert.com/signacert.html). Even though Tomcat tells me to purchase a certificate from those places you mention, is there any way to get this certificate free? As a matter of fact I am just testing how to use htpps connection with Tomcat (an open source product). Regards. - Original Message - From: Martin Gainty mgai...@hotmail.com To: Tomcat Users List users@tomcat.apache.org Sent: Thursday, October 25, 2012 12:27:31 PM Subject: RE: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7) Gabriel unless you are using a cert from entrust, verisign or thawte you cannot generate a certificate which will be trusted as a CA level cert by all versions for all supported browsers Buena Suerte, Martin __ Porfavor..no altere ni interruptir esta communicacion..Gracias Date: Thu, 25 Oct 2012 12:02:22 -0500 From: huert...@hildebrando.com To: users@tomcat.apache.org Subject: Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7) Hi Christopher: What I tried to mean is that Internet explorer fails. I have attached image file with the error generated(Internet Explorer error.gif). By the way below is what Tomcat generates as log, once I started Tomcat and after executing https://localhost:8443/ on my Internet Explorer: 25/10/2012 12:00:57 PM org.apache.catalina.core.AprLifecycleListener init INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program Files (x86)\Liquid Technologies\Liquid XML Studio 2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\CVSNT\;. 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8080] 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 679 ms 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardService startInternal INFO: Arrancando servicio Catalina 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.32 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\docs de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\examples de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\host-manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\ROOT de la aplicación web 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-bio-8080] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 488 ms Regards. - Original Message - From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Thursday, October 25, 2012 11:21:15 AM Subject: Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 10:35 AM, Gabriel Huerta Araujo wrote: I have followed your procedure which has been stated on http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html to use SSL or https with JSSE implementation. Below is configuration for my server.xml Connector
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 1:02 PM, Gabriel Huerta Araujo wrote: What I tried to mean is that Internet explorer fails. That's not terribly specific. Seg fault? BSOD? Blank screen? I have attached image file with the error generated(Internet Explorer error.gif). This list strips most attachments. Try your best to describe what you see. Consider posting the text of any error messages that you see. By the way below is what Tomcat generates as log, once I started Tomcat and after executing https://localhost:8443/ on my Internet Explorer: 25/10/2012 12:00:57 PM org.apache.catalina.core.AprLifecycleListener init INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program Files (x86)\Liquid Technologies\Liquid XML Studio 2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\CVSNT\;. 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8080] 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 679 ms 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardService startInternal INFO: Arrancando servicio Catalina 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.32 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\docs de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\examples de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\host-manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\ROOT de la aplicación web 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-bio-8080] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 488 ms That all looks good to me. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCJezIACgkQ9CaO5/Lv0PCFnACeO5qVLrZFYBX7ZCi9NwnXxQDJ 94AAnjGVQMkAblNo4UhDLn4IgzBgN/r5 =Nrmj -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 1:43 PM, Gabriel Huerta Araujo wrote: Even though Tomcat tells me to purchase a certificate from those places you mention, is there any way to get this certificate free? Most CAs will issue you a free 30-day certificate to make sure that everything is going to work. If you want a long-term cert, you may as well just buy one because the process is such a pain in the neck: it's going to work. As a matter of fact I am just testing how to use htpps connection with Tomcat (an open source product). If you just need an SSL connection, then there is no reason you couldn't use a self-signed certificate. The only problem is that your web browser is going to complain. Most web browsers have an option to accept the certificate permanently so you don't get security warnings all the time. If you want a free, well-recognized certificate, I can recommend StartSSL: https://www.startssl.com/ After you validate that you control a domain (via email), you can create 1-year basic certificates entirely for free. Here's their comparison chart which includes their rate card and browser/OS support: https://www.startssl.com/?app=40 All major OSs and browsers currently support StartSSL, though, unfortunately, Java does not: you'll have to import their CA and intermediate certificates into a local trust store if you want to use a Java client with these certificates. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCJfIoACgkQ9CaO5/Lv0PD68wCgmZfuZIHr0CU65k8mbZXF0DvX Ds4An0S9oDEfpSaZlq+rlKodk/LLvv04 =M3NB -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7.0.30 CMA, clustering, and SSO
We've setup TC 7.0.32 with Clustering and Tomcat Container Managed Authentication. HTTPSessions and SSOSessions are clustered across the wire. With logging turned way up, I can see the synchronization and I can see the sessions in the Tomcat Manager. When I kill -9 one of the tomcats, I'm automatically swapped to the other leg, and I'm still logged in. So it works, unless I do a catalina.sh shutdown. In that case, the SSO session is expired from the other leg. The HTTPSession is still there, but because the SSO session is expired, I'm forced to login again. This doesn't seem correct. The DeltaSession looks at the notifyCluster parameter before sending a message to expire the HTTPSession, but the ClusterSingleSignOn valve has already sent its message to expire the SSO session by then. So the SSO is missing for the session. When shutting down, the stack trace looks like this (with some relevant parameters replaced in line) isExpireSessionsOnShutdown() == false ClusterSingleSignOn.deregister(SSOID) line: 274 ClusterSingleSignOn(SingleSignOn).sessionEvent(SessionEvent) line: 247 DeltaSession(StandardSession).fireSessionEvent(Session.SESSION_DESTROYED_EVENT, null) line: 1752 DeltaSession(StandardSession).expire(true) line: 844 DeltaSession.expire(true, false) line: 462 DeltaManager.stopInternal() line: 967 DeltaManager(LifecycleBase).stop() line: 232 StandardContext.stopInternal() line: 5474 StandardContext(LifecycleBase).stop() line: 232 When doing a normal session invalidation (for logout), it ends up doing the same thing, which is correct. ClusterSingleSignOn.deregister(SSOID) line: 276 ClusterSingleSignOn(SingleSignOn).sessionEvent(SessionEvent) line: 247 DeltaSession(StandardSession).fireSessionEvent(Session.SESSION_DESTROYED_EVENT, null) line: 1752 DeltaSession(StandardSession).expire(true) line: 844 DeltaSession.expire(true, true) line: 462 DeltaSession.expire(true) line: 444 DeltaSession(StandardSession).expire() line: 742 DeltaSession(StandardSession).invalidate() line: 1253 StandardSessionFacade.invalidate() line: 190 So I can't just change the DeltaSession to ignore that event. I can't just have expire not call the super, or the HTTPSessionListeners would not be called. I think this is a bug, but I don't see even a good fix for it. Ideas? If this does look like a bug, I can log an issue for it. Relevant server.xml here: Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false Valve className=org.apache.catalina.ha.authenticator.ClusterSingleSignOn / Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster channelSendOptions=8 Manager className=org.apache.catalina.ha.session.DeltaManager / Channel className=org.apache.catalina.tribes.group.GroupChannel /Channel Valve className=org.apache.catalina.ha.tcp.ReplicationValve filter= statistics=true / Valve className=org.apache.catalina.ha.session.JvmRouteBinderValve / ClusterListener className=org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener / ClusterListener className=org.apache.catalina.ha.session.ClusterSessionListener / /Cluster /Host The context XML just has a JDBCRealm realm configuration.
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
Chistopher: An spanish message like this: Internet Explorer can not display the web page. Puede diagnosticar lo siguiente: Diagnosticar problemas de conexion When I click Diagnosticar problemas de conexion, it says El equipo o dispositivo remoto no acepta la conexion which translated means The computer or remote device does not accept the connection For more information, it mentions: If this is an HTTPS address (secure), click Tools, Internet Options, Advanced Options, and check the SSL and TLS protocols are enabled in the security section I checked it and these are my internet options for SSL and TLS, as enabled: SSL 3.0 TLS 1.0 Regards - Original Message - From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Thursday, October 25, 2012 12:47:30 PM Subject: Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 1:02 PM, Gabriel Huerta Araujo wrote: What I tried to mean is that Internet explorer fails. That's not terribly specific. Seg fault? BSOD? Blank screen? I have attached image file with the error generated(Internet Explorer error.gif). This list strips most attachments. Try your best to describe what you see. Consider posting the text of any error messages that you see. By the way below is what Tomcat generates as log, once I started Tomcat and after executing https://localhost:8443/ on my Internet Explorer: 25/10/2012 12:00:57 PM org.apache.catalina.core.AprLifecycleListener init INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un rendimiento óptimo en entornos de desarrollo no ha sido hallada en java.library.path: C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program Files (x86)\Liquid Technologies\Liquid XML Studio 2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\CVSNT\;. 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-bio-8080] 25/10/2012 12:00:57 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 679 ms 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardService startInternal INFO: Arrancando servicio Catalina 25/10/2012 12:00:58 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.32 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\docs de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\examples de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\host-manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\manager de la aplicación web 25/10/2012 12:00:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Despliegue del directorio C:\Tomcat7.0\webapps\ROOT de la aplicación web 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-bio-8080] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [http-nio-8443] 25/10/2012 12:00:58 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler [ajp-bio-8009] 25/10/2012 12:00:58 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 488 ms That all looks good to me. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCJezIACgkQ9CaO5/Lv0PCFnACeO5qVLrZFYBX7ZCi9NwnXxQDJ 94AAnjGVQMkAblNo4UhDLn4IgzBgN/r5 =Nrmj -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail:
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 2:08 PM, Gabriel Huerta Araujo wrote: An spanish message like this: Internet Explorer can not display the web page. Puede diagnosticar lo siguiente: Diagnosticar problemas de conexion When I click Diagnosticar problemas de conexion, it says El equipo o dispositivo remoto no acepta la conexion which translated means The computer or remote device does not accept the connection For more information, it mentions: If this is an HTTPS address (secure), click Tools, Internet Options, Advanced Options, and check the SSL and TLS protocols are enabled in the security section I checked it and these are my internet options for SSL and TLS, as enabled: SSL 3.0 TLS 1.0 Do you have access to an OpenSSL client? If this were happening to me, the first thing I would do is this: $ openssl c_client -connect host:8443 This will give you a ton of information about the certificate, ciphers, etc. It's possible that you have configured your connector such that it cannot use SSL3 or TLS1 secure connections. In that case, MSIE would not be able to connect at all. Please post all versions of everything (patch level included, like Tomcat 7.0.32) like Tomcat and JVM, plus your Connector configuration (unless it hasn't changed). You can get a win32 binary for OpenSSL here: http://www.openssl.org/related/binaries.html - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCJl94ACgkQ9CaO5/Lv0PDWKwCaAjTfrFpY6qGMHNlqf8x1rGP8 yj0An0e9nzGeW5nnk9n1parTMhs1vwg8 =a6ba -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
My web.xml's connector section originally was:
Connector SSLEnabled=true acceptCount=100 clientAuth=false
disableUploadTimeout=true enableLookups=false
maxThreads=25
port=8443 keystoreFile=${user.home}/.keystore
keystorePass=my_key_pass
protocol=org.apache.coyote.http11.Http11NioProtocol
scheme=https
secure=true sslProtocol=TLS /
and I had to replace for this (because I wanted to know at least one message
error, this way I could do something else):
Connector port=8443 maxThreads=200
scheme=https secure=true SSLEnabled=true
keystoreFile=${user.home}/.keystore keystorePassmy_key_pass
clientAuth=false sslProtocol=TLS/
Below it is whar Tomcat reports:
25/10/2012 04:23:20 PM org.apache.catalina.core.AprLifecycleListener init
INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un
rendimiento óptimo en entornos de desarrollo no ha sido hallada en
java.library.path:
C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program
Files (x86)\ATI
Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program
Files (x86)\Liquid Technologies\Liquid XML Studio
2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program
Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files
(x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files
(x86)\CVSNT\;.
25/10/2012 04:23:20 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
25/10/2012 04:23:21 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8443]
25/10/2012 04:23:21 PM org.apache.coyote.AbstractProtocol init
GRAVE: Failed to initialize end point associated with ProtocolHandler
[http-bio-8443]
java.io.IOException: La configuración SSL no es válida debido a No available
certificate or key corresponds to the SSL cipher suites which are enabled.
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.checkConfig(JSSESocketFactory.java:822)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:470)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:158)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
at
org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:633)
at org.apache.catalina.startup.Catalina.load(Catalina.java:658)
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:597)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:281)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
Caused by: javax.net.ssl.SSLException: No available certificate or key
corresponds to the SSL cipher suites which are enabled.
at
com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(SSLServerSocketImpl.java:310)
at
com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:255)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.checkConfig(JSSESocketFactory.java:818)
... 20 more
25/10/2012 04:23:21 PM org.apache.catalina.core.StandardService initInternal
GRAVE: No pude inicializar el conector [Connector[HTTP/1.1-8443]]
org.apache.catalina.LifecycleException: Failed to initialize component
[Connector[HTTP/1.1-8443]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at
org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
at
Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)
Sorry I forgot to include what below command generates:
openssl c_client -connect host:8443
Here it is:
With c_client option fails as indicated:
openssl:Error: 'c_client' is an invalid command.
Standard commands
asn1parse ca cipherscrlcrl2pkcs7
dgst dh dhparamdsadsaparam
ec ecparamencengine errstr
gendh gendsa genrsa nseq ocsp
passwd pkcs12 pkcs7 pkcs8 prime
rand reqrsarsautl s_client
s_server s_time sess_idsmime speed
spkac verify versionx509
Message Digest commands (see the `dgst' command for more details)
md2md4md5rmd160 sha
sha1
Cipher commands (see the `enc' command for more details)
aes-128-cbcaes-128-ecbaes-192-cbcaes-192-ecbaes-256-cbc
aes-256-ecbbase64 bf bf-cbc bf-cfb
bf-ecb bf-ofb cast cast-cbc cast5-cbc
cast5-cfb cast5-ecb cast5-ofb desdes-cbc
des-cfbdes-ecbdes-ededes-ede-cbcdes-ede-cfb
des-ede-ofbdes-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb
des-ofbdes3 desx rc2rc2-40-cbc
rc2-64-cbc rc2-cbcrc2-cfbrc2-ecbrc2-ofb
rc4rc4-40
I had to run it as:
openssl s_client -connect host:8443
And this is what generates:
gethostbyname failure
connect:errno=1
Regards.
- Original Message -
From: Gabriel Huerta Araujo huert...@hildebrando.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Thursday, October 25, 2012 4:32:47 PM
Subject: Re: Implementing SSL and error invocating https://localhost:8443/
(Tomcat 7.0 on Windows 7)
My web.xml's connector section originally was:
Connector SSLEnabled=true acceptCount=100 clientAuth=false
disableUploadTimeout=true enableLookups=false
maxThreads=25
port=8443 keystoreFile=${user.home}/.keystore
keystorePass=my_key_pass
protocol=org.apache.coyote.http11.Http11NioProtocol
scheme=https
secure=true sslProtocol=TLS /
and I had to replace for this (because I wanted to know at least one message
error, this way I could do something else):
Connector port=8443 maxThreads=200
scheme=https secure=true SSLEnabled=true
keystoreFile=${user.home}/.keystore keystorePassmy_key_pass
clientAuth=false sslProtocol=TLS/
Below it is whar Tomcat reports:
25/10/2012 04:23:20 PM org.apache.catalina.core.AprLifecycleListener init
INFO: La biblioteca nativa de Apache Tomcat basada en ARP que permite un
rendimiento óptimo en entornos de desarrollo no ha sido hallada en
java.library.path:
C:\jdk1.6.35\bin;C:\windows\Sun\Java\bin;C:\windows\system32;C:\windows;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\mingw\mingw64\bin;C:\Program
Files (x86)\ATI
Technologies\ATI.ACE\Core-Static;C:\jdk1.6.35\bin;C:\Spring\apache-maven-3.0.4\bin;C:\Program
Files (x86)\Liquid Technologies\Liquid XML Studio
2011\XmlDataBinder9\Redist9\cpp\win32\bin;C:\cygwin\bin\;C:\apache-ant-1.8.2/bin;C:\Program
Files (x86)\Microchip\MPLAB C32 Suite\bin;C:\Program Files
(x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files
(x86)\CVSNT\;.
25/10/2012 04:23:20 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
25/10/2012 04:23:21 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8443]
25/10/2012 04:23:21 PM org.apache.coyote.AbstractProtocol init
GRAVE: Failed to initialize end point associated with ProtocolHandler
[http-bio-8443]
java.io.IOException: La configuración SSL no es válida debido a No available
certificate or key corresponds to the SSL cipher suites which are enabled.
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.checkConfig(JSSESocketFactory.java:822)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:470)
at
org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:158)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:393)
at
org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:610)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:429)
at
org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at
org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at
tomcat 7 PermGen
Hello: After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help. Is there any way to reduce the chance of PermGen errors? such as how deployment should be done, etc? Thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 PermGen
After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help. All those JVM settings for perm memory - could you share which settings you have tried, and what values you set? Ideally tell us exactly how you made the changes. Also knowing a little about your system might help. You know the basics. Like which tomcat v7 - there are 32 of them. Which version of java? Which os? Little things like that help Thanks Chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 PermGen
Can you post the exact error message you are seeing and what your JVM settings are when you get that error? Warm Regards, Jordan Michaels On 10/25/2012 04:24 PM, Ted Smith wrote: Hello: After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help. Is there any way to reduce the chance of PermGen errors? such as how deployment should be done, etc? Thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 PermGen
I am running tomcat 7.0.29, JDK 6.0.30 -XX:MaxPermSize=256m is one of the settings I tried but no help and others settings that could be found googling. it occurred in 6 as well, but suddently so often after upgrading to 7 I am curious how many on this list are having the similar issues, i.e., live deployment of new war files. or most users have to restart tomcat after new war copying. or just me having this issue. On 10/25/2012 7:36 PM, chris derham wrote: After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help. All those JVM settings for perm memory - could you share which settings you have tried, and what values you set? Ideally tell us exactly how you made the changes. Also knowing a little about your system might help. You know the basics. Like which tomcat v7 - there are 32 of them. Which version of java? Which os? Little things like that help Thanks Chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: tomcat 7 PermGen
Exception in thread http-bio-7070-exec-31 java.lang.OutOfMemoryError: PermGen space at java.lang.Throwable.getStackTraceElement(Native Method) at java.lang.Throwable.getOurStackTrace(Throwable.java:591) at java.lang.Throwable.printStackTrace(Throwable.java:510) at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:72) at org.apache.juli.FileHandler.publish(FileHandler.java:200) at java.util.logging.Logger.log(Logger.java:478) at java.util.logging.Logger.doLog(Logger.java:500) at java.util.logging.Logger.logp(Logger.java:700) at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:185) at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:151) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:263) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:123) On 10/25/2012 7:49 PM, Jordan Michaels wrote: Can you post the exact error message you are seeing and what your JVM settings are when you get that error? Warm Regards, Jordan Michaels On 10/25/2012 04:24 PM, Ted Smith wrote: Hello: After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help. Is there any way to reduce the chance of PermGen errors? such as how deployment should be done, etc? Thanks in advance. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
