Re: Error while starting Tomcat 8.5.14
Hi All, We could finally mange through this. Somehow, the SSLEngine attribute was set as "off" in the AprLifecycleListener which did not allow OpenSSL implementation to work. This is resolved now. Thanks Neha On Mon, Jun 5, 2017 at 1:27 PM, Neha Munjal <neha.munj...@gmail.com> wrote: > Hi, > > We tried the following configuration, but it still fails with the same > error: > > address= >protocol="org.apache.coyote.http11.Http11NioProtocol" >SSLEnabled="true" >maxThreads="150" keyAlias="interact7-priv" >scheme="https" >secure="true" >clientAuth="false" >sslProtocol="TLS"> > > certificateKeystoreFile= > certificateKeystorePassword=x /> > > > > Thanks > Neha > > On Mon, Jun 5, 2017 at 11:53 AM, Hassan Khan <hassankhan...@gmail.com> > wrote: > >> Hi, >> >> we had a different problem with Nio : >> > > Non-blocking connector >> maxThreads="200" SSLEnabled="true" compression="on" >> minSpareThreads="25" maxSpareThreads="75" >> enableLookups="false"connectionTimeout="-1" >> scheme="https" secure="true"> >> >> >> > certificateKeystorePassword="XXX" >> certificateKeyAlias="localhost" >> type="RSA" /> >> >> >> >> so we changed to APR as below and everything worked great : >> > port="443" clientAuth="false" sslProtocol="TLS" >> SSLEnabled="true" maxThreads="150" scheme="https" secure="true" >> SSLCertificateFile="ABC.crt" >> SSLCertificateKeyFile="TRE.key" >> SSLEngine="on" SSLVerifyDepth="2" >>/> >> >> But your may be different issue... >> >> Thanks >> Hassan >> >> On Mon, Jun 5, 2017 at 1:30 PM, Neha Munjal <neha.munj...@gmail.com> >> wrote: >> >> > Hi Chris, >> > >> > Please find below our Connector information: >> > >> > > > >> >address=xx >> > >> >protocol="org.apache.coyote.http11.Http11NioProtocol" >> > >> >SSLEnabled="true" >> > >> >maxThreads="150" >> > >> >keyAlias=x >> > >> >keystoreFile=xxxxxx keystorePass=x >> > >> >scheme="https" >> > >> >secure="true" >> > >> >clientAuth="false" >> > >> >sslProtocol="TLS" /> >> > >> > >> > Also found this link that talks about different SSL implementations >> that we >> > can configure: >> > >> > >> > https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html >> > >> > >> > Our installation uses APR and we have openssl102 installed. I think the >> > connector configuration requires changes. >> > >> > >> > Thanks >> > >> > Neha >> > >> > >> > >> > On Mon, Jun 5, 2017 at 7:58 AM, Christopher Schultz < >> > ch...@christopherschultz.net> wrote: >> > >> > > -BEGIN PGP SIGNED MESSAGE- >> > > Hash: SHA256 >> > > >> > > >> > > >> > > Neha, >> > > >> > > On 6/2/17 5:36 PM, Neha Munjal wrote: >> > > > We have been trying to start Apache Tomcat 8.5.14 (JDK version >> > > 8.0_121-b13) >> > > > and land into the following error: >> > > > >> > > > # >> > > > >> > > > # A fatal error has been detected by the Java Runtime Environment: >> > > > # # SIGSEGV (0xb) at pc=0x7fafaa9ad123, pid=590, >> > > tid=0x7fb095cdc700 >> > > > # # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) >> > > > (build 1.8.0_121-b13) >> > > > >> > > > # Ja
Re: Error while starting Tomcat 8.5.14
Hi, We tried the following configuration, but it still fails with the same error: Thanks Neha On Mon, Jun 5, 2017 at 11:53 AM, Hassan Khan <hassankhan...@gmail.com> wrote: > Hi, > > we had a different problem with Nio : > > Non-blocking connector > maxThreads="200" SSLEnabled="true" compression="on" > minSpareThreads="25" maxSpareThreads="75" > enableLookups="false"connectionTimeout="-1" > scheme="https" secure="true"> > > > certificateKeystorePassword="XXX" > certificateKeyAlias="localhost" > type="RSA" /> > > > > so we changed to APR as below and everything worked great : >port="443" clientAuth="false" sslProtocol="TLS" > SSLEnabled="true" maxThreads="150" scheme="https" secure="true" > SSLCertificateFile="ABC.crt" > SSLCertificateKeyFile="TRE.key" > SSLEngine="on" SSLVerifyDepth="2" >/> > > But your may be different issue... > > Thanks > Hassan > > On Mon, Jun 5, 2017 at 1:30 PM, Neha Munjal <neha.munj...@gmail.com> > wrote: > > > Hi Chris, > > > > Please find below our Connector information: > > > > > > >address=xx > > > >protocol="org.apache.coyote.http11.Http11NioProtocol" > > > >SSLEnabled="true" > > > >maxThreads="150" > > > >keyAlias=x > > > >keystoreFile=xx keystorePass=x > > > >scheme="https" > > > >secure="true" > > > >clientAuth="false" > > > >sslProtocol="TLS" /> > > > > > > Also found this link that talks about different SSL implementations that > we > > can configure: > > > > > > https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html > > > > > > Our installation uses APR and we have openssl102 installed. I think the > > connector configuration requires changes. > > > > > > Thanks > > > > Neha > > > > > > > > On Mon, Jun 5, 2017 at 7:58 AM, Christopher Schultz < > > ch...@christopherschultz.net> wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > > > > > > > Neha, > > > > > > On 6/2/17 5:36 PM, Neha Munjal wrote: > > > > We have been trying to start Apache Tomcat 8.5.14 (JDK version > > > 8.0_121-b13) > > > > and land into the following error: > > > > > > > > # > > > > > > > > # A fatal error has been detected by the Java Runtime Environment: > > > > # # SIGSEGV (0xb) at pc=0x7fafaa9ad123, pid=590, > > > tid=0x7fb095cdc700 > > > > # # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) > > > > (build 1.8.0_121-b13) > > > > > > > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed > > > > mode linux-amd64 compressed oops) > > > > > > > > # Problematic frame: > > > > > > > > # C [libapr-1.so.0+0x25123] apr_threadkey_private_set+0x3 > > > > > > > > > Hmm... I've not seen this one before. > > > > > > Can you please post your configuration (with any secrets > > > removed)? > > > > > > - -chris > > > > > > -BEGIN PGP SIGNATURE- > > > Comment: GPGTools - http://gpgtools.org > > > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > > > > > iQIcBAEBCAAGBQJZNXF8AAoJEBzwKT+lPKRYZjYP/jgD5WziGLxS6FzHBX9bkkKZ > > > NeNVsi0PZZDRBmdKdcudeHYHsW4gqNNfYHIakcWYhS5f7fSJx6cgJrC550OSL5mU > > > Wzeqe7gTBmju2L9YcM9TJwITS7X+FvpaGv+y4tCcjGyHNwB1Se0N1bHasRZYo8DR > > > lg7rAAtPKfzBaeMlf6JcHGK2+K/3sXzGL0oAAyWG3j5jzE1IYl5hiV/oQtNKwZ7K > > > l6YzL0/tx9jpiuRFRhHPkPJh2fYUP6ZQ5I8J12fjjeKWgiCepJvwuLKgQ9uDwYrB > > > Bz0mrc8hQSvMTbIx5bVrRVmMmJiofTcL81H3QE9BN5/yFk+CrCwvmt8E/w25/PoP > > > tfZ4fbcDJ2U4tA2BDbXL/oOpl3TtcDh8kzZadWa6hZBfEjgsoyXJD9MJ4QHtrjql > > > FHLx0SYCasAwpNNGM2TZ3rvXEWEoWh+thRkxN1oe6ysmVqKgT7y7JO2fjPRXNQ+x > > > PP6DouWUAItXTxa4Rzom7Pu9o8YkxJ10GU6U7hAKI8JzVpSiifOttMy/QWV02Rpx > > > th4+SOhzkjgsecTFzK9vsdM1M0MTHVsyNyrj1iRilt0eHonYiTmq9NfmKvskIgqi > > > QaOdO5Ykd2YCHroF8qtVmr559Z84XOyaqOzjeyz8pgCaRtamHNGXdm6UGdfv7QjZ > > > /AEW3TdCWPHVOr3xmdgq > > > =4rJc > > > -END PGP SIGNATURE- > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > > > > > > > -- > Hassan Khan >
Re: Error while starting Tomcat 8.5.14
Hi Chris, Please find below our Connector information: Also found this link that talks about different SSL implementations that we can configure: https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html Our installation uses APR and we have openssl102 installed. I think the connector configuration requires changes. Thanks Neha On Mon, Jun 5, 2017 at 7:58 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > > Neha, > > On 6/2/17 5:36 PM, Neha Munjal wrote: > > We have been trying to start Apache Tomcat 8.5.14 (JDK version > 8.0_121-b13) > > and land into the following error: > > > > # > > > > # A fatal error has been detected by the Java Runtime Environment: > > # # SIGSEGV (0xb) at pc=0x7fafaa9ad123, pid=590, > tid=0x7fb095cdc700 > > # # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) > > (build 1.8.0_121-b13) > > > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed > > mode linux-amd64 compressed oops) > > > > # Problematic frame: > > > > # C [libapr-1.so.0+0x25123] apr_threadkey_private_set+0x3 > > > Hmm... I've not seen this one before. > > Can you please post your configuration (with any secrets > removed)? > > - -chris > > -BEGIN PGP SIGNATURE- > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJZNXF8AAoJEBzwKT+lPKRYZjYP/jgD5WziGLxS6FzHBX9bkkKZ > NeNVsi0PZZDRBmdKdcudeHYHsW4gqNNfYHIakcWYhS5f7fSJx6cgJrC550OSL5mU > Wzeqe7gTBmju2L9YcM9TJwITS7X+FvpaGv+y4tCcjGyHNwB1Se0N1bHasRZYo8DR > lg7rAAtPKfzBaeMlf6JcHGK2+K/3sXzGL0oAAyWG3j5jzE1IYl5hiV/oQtNKwZ7K > l6YzL0/tx9jpiuRFRhHPkPJh2fYUP6ZQ5I8J12fjjeKWgiCepJvwuLKgQ9uDwYrB > Bz0mrc8hQSvMTbIx5bVrRVmMmJiofTcL81H3QE9BN5/yFk+CrCwvmt8E/w25/PoP > tfZ4fbcDJ2U4tA2BDbXL/oOpl3TtcDh8kzZadWa6hZBfEjgsoyXJD9MJ4QHtrjql > FHLx0SYCasAwpNNGM2TZ3rvXEWEoWh+thRkxN1oe6ysmVqKgT7y7JO2fjPRXNQ+x > PP6DouWUAItXTxa4Rzom7Pu9o8YkxJ10GU6U7hAKI8JzVpSiifOttMy/QWV02Rpx > th4+SOhzkjgsecTFzK9vsdM1M0MTHVsyNyrj1iRilt0eHonYiTmq9NfmKvskIgqi > QaOdO5Ykd2YCHroF8qtVmr559Z84XOyaqOzjeyz8pgCaRtamHNGXdm6UGdfv7QjZ > /AEW3TdCWPHVOr3xmdgq > =4rJc > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Error while starting Tomcat 8.5.14
Hi, We have been trying to start Apache Tomcat 8.5.14 (JDK version 8.0_121-b13) and land into the following error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fafaa9ad123, pid=590, tid=0x7fb095cdc700 # # JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libapr-1.so.0+0x25123] apr_threadkey_private_set+0x3 # # Core dump written. Default location: /opt/tomcat-8.5.14/bin/core or core.590 # # An error report file with more information is saved as: # /tmp/hs_err_pid590.log The log dump indicates the following problem: Also, saw the following internal exceptions in the log dump: Internal exceptions (10 events): Event: 0.372 Thread 0x7f4d5400b800 Exception (0x0003bfa226c0) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/runtime/sharedRuntime.cpp, line 605] Event: 0.382 Thread 0x7f4d5400b800 Exception (0x0003bfa48cb0) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/runtime/sharedRuntime.cpp, line 605] Event: 0.392 Thread 0x7f4d5400b800 Exception (0x0003bfa58800) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/runtime/sharedRuntime.cpp, line 605] Event: 0.548 Thread 0x7f4d5400b800 Exception (0x0003bec64a18) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210] Event: 0.556 Thread 0x7f4d5400b800 Exception (0x0003bec89a98) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210] Event: 0.633 Thread 0x7f4d5400b800 Exception (0x0003beddd558) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/prims/methodHandles.cpp, line 1146] Event: 0.635 Thread 0x7f4d5400b800 Exception (0x0003bedeb068) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/prims/methodHandles.cpp, line 1146] Event: 0.747 Thread 0x7f4d5400b800 Exception (0x0003be2cae58) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/classfile/systemDictionary.cpp Event: 1.256 Thread 0x7f4d5400b800 Implicit null exception at 0x7f4d45611af5 to 0x7f4d45611f8d Event: 1.279 Thread 0x7f4d5400b800 Exception (0x0003bc6a0b68) thrown at [/HUDSON3/workspace/8-2-build-linux-amd64/jdk8u121/8372/hotspot/src/share/vm/classfile/systemDictionary.cpp, line 210] Can somebody provide hints towards the issue? Please note that APR based Apache Tomcat Native library 1.2.12 using APR version 1.4.5 is used. Thanks Neha
RequestDispatcher.forward between 2 virtual hosts defined in the same Tomcat container
Hi, I would like to know if we can do servlet forwarding between 2 different webapps deployed on 2 different virtual hosts configured in the same Tomcat container. So, I have configured 2 different virtual hosts in my Tomcat server.xml as follows: Host name=firstservlet appBase=firstservletapps/ Host name=secondservlet appBase=secondservletapps/ and put the root.xml file for default webapps to: $CATALINA_HOME/conf/Catalina/virtualhost directory. servlet2 is deployed as a different war in the 2nd virtual host. I notice that when I try to fetch the context of servlet2 from Servlet1 to do a forward from Servlet1 to Servlet2, the loaded context is null and so there is forwars. Please note that crossContext attribute is set to true in the context.xml for the 1st war. Also, noticed that in case I do not define any explicit virtual hosts and deploy both the wars in the default host i.e localhost, the forwarding works fine. Can somebody please let me know if servlet.forward works with virtual hosts. Any suggestions would be highly appreciated. Thanks Neha
Issue while deploying a war file using Tomcat 7.0.52
Hi All, I am using Tomcat7.0.52 on Windows 7 64 Bit. The issue I am facing is that when I try to deploy a war file, I receive the following exception: *Caused by: java.lang.ClassCastException: org.hornetq.jms.client.HornetQJMSConnectionFactory cannot be cast to javax.jms.ConnectionFactory* The set up is as follows: We have an implementation of HornetQServer that basically starts up some JMS threads for application specific tasks. The client side implementation has a class org.hornetq.jms.client.HornetQJMSConnectionFactory that implements the interface javax.jms.ConnectionFactory. (jms-api.jar). As part of our customized ant target that we run to start the Tomcat, we have set the classpath that points to the location where we have jms-api.jar, which implies that these would be taken care of by the Bootstrap Loader. Additionally, we have added a location to common.loader setting in catalina.properties that contains some HornetQspecific jars that should be available to all deployables of our application. These would be taken care of by Common classloader. At the same time, we have jms-api.jar file in the /WEB-INF/lib directory of our deployable as well. Now when we deploy this war file, we get the above mentioned exception. I tried the same set up on Tomcat7.0.50 as well and there, no such exception is encountered. I would like to know the probable cause of this issue and why this is working fine on Tomcat7.0.50 and not 7.0.52. Any feedback wold be greatly appreciated. Thanks
Re: Issue while deploying a war file using Tomcat 7.0.52
Hi Konstanti, In my opinion, The Bootstrap classloader should be effective and since the jar is present there, it should consider it and not throw this exception. Thanks Neha On Thu, Feb 27, 2014 at 5:26 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2014-02-27 15:36 GMT+04:00 Neha Munjal neha.munj...@gmail.com: Hi All, I am using Tomcat7.0.52 on Windows 7 64 Bit. The issue I am facing is that when I try to deploy a war file, I receive the following exception: *Caused by: java.lang.ClassCastException: org.hornetq.jms.client.HornetQJMSConnectionFactory cannot be cast to javax.jms.ConnectionFactory* The set up is as follows: We have an implementation of HornetQServer that basically starts up some JMS threads for application specific tasks. The client side implementation has a class org.hornetq.jms.client.HornetQJMSConnectionFactory that implements the interface javax.jms.ConnectionFactory. (jms-api.jar). As part of our customized ant target that we run to start the Tomcat, we have set the classpath that points to the location where we have jms-api.jar, which implies that these would be taken care of by the Bootstrap Loader. Additionally, we have added a location to common.loader setting in catalina.properties that contains some HornetQspecific jars that should be available to all deployables of our application. These would be taken care of by Common classloader. At the same time, we have jms-api.jar file in the /WEB-INF/lib directory of our deployable as well. Now when we deploy this war file, we get the above mentioned exception. I tried the same set up on Tomcat7.0.50 as well and there, no such exception is encountered. I would like to know the probable cause of this issue and why this is working fine on Tomcat7.0.50 and not 7.0.52. Any feedback wold be greatly appreciated. So, of the two copies of jms-api.jar what are your expectations on which one will be effective? Also, https://issues.apache.org/bugzilla/show_bug.cgi?id=56180#c2 Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
