[
https://issues.apache.org/jira/browse/AXISCPP-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496748
]
nadir amra commented on AXISCPP-1031:
-------------------------------------
Wayne,
The code should be throwing an exception on the initial error. It does not. I
can make the code changes so that the SSL transport throws an exception (not
sure why it does not), but can you test given that I do not have the resources
or expertise in open SSL?
Otherwise, I can make your change but I do not think it is the right thing to
do....it seems to hide the fact that there was an error.
> 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
>
>
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
