DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44283>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44283 ------- Additional Comments From [EMAIL PROTECTED] 2008-01-31 01:33 ------- (In reply to comment #4) > The only call in tomcat native component to SSL_Write is in > sslnetwork.c:ssl_socket_send(). > Since the offset of failure is 4 in SSL_Write, it seems to me that SSL_Write > may > get a null or invalid pointer as parameter from ssl_socket_send() and crash > while trying to dereference parameter pointer. > Even if there is no certainty, it may really be an issue in tomcat native > code > and not in openssl. > Recompiling libtcnative with debug symbols and running the jvm under debugger > may help ... > > The simplest and quickest solution is to stop using APR and use standard HTTP > connector instead if it is possible (or NIO if you are bold :-). Thank you for your answer. But it's not a variant to switch to standard HTTP in my case because i am using Comet in my project and i really need scalable application. With NIO situation is very strange because when i am using NIO connector, server CPU usage unexpectedly grows to 100% until restarted (I am using Java 1.6 u4 so some bugs with selector fixed there but it didn't help me). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
