You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Hudson (Commented) (JIRA)" <ji...@apache.org> on 2012/03/02 07:14:59 UTC
[jira] [Commented] (THRIFT-1523) clientTimeout not worked as
expected in TServerSocket created by TSSLTransportFactory
[ https://issues.apache.org/jira/browse/THRIFT-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220710#comment-13220710 ]
Hudson commented on THRIFT-1523:
--------------------------------
Integrated in Thrift #422 (See [https://builds.apache.org/job/Thrift/422/])
THRIFT-1523: clientTimeout not worked as expected in TServerSocket created by TSSLTransportFactory
Client: java
Patch: Alexey Sviridov
Adds server timeout to SSLTransportFactory (Revision 1296053)
Result = SUCCESS
jfarrell : http://svn.apache.org/viewvc/?view=rev&rev=1296053
Files :
* /thrift/trunk/lib/java/src/org/apache/thrift/transport/TSSLTransportFactory.java
> clientTimeout not worked as expected in TServerSocket created by TSSLTransportFactory
> -------------------------------------------------------------------------------------
>
> Key: THRIFT-1523
> URL: https://issues.apache.org/jira/browse/THRIFT-1523
> Project: Thrift
> Issue Type: Bug
> Components: Java - Library
> Affects Versions: 0.6.1, 0.7, 0.8, 0.9
> Reporter: Alexey Sviridov
> Assignee: Alexey Sviridov
> Priority: Blocker
> Fix For: 0.9
>
> Attachments: clientTimeout.patch
>
>
> TSSLTransportFactory has method
> public static TServerSocket getServerSocket(int port, int clientTimeout)
> there is parameter clientTimeout that need to close idle client connections (after clientTimeout amount of millis of client inactivity server closes opened connection themself, not waiting while client called close() method). This parameter work fine when create TServerSocket through new, but not working at all when creating TServerSocket through TSSLTransportFactory.getServerSocket
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira