On Tue, Jan 29, 2013 at 6:08 PM, Konstantin Kolinko <knst.koli...@gmail.com>wrote:
> 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 (0xc0000005) at pc=0x0000000180005310, 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 (0x0000000014f08000): JavaThread "Atmosphere-AsyncWrite-60" daemon [_thread_in_native, id=3724, stack(0x000000001f130000,0x000000001f230000)] [1] https://github.com/Atmosphere/atmosphere/issues/869
