https://issues.apache.org/bugzilla/show_bug.cgi?id=57521
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Shunsuke Tanaka from comment #2) > Please tell me the tomcat and tc-native version it had been fixed. > The system run in production environment, so if I upgrade > the tomcat and tc-native, I have to prove to my customer > this problem never appear. If you need to prove to your customer that the problem [will] never appear, then that's your job, since they are paying you to get the job done. > https://issues.apache.org/bugzilla/show_bug.cgi?id=51813 > > In the above ticket, it has been commented that "Please re-open if it > appears". So why didn't you re-open that ticket if you are having the same problem? Let me save you some time: the patch went into 1.1.28 but it only tries to prevent the JVM from crashing when the application is doing something it should not be doing (like keeping references to request and response objects). That patch fixes nothing other than the symptom (the JVM crash)... the core problem is misuse of resources. In reviewing the code (again) for sendbb, there are very few opportunities for a null-pointer de-reference. Are you able to re-build tcnative with debugging symbols and do some back-tracing for me? "sendbb+0x75" can mean different things depending upon the environment. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
