https://issues.apache.org/bugzilla/show_bug.cgi?id=54756
--- Comment #4 from Sebb <s...@apache.org> --- A bit more info from the crash log: the original cause of the crash is an access violation: Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [tcnative-1.dll+0x52f0] Java_org_apache_tomcat_jni_Socket_send+0xa0 The thread that invoked the JNI code is as shown in comment 2. Ideally, it should not be possible to crash the JVM - whether that is by bugs in the JVM native code or in user-provided JNI code as is the case here. Seems to me it should be possible to fix tcnative so it does not generate this access violation. The calling code has likely violated an expected calling sequence or pre-condition, but IMO that should still not be able to cause an access violation. Rather, some kind of exception should be thrown & should give a clue as to what went wrong so the application can be more readily fixed. -- 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
