Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
On 31/01/2013 03:14, Howard W. Smith, Jr. wrote: 5. from what I can see, there is an atmosphere thread that is (possibly) causing this issue; please see below and let me know if I should open a tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I want to upload and/or share/provide the heap dump files; i'm assuming that I should 'not' attach the files via email, and it might not be readable to copy/paste the content here; please advise. That looks like a problem with the APR/native connector. Was there any more text (like a full stack trace) in the error message you quote below? I can't see any relevant changes between 7.0.34 and 7.0.35 that might have triggered this. Mark # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x000180005310, pid=2396, tid=3724 # # JRE version: 7.0_11-b21 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0 # # Core dump written. Default location: D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x14f08000): JavaThread Atmosphere-AsyncWrite-60 daemon [_thread_in_native, id=3724, stack(0x1f13,0x1f23)] - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
On Thu, Jan 31, 2013 at 6:10 AM, Mark Thomas ma...@apache.org wrote: On 31/01/2013 03:14, Howard W. Smith, Jr. wrote: 5. from what I can see, there is an atmosphere thread that is (possibly) causing this issue; please see below and let me know if I should open a tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I want to upload and/or share/provide the heap dump files; i'm assuming that I should 'not' attach the files via email, and it might not be readable to copy/paste the content here; please advise. That looks like a problem with the APR/native connector. Was there any more text (like a full stack trace) in the error message you quote below? I can't see any relevant changes between 7.0.34 and 7.0.35 that might have triggered this. Mark # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x000180005310, pid=2396, tid=3724 # # JRE version: 7.0_11-b21 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0 # # Core dump written. Default location: D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x14f08000): JavaThread Atmosphere-AsyncWrite-60 daemon [_thread_in_native, id=3724, stack(0x1f13,0x1f23)] Please see https://gist.github.com/4680412
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2013/1/30 Caldarale, Charles R chuck.caldar...@unisys.com: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs Sending this to tomee/openejb and tomcat user mailing lists. Cross-posting is really frowned upon. Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event SEVERE: Servlet.service() for servlet [Push Servlet] in context with path [/mcmsweb] threw exception java.lang.NumberFormatException: For input string: (TomEE)/7 at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.valueOf(Unknown Source) at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141) Sure looks like an Atmosphere problem from here... +1. https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129 That bz51881 method... an example of what you should never do... It tries to parse a version string to workaround a bug that was properly fixed more than a year ago, and fails horribly. It is a normal practice to modify the server info value, e.g. [1]. It is useless to rely on it. It is no wonder that the one used by TomEE is different from Tomcat. [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves UPDATE: 1. Atmosphere issue 869[1] was opened, fixed, and closed on atmosphere github 2. This issue has been occurring on my Windows Server 2008 64bit 32GB RAM production server ever since I started using a new(er) version of TomEE 1.5.2-SNAPSHOT (which now has Tomcat 7.0.35 dependency) 3. So, I reverted to an earlier (2013-01-14) version of TomEE 1.5.2-SNAPSHOT (which has tomcat 7.0.34 dependency), in the meanwhile, to avoid this issue on the production server. 4. Within the last 30 minutes, I recognized that I have heap dump files for the times that TomEE 1.5.2-SNAPSHOT (with Tomcat 7.0.35 dependency) stopped running as windows service. 5. from what I can see, there is an atmosphere thread that is (possibly) causing this issue; please see below and let me know if I should open a tomcat7.0.35 JIRA/issue or atmosphere issue on atmosphere github, because I want to upload and/or share/provide the heap dump files; i'm assuming that I should 'not' attach the files via email, and it might not be readable to copy/paste the content here; please advise. # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x000180005310, pid=2396, tid=3724 # # JRE version: 7.0_11-b21 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.6-b04 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [tcnative-1.dll+0x5310] Java_org_apache_tomcat_jni_Socket_send+0xa0 # # Core dump written. Default location: D:\apache-tomcat-7.0.35\bin\hs_err_pid2396.mdmp # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x14f08000): JavaThread Atmosphere-AsyncWrite-60 daemon [_thread_in_native, id=3724, stack(0x1f13,0x1f23)] [1] https://github.com/Atmosphere/atmosphere/issues/869
RE: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs Sending this to tomee/openejb and tomcat user mailing lists. Cross-posting is really frowned upon. Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event SEVERE: Servlet.service() for servlet [Push Servlet] in context with path [/mcmsweb] threw exception java.lang.NumberFormatException: For input string: (TomEE)/7 at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.valueOf(Unknown Source) at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141) Sure looks like an Atmosphere problem from here... - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
Sending this to tomee/openejb and tomcat user mailing lists. Cross-posting is really frowned upon. Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event SEVERE: Servlet.service() for servlet [Push Servlet] in context with path [/mcmsweb] threw exception java.lang.NumberFormatException: For input string: (TomEE)/7 at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.valueOf(Unknown Source) at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141) Sure looks like an Atmosphere problem from here... - Chuck Thanks Chuck for the response, my apologies for cross-posting, and that part of the question, I was hoping to get a response from tomcat committers/users, and I was assuming the same, an Atmosphere issue.
RE: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs I was hoping to get a response from tomcat committers/users, and I was assuming the same, an Atmosphere issue. The other possibility is that TomEE (not supported on this mailing list) has set some value to a non-numeric string, whereas a true Tomcat only uses numeric values in that location. Without looking at the Atmosphere code, it's really impossible to tell. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
2013/1/30 Caldarale, Charles R chuck.caldar...@unisys.com: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs Sending this to tomee/openejb and tomcat user mailing lists. Cross-posting is really frowned upon. Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event SEVERE: Servlet.service() for servlet [Push Servlet] in context with path [/mcmsweb] threw exception java.lang.NumberFormatException: For input string: (TomEE)/7 at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.valueOf(Unknown Source) at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141) Sure looks like an Atmosphere problem from here... +1. https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129 That bz51881 method... an example of what you should never do... It tries to parse a version string to workaround a bug that was properly fixed more than a year ago, and fails horribly. It is a normal practice to modify the server info value, e.g. [1]. It is useless to rely on it. It is no wonder that the one used by TomEE is different from Tomcat. [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
On Tue, Jan 29, 2013 at 6:00 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs I was hoping to get a response from tomcat committers/users, and I was assuming the same, an Atmosphere issue. The other possibility is that TomEE (not supported on this mailing list) has set some value to a non-numeric string, whereas a true Tomcat only uses numeric values in that location. Without looking at the Atmosphere code, it's really impossible to tell. Understood about TomEE not supported on this list. Prior to using latest Atmosphere version (1.0.9) along with latest version of TomEE, I reached out to Jeanfrancois, and he confirmed that Atmosphere 1.0.10 is targeted for PrimeFaces Push users (like myself), and from what I understand, 1.0.9 fixed a simple software/typo mistake in 1.0.8, and I'm assuming that 1.0.9 should not be used to replace 1.0.8 by PrimeFaces Push users like myself. for now, i have reverted to Atmosphere 1.0.6, which was the recommended (and most applicable/appropriate version), weeks ago, to use with my PrimeFaces web app. I informed the tomee list that I will monitor this behavior for the meanwhile, and I'm looking forward to using/testing Atmosphere 1.0.10 when it is released.
Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs
On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2013/1/30 Caldarale, Charles R chuck.caldar...@unisys.com: From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] Subject: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died on me, nothing in server logs Sending this to tomee/openejb and tomcat user mailing lists. Cross-posting is really frowned upon. Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve event SEVERE: Servlet.service() for servlet [Push Servlet] in context with path [/mcmsweb] threw exception java.lang.NumberFormatException: For input string: (TomEE)/7 at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.valueOf(Unknown Source) at org.atmosphere.container.Tomcat7CometSupport.bz51881(Tomcat7CometSupport.java:141) Sure looks like an Atmosphere problem from here... +1. https://github.com/Atmosphere/atmosphere/blob/master/modules/cpr/src/main/java/org/atmosphere/container/Tomcat7CometSupport.java#L129 That bz51881 method... an example of what you should never do... It tries to parse a version string to workaround a bug that was properly fixed more than a year ago, and fails horribly. It is a normal practice to modify the server info value, e.g. [1]. It is useless to rely on it. It is no wonder that the one used by TomEE is different from Tomcat. [1] http://tomcat.apache.org/tomcat-7.0-doc/security-howto.html#Valves Interesting, thanks for the response, Konstantin.
