
Hi, I am using quickfix application to connect to an exchange and receive market data. The connectivity to exchange is through SSL and am using stunnel 4.15. I see that stunnel dies, every time my quickfix application is restarted or sends a logout to server. Please let me know if a solution is in place. *Below is the stunnel.conf file:* cert = /home/bhavna/workspace/stunnel/str10100str.pem key = /home/bhavna/workspace/stunnel/str10100str.pem ; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 ; Some debugging stuff useful for troubleshooting debug = 7 output = /home/bhavna/workspace/stunnel/stunnel.log pid = /home/bhavna/workspace/stunnel/stunnel.pid ; Use it for client mode client = yes ; Service-level configuration [currenex_stream] ;accept = 127.0.0.1:1109 accept = 1110 ;prod details connect = server_IP:port TIMEOUTclose = 10 *Below are the version details of stunnel:*
./stunnel -version stunnel 4.15 on x86_64-redhat-linux-gnu with OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP
Global options debug = 5 pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes Service-level options cert = /etc/stunnel/stunnel.pem ciphers = AES:ALL:!aNULL:!eNULL:+RC4:@STRENGTH key = /etc/stunnel/stunnel.pem session = 300 seconds TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none *Logs:* 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL alert (read): warning: close notify 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL closed on SSL_read 2010.06.16 18:59:23 LOG7[6401:1084586304]: Socket write shutdown 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL write shutdown 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL alert (write): warning: close notify 2010.06.16 18:59:23 LOG6[6401:1084586304]: SSL_shutdown successfully sent close_notify 2010.06.16 18:59:23 LOG5[6401:1084586304]: Connection closed: 109 bytes sent to SSL, 129 bytes sent to socket 2010.06.16 18:59:23 LOG7[6401:1084586304]: currenex_stream finished (0 left) -- Thanks, Bhavna DISCLAIMER: This e-mail and any attachments are for the confidential use of the intended recipient. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any investment product, an official confirmation of any transaction or an official statement of Quantitative Brokers, LLC. E-mail transmissions cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. Quantitative Brokers may, at its discretion, monitor and review the content of all e-mail communications.

Adding to the info below: Its a Mac OS with
gcc -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux Thread model: posix gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
openssl version OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
On Thu, Jun 17, 2010 at 11:43 AM, Bhavna Jhunjhunwala < bhavnaj@quantitativebrokers.com> wrote:
Hi,
I am using quickfix application to connect to an exchange and receive market data. The connectivity to exchange is through SSL and am using stunnel 4.15. I see that stunnel dies, every time my quickfix application is restarted or sends a logout to server. Please let me know if a solution is in place.
*Below is the stunnel.conf file:* cert = /home/bhavna/workspace/stunnel/str10100str.pem key = /home/bhavna/workspace/stunnel/str10100str.pem
; Some performance tunings socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1
; Some debugging stuff useful for troubleshooting debug = 7 output = /home/bhavna/workspace/stunnel/stunnel.log
pid = /home/bhavna/workspace/stunnel/stunnel.pid
; Use it for client mode client = yes
; Service-level configuration
[currenex_stream] ;accept = 127.0.0.1:1109 accept = 1110 ;prod details connect = server_IP:port TIMEOUTclose = 10
*Below are the version details of stunnel:*
./stunnel -version stunnel 4.15 on x86_64-redhat-linux-gnu with OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 Threading:PTHREAD SSL:ENGINE Sockets:POLL,IPv6 Auth:LIBWRAP
Global options debug = 5 pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes
Service-level options cert = /etc/stunnel/stunnel.pem ciphers = AES:ALL:!aNULL:!eNULL:+RC4:@STRENGTH key = /etc/stunnel/stunnel.pem session = 300 seconds TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds verify = none
*Logs:*
2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL alert (read): warning: close notify 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL closed on SSL_read 2010.06.16 18:59:23 LOG7[6401:1084586304]: Socket write shutdown 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL write shutdown 2010.06.16 18:59:23 LOG7[6401:1084586304]: SSL alert (write): warning: close notify 2010.06.16 18:59:23 LOG6[6401:1084586304]: SSL_shutdown successfully sent close_notify 2010.06.16 18:59:23 LOG5[6401:1084586304]: Connection closed: 109 bytes sent to SSL, 129 bytes sent to socket 2010.06.16 18:59:23 LOG7[6401:1084586304]: currenex_stream finished (0 left)
-- Thanks, Bhavna
-- Thanks, Bhavna Quantitative Brokers 646 293 1808 DISCLAIMER: This e-mail and any attachments are for the confidential use of the intended recipient. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any investment product, an official confirmation of any transaction or an official statement of Quantitative Brokers, LLC. E-mail transmissions cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice. Quantitative Brokers may, at its discretion, monitor and review the content of all e-mail communications.
participants (1)
-
Bhavna Jhunjhunwala