Thread: [Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

Brought to you by: orenmnero

quickfix-developers

[Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: <ch...@gm...> - 2009-10-16 16:54:29

Hi i am trying to connect to FIX server.....  I am using Stunnel for SSL. but
i am got getting loged on.
Below is my log file....

20091014-16:28:18 : Created session
20091014-16:28:20 : Connecting to 127.0.0.1 on port 9000
20091014-16:28:20 : Initiated logon request
20091014-16:28:21 : Socket Error: Connection reset by peer.
20091014-16:28:21 : Disconnecting
20091014-16:28:41 : Connecting to 127.0.0.1 on port 9000
20091014-16:28:41 : Initiated logon request
20091014-16:28:42 : Socket Error: Connection reset by peer.
20091014-16:28:42 : Disconnecting

Config file setting are as follows..

[DEFAULT]
ConnectionType=initiator
ReconnectInterval=20
StartTime=12:00:00
EndTime=23:00:00
SenderCompID=TW
SenderSubID=user1
HeartBtInt=10
SocketConnectPort=443
SocketConnectHost=ssl://84.219.221.89
FileLogPath=c:\qfixlogs\
FileStorePath=c:\qfixstore\

# session definition
[SESSION]
# inherit ConnectionType, ReconnectInterval and SenderCompID from default
BeginString=FIX.4.4
TargetCompID=ISLD
TargetSubID=qftrade
HeartBtInt=10
FileLogPath=c:\qfixlogs\
FileStorePath=c:\qfixstore\
DataDictionary=C:\quickfix-1.12.4\quickfix\spec\FIX44.xml

here are The messages in the message log....

8=FIX.4.49=9035=A34=149=inttest50=trader152=20091014-16:28:20.42056=FXALL96=fxall12398=0108=1010=041
8=FIX.4.49=9035=A34=249=inttest50=trader152=20091014-16:28:41.41656=FXALL96=fxall12398=0108=1010=050


Please guide me whats the issue in this????
-- 
View this message in context: http://www.nabble.com/getting-connection-error....-Socket-Error%3A-Connection-reset-by-peer.-tp25928657p25928657.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

[Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: <ch...@gm...> - 2009-10-16 17:10:25

Hi i am trying to connect to FIX server.....  I am using Stunnel for SSL. but
i am got getting loged on.
Below is my log file....

20091014-16:28:18 : Created session
20091014-16:28:20 : Connecting to 127.0.0.1 on port 9000
20091014-16:28:20 : Initiated logon request
20091014-16:28:21 : Socket Error: Connection reset by peer.
20091014-16:28:21 : Disconnecting
20091014-16:28:41 : Connecting to 127.0.0.1 on port 9000
20091014-16:28:41 : Initiated logon request
20091014-16:28:42 : Socket Error: Connection reset by peer.
20091014-16:28:42 : Disconnecting

Config file setting are as follows..

[DEFAULT]
ConnectionType=initiator
ReconnectInterval=20
StartTime=12:00:00
EndTime=23:00:00
SenderCompID=TW
SenderSubID=user1
HeartBtInt=10
SocketConnectPort=443
SocketConnectHost=ssl://84.219.221.89
FileLogPath=c:\qfixlogs\
FileStorePath=c:\qfixstore\

# session definition
[SESSION]
# inherit ConnectionType, ReconnectInterval and SenderCompID from default
BeginString=FIX.4.4
TargetCompID=ISLD
TargetSubID=qftrade
HeartBtInt=10
FileLogPath=c:\qfixlogs\
FileStorePath=c:\qfixstore\
DataDictionary=C:\quickfix-1.12.4\quickfix\spec\FIX44.xml

here are The messages in the message log....

8=FIX.4.4 9=90 35=A 34=1 49=TW 50=user1 52=20091014-16:28:20.420 56=ISLD
96=1234567 98=0 108=10 10=041
8=FIX.4.4 9=90 35=A 34=2 49=TW 50=User1 52=20091014-16:28:41.416 56=ISLD
96=1234567 98=0 108=10 10=050


Please guide me whats the issue in this????
-- 
View this message in context: http://www.nabble.com/getting-connection-error....-Socket-Error%3A-Connection-reset-by-peer.-tp25928930p25928930.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: Malinka R. <ael...@gm...> - 2009-10-16 17:12:19

On Fri, Oct 16, 2009 at 12:54, ch...@gm... <ch...@gm...> wrote:
> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> Hi i am trying to connect to FIX server.....  I am using Stunnel for SSL. but
> i am got getting loged on.
> Below is my log file....

your config and your logs don't match, and we'd need to see your
stunnel config, but off the top of my head stunnel is either not
running or not configured right

Re: [Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: <ch...@gm...> - 2009-10-16 17:31:58

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.

Malinka Rellikwodahs wrote:
> 
> 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 12:54, ch...@gm... <ch...@gm...>
> wrote:
>> QuickFIX Documentation:
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>> Hi i am trying to connect to FIX server.....  I am using Stunnel for SSL.
>> but
>> i am got getting loged on.
>> Below is my log file....
> 
> your config and your logs don't match, and we'd need to see your
> stunnel config, but off the top of my head stunnel is either not
> running or not configured right
> 
> ------------------------------------------------------------------------------
> 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
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

-- 
View this message in context: http://www.nabble.com/Re%3A-getting-connection-error....-Socket-Error%3A-Connection-reset-by-peer.-tp25929021p25929334.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: <ch...@gm...> - 2009-10-16 17:35:09

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



ch...@gm... wrote:
> 
> 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.
> 
> Malinka Rellikwodahs wrote:
>> 
>> 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 12:54, ch...@gm... <ch...@gm...>
>> wrote:
>>> QuickFIX Documentation:
>>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>>
>>>
>>> Hi i am trying to connect to FIX server.....  I am using Stunnel for
>>> SSL. but
>>> i am got getting loged on.
>>> Below is my log file....
>> 
>> your config and your logs don't match, and we'd need to see your
>> stunnel config, but off the top of my head stunnel is either not
>> running or not configured right
>> 
>> ------------------------------------------------------------------------------
>> 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
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Re%3A-getting-connection-error....-Socket-Error%3A-Connection-reset-by-peer.-tp25929021p25929382.html
Sent from the QuickFIX - Dev mailing list archive at Nabble.com.

Re: [Quickfix-developers] getting connection error.... Socket Error: Connection reset by peer.

From: Malinka R. <ael...@gm...> - 2009-10-16 17:50:51

On Fri, Oct 16, 2009 at 13:31, ch...@gm... <ch...@gm...> 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