Closed abhideodhar closed 9 years ago
@abhideodhar the first ssl connection against a Simulator takes slightly longer than it should.
I increased the default _connecttimeout to 1 second for the SecureClient
to compensate for that.
By the way, if you want to get a secure connection with a drive I recommend you use the new SecureClient
class instead of Client
.
import kinetic
c = kinetic.SecureClient('209.243.160.69') # default port is 8443
c.connect()
# ...
c.close()
@icorderi - SecureClient doesn't support Async operations. How can be the async operations be ran with SSL in kinetic-py? Is SecureClient going to support Async operations?
Thanks, Neha
@icorderi -
I am seeing a SSL timeout issue while doing a connect via latest kinetic-python client on SSL port with the Kinetic Java simulator. Is this a client side issue or a server issue?
Thanks Abhijit
Client logs: [root@crane kinetic-py]# python Python 2.7.9 (default, Jul 30 2015, 05:49:38) [GCC 4.8.2 20140120 (Red Hat 4.8.2-16)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
Server side logs:
Jul 30, 2015 1:05:17 PM com.seagate.kinetic.simulator.io.provider.nio.NioMessageServiceHandler handlerRemoved INFO: connection info is removed, id=1438286686215, is secure channel=true Jul 30, 2015 1:05:20 PM com.seagate.kinetic.common.lib.TlsUtil enableSupportedProtocols INFO: enabled TLS protocol: [TLSv1, TLSv1.1, TLSv1.2] Jul 30, 2015 1:05:20 PM com.seagate.kinetic.simulator.io.provider.nio.NioQueuedRequestProcessRunner
INFO: nio queued process runner instantiated. message ordering is enforced.
Jul 30, 2015 1:05:20 PM com.seagate.kinetic.simulator.io.provider.nio.ssl.SslChannelInitializer initChannel
INFO: ssl nio channel initialized ...