Re: getting connection error.... Socket Error: Connection reset by peer.
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
|
|
|
Re: getting connection error.... Socket Error: Connection reset by peer.
by ch.asad@gmail.com
::
Rate this Message:
HI, sorry i copied the config file from wrong looaction . in the config file i am sending data to localhost. Stunnel is sending data out correctly i have checked the logs.
here is my config file of qfix the defut part one rest is same.. default settings for sessions [DEFAULT] ConnectionType=initiator ReconnectInterval=20 LogonTimeout=30 StartTime=00:00:00 EndTime=23:00:00 HeartBtInt=10 #SocketConnectHost=localhost SocketConnectHost=127.0.0.1 FileLogPath=c:\qfixlogs\ FileStorePath=c:\qfixstore\ here is my Stunnel config ; Use it for client mode client = yes debug = 7 output = stunnel.log [https] accept = 127.0.0.1:9000 connect = 84.219.221.89:443 ;TIMEOUTclose = 0 Please suggest.
|
|
|
Re: getting connection error.... Socket Error: Connection reset by peer.
by ch.asad@gmail.com
::
Rate this Message:
here are my Stunnel logs for
2009.10.16 23:14:16 LOG7[5484:5436]: https connecting 84.219.221.89:443 2009.10.16 23:14:16 LOG7[5484:5436]: connect_wait: waiting 10 seconds 2009.10.16 23:14:17 LOG7[5484:5436]: connect_wait: connected 2009.10.16 23:14:17 LOG5[5484:5436]: https connected remote server from 192.168.2.3:3199 2009.10.16 23:14:17 LOG7[5484:5436]: Remote FD=368 initialized 2009.10.16 23:14:17 LOG7[5484:5436]: TCP_NODELAY option set on remote socket 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): before/connect initialization 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 write client hello A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 read server hello A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 read server certificate A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 read server done A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 write client key exchange A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 write change cipher spec A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 write finished A 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 flush data 2009.10.16 23:14:17 LOG7[5484:5436]: SSL state (connect): SSLv3 read finished A 2009.10.16 23:14:17 LOG7[5484:5436]: 1 items in the session cache 2009.10.16 23:14:17 LOG7[5484:5436]: 1 client connects (SSL_connect()) 2009.10.16 23:14:17 LOG7[5484:5436]: 1 client connects that finished 2009.10.16 23:14:17 LOG7[5484:5436]: 0 client renegotiations requested 2009.10.16 23:14:17 LOG7[5484:5436]: 0 server connects (SSL_accept()) 2009.10.16 23:14:17 LOG7[5484:5436]: 0 server connects that finished 2009.10.16 23:14:17 LOG7[5484:5436]: 0 server renegotiations requested 2009.10.16 23:14:17 LOG7[5484:5436]: 0 session cache hits 2009.10.16 23:14:17 LOG7[5484:5436]: 0 session cache misses 2009.10.16 23:14:17 LOG7[5484:5436]: 0 session cache timeouts
|
|
|
Re: getting connection error.... Socket Error: Connection reset by peer.
by Malinka Rellikwodahs
::
Rate this Message:
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html On Fri, Oct 16, 2009 at 13:31, ch.asad@... <ch.asad@...> wrote: > here is my config file of qfix the defut part one rest is same.. > > default settings for sessions > > [DEFAULT] > ConnectionType=initiator > ReconnectInterval=20 > > LogonTimeout=30 > StartTime=00:00:00 > EndTime=23:00:00 > HeartBtInt=10 > #SocketConnectHost=localhost > SocketConnectHost=127.0.0.1 I see no socket connect port, but according to your fix logs it's getting somehow > > FileLogPath=c:\qfixlogs\ > FileStorePath=c:\qfixstore\ > > > here is my Stunnel config > > ; Use it for client mode > client = yes > debug = 7 please turn logging level down some this makes it difficult to sort through the stunnel logs > output = stunnel.log > [https] > accept = 127.0.0.1:9000 in log you're connecting from 192.168.2.3? accept = 9000 will allow connections from anywhere > connect = 84.219.221.89:443 > ;TIMEOUTclose = 0 > personally i would try telnet on each individual piece until you find the part that isn't playing well, and start trying to change things there until it works. just like trouble shooting anything else break it down to what you can prove works or doesn't and then slowly add the complexity back in p.s. also when dealing with mailing lists it's best to make sure that you're at least cc'ing the mailing list still on a reply so that everyone still gets the relevant information ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Quickfix-developers mailing list Quickfix-developers@... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
| Free embeddable forum powered by Nabble | Forum Help |
