Re: [EXTERNAL] Re: Tomcat Connection Rest Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Gary, On 4/5/20 12:08, Hua, Gary - Saint Louis, MO - Contractor wrote: > You are right this is INFO message and not an ERROR. > > We didn't find anything in the log that suggesting there is a > successful connection.What those successful connection message > suppose to be? I was just asking. How about this part of my reply? On 3/31/20 13:28, Christopher Schultz wrote:> Gary, > > Where does the server hang? On logins? Do you have a thread dump of > a "hung" server? - -chris > -Original Message- From: Christopher Schultz > [mailto:ch...@christopherschultz.net] Sent: Tuesday, March 31, 2020 > 12:28 PM To: users@tomcat.apache.org Subject: [EXTERNAL] Re: Tomcat > Connection Rest Error > > Gary, > > On 3/31/20 13:20, Hua, Gary - Saint Louis, MO - Contractor wrote: >> After we deploy our application to production in Tomcat server >> 9.0.33, we got following error when multiple users login for some >> time and the server hangs. > > Where does the server hang? On logins? Do you have a thread dump of > a "hung" server? > >> When user click the "Login" button on the login form, it has a >> security realm that connect to the LDAP as in the server.xml: > >> > connectionURL="ldaps://" /> > > >> 30-Mar-2020 12:47:29.218 INFO [https-jsse-nio-9443-exec-30] >> org.apache.catalina.realm.JNDIRealm.authenticate Exception >> performing authentication. Retrying... > >> javax.naming.CommunicationException: Connection reset [Root >> exception is java.net.SocketException: Connection reset]; >> remaining name "XXX" > >> at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) [snip] > >> Caused by: java.net.SocketException: Connection reset > >> at java.net.SocketInputStream.read(SocketInputStream.java:210) >> [snip] > > This often happens because a firewall terminates a long-lived > connection. When encountering an error like this, Tomcat should > retry its connection and work-around any such termination. You can > see that this is an INFO message and not an ERROR. Does Tomcat > eventually log anything suggesting that there is a successful > connection? > > -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 > -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl6LeqcACgkQHPApP6U8 pFjhOhAAlWEmo6xSp1wWnbXIaygoAEqLenKz/m+izI942TfwZAYEUEh3khFmlh8H vptydoLDKsqrW7EemOyW6dhA6aWZT3TCQXRCGD0MaR6XynemOEoQ3qg3U3N2kSgR 1eQius6e5iJ4/RQEYnBytcIxkGazCfUoctvw89+HFFEd0tvOotcf9vMLsC8Wy+SA x7v8vkVG44UAH5KFFaEj0wcxLQxZf2ko0yqqI0Z3cpmlLUaVjkiGJ1iUX4yrpVgW SnierAggxUAOGJsNPFocE47NHSB724OQ6Uwe7W8Cgxn7LP5QG/9afATM1cQnaFNB e1ne+w4BJwiyBPFvXhv4KmqQSFFS9675t/eW/zU8JMBbiVpmN4P9m47xT3OIsxWz jqXzjGaeRF2RiOJFvfZq/gpW2wdzJVIHHYaxmxsubuhvzaI012rca333YBgKLD1Q qjIVTycrmgKpi0UNJB8bQyK+k4iZkb2MHREk90F5q7gXDEOw3iYOgzZ45KPstPRF GHcy9Zh9a284yBp2dejRiPDaKQoRaKgOq07tkWNuKh2oQ47oSP/le8iWGJ6RTqIw ylqOzvdII9g+e2fNddrCuL9GPXuw79QMBuYqHkDMhQLrPxxOwc2tAVts3M1G3tbb o7rSa1jR9kv8sb5SCuFScd4tXlf2cNBHHCp/wnxL3PvQMv4t5Y0= =q1eV -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: [EXTERNAL] Re: Tomcat Connection Rest Error
Chris: You are right this is INFO message and not an ERROR. We didn't find anything in the log that suggesting there is a successful connection.What those successful connection message suppose to be? Thanks Gary -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, March 31, 2020 12:28 PM To: users@tomcat.apache.org Subject: [EXTERNAL] Re: Tomcat Connection Rest Error -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Gary, On 3/31/20 13:20, Hua, Gary - Saint Louis, MO - Contractor wrote: > After we deploy our application to production in Tomcat server 9.0.33, > we got following error when multiple users login for some time and the > server hangs. Where does the server hang? On logins? Do you have a thread dump of a "hung" server? > When user click the "Login" button on the login form, it has a > security realm that connect to the LDAP as in the server.xml: > > connectionURL="ldaps://" /> > > > 30-Mar-2020 12:47:29.218 INFO [https-jsse-nio-9443-exec-30] > org.apache.catalina.realm.JNDIRealm.authenticate Exception performing > authentication. Retrying... > > javax.naming.CommunicationException: Connection reset [Root exception > is java.net.SocketException: Connection reset]; remaining name "XXX" > > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) [snip] > > Caused by: java.net.SocketException: Connection reset > > at java.net.SocketInputStream.read(SocketInputStream.java:210) > [snip] This often happens because a firewall terminates a long-lived connection. When encountering an error like this, Tomcat should retry its connection and work-around any such termination. You can see that this is an INFO message and not an ERROR. Does Tomcat eventually log anything suggesting that there is a successful connection? - -chris -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl6DfaUACgkQHPApP6U8 pFgWcg/7BufYygaJeerkpwGuCXafQ9f/xTFTPevvgfL2PSD9/iZiYm7vOTWXqwrP 7xn8XRUEmycNROq31pfFyfDP8IJqlrRwampEoRRzVbQDXwBdeNDHlFILL7+BVrvP 0q9Wgb9WdWlPuVv/ZYMM5GLRVxhoCX68p0tRlmxpOM/U4Uiaa9eDR809GCliNWa9 +QThei2UewGfOsIQovpSU76qUuSnmcIf2iy6UJ2DkKH7mLmbyX58WW3JAX4Y1kPY CV1jUVQ58KRcqD3bgHrEarMkAWI6AhgrXFf6MaqC8z0NPykPmeiwfAl4JY3kkUsU LmxzJqfQoztv+NJdcsBwjV+hA81zeeAP/6NfV/q1kTocHYYea5wKSJXRFFbGUeh/ STAu2pw5yA43tZvW9Nthn2SJS1lC7XMs/izi95J+srxjxedMg3i/NfkBiaf78i42 GXnjxNIi8GBPTQZ4hEL83p8Jn1r0jd/13zCUSAcpiV8svTBlWhqPelVXti4fuL41 ssqpAmhe4A0lUDnnpiGZHld57oA5K3FJ46c6PRhjR5hu9/nQig3d3cZuqFlimnwK 79PeLquSewFTNDOVbJhhYsQzPgMOFNejo50E88AVQWIWMDqAtEzFZ87LFlLjq3cI Hek1jV4PMpDjnaJNERJdzRMSAhXdyu5JIjkia3+s/d8B8Q+htR4= =c9iM -END PGP SIGNATURE- - 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 Connection Rest Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Gary, On 3/31/20 13:20, Hua, Gary - Saint Louis, MO - Contractor wrote: > After we deploy our application to production in Tomcat server > 9.0.33, we got following error when multiple users login for some > time and the server hangs. Where does the server hang? On logins? Do you have a thread dump of a "hung" server? > When user click the "Login" button on the login form, it has a > security realm that connect to the LDAP as in the server.xml: > > connectionURL="ldaps://" /> > > > 30-Mar-2020 12:47:29.218 INFO [https-jsse-nio-9443-exec-30] > org.apache.catalina.realm.JNDIRealm.authenticate Exception > performing authentication. Retrying... > > javax.naming.CommunicationException: Connection reset [Root > exception is java.net.SocketException: Connection reset]; remaining > name "XXX" > > at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) [snip] > > Caused by: java.net.SocketException: Connection reset > > at java.net.SocketInputStream.read(SocketInputStream.java:210) > [snip] This often happens because a firewall terminates a long-lived connection. When encountering an error like this, Tomcat should retry its connection and work-around any such termination. You can see that this is an INFO message and not an ERROR. Does Tomcat eventually log anything suggesting that there is a successful connection? - -chris -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl6DfaUACgkQHPApP6U8 pFgWcg/7BufYygaJeerkpwGuCXafQ9f/xTFTPevvgfL2PSD9/iZiYm7vOTWXqwrP 7xn8XRUEmycNROq31pfFyfDP8IJqlrRwampEoRRzVbQDXwBdeNDHlFILL7+BVrvP 0q9Wgb9WdWlPuVv/ZYMM5GLRVxhoCX68p0tRlmxpOM/U4Uiaa9eDR809GCliNWa9 +QThei2UewGfOsIQovpSU76qUuSnmcIf2iy6UJ2DkKH7mLmbyX58WW3JAX4Y1kPY CV1jUVQ58KRcqD3bgHrEarMkAWI6AhgrXFf6MaqC8z0NPykPmeiwfAl4JY3kkUsU LmxzJqfQoztv+NJdcsBwjV+hA81zeeAP/6NfV/q1kTocHYYea5wKSJXRFFbGUeh/ STAu2pw5yA43tZvW9Nthn2SJS1lC7XMs/izi95J+srxjxedMg3i/NfkBiaf78i42 GXnjxNIi8GBPTQZ4hEL83p8Jn1r0jd/13zCUSAcpiV8svTBlWhqPelVXti4fuL41 ssqpAmhe4A0lUDnnpiGZHld57oA5K3FJ46c6PRhjR5hu9/nQig3d3cZuqFlimnwK 79PeLquSewFTNDOVbJhhYsQzPgMOFNejo50E88AVQWIWMDqAtEzFZ87LFlLjq3cI Hek1jV4PMpDjnaJNERJdzRMSAhXdyu5JIjkia3+s/d8B8Q+htR4= =c9iM -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat Connection Rest Error
Experts: After we deploy our application to production in Tomcat server 9.0.33, we got following error when multiple users login for some time and the server hangs. When user click the "Login" button on the login form, it has a security realm that connect to the LDAP as in the server.xml: _realm; cat LDAP_realm.xml 30-Mar-2020 12:47:29.218 INFO [https-jsse-nio-9443-exec-30] org.apache.catalina.realm.JNDIRealm.authenticate Exception performing authentication. Retrying... javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name "XXX" at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2002) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1844) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1769) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:392) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:358) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:341) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267) at org.apache.catalina.realm.JNDIRealm.getUserBySearch(JNDIRealm.java:1685) at org.apache.catalina.realm.JNDIRealm.getUser(JNDIRealm.java:1521) at org.apache.catalina.realm.JNDIRealm.getUser(JNDIRealm.java:1469) at org.apache.catalina.realm.JNDIRealm.authenticate(JNDIRealm.java:1414) at org.apache.catalina.realm.JNDIRealm.authenticate(JNDIRealm.java:1296) at org.apache.catalina.realm.CombinedRealm.authenticate(CombinedRealm.java:190) at org.apache.catalina.realm.LockOutRealm.authenticate(LockOutRealm.java:154) at org.apache.catalina.authenticator.FormAuthenticator.doAuthenticate(FormAuthenticator.java:243) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:631) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:688) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1594) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:933) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at
