You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "nadir amra (JIRA)" <ax...@ws.apache.org> on 2007/05/18 06:00:16 UTC
[jira] Updated: (AXISCPP-1031) SSL_write called with
m_sslHandle=null when socket closed
[ https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra updated AXISCPP-1031:
--------------------------------
Attachment: HTTPSSLChannel.hpp
HTTPSSLChannel.cpp
Wayne, try these out. I have not compiled the code so you might get some stupid compile errors, if so, let me know. I tried to ensure correctness.
Please ensure that everything works, and then the error condition that you were encountering (i.e. timeout).
Thanks
> SSL_write called with m_sslHandle=null when socket closed
> ---------------------------------------------------------
>
> Key: AXISCPP-1031
> URL: https://issues.apache.org/jira/browse/AXISCPP-1031
> Project: Axis-C++
> Issue Type: Bug
> Components: Transport (axis3)
> Affects Versions: 1.6 Final
> Environment: Testing with Axis[J] on a jetty server. Server has maxIdleTime=60000 (for testing, but any time could be used). WIndowsXP.
> Reporter: Wayne Johnson
> Fix For: 1.6 Final
>
> Attachments: HTTPSSLChannel.cpp, HTTPSSLChannel.hpp
>
>
> When Jetty closes the socket due to maxIdleTime, the next write (from httptransport.cpp, ~line 264) detects the closure and calls HTTPSSLChannel::OpenSSL_Close(), which sets m_sslHandle = NULL. httptransport.cpp, ~line 265 then calls the m_pActiveChannel->writeBytes() again to send the remainder of the packet (without checking if the first write succeded). The null handle causes a crash.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org