Re: [Quickfix-users] Gathering more information about connection problems

[C. G. <let...@gm...>]

Thank you for your help :)
Problem is, no messages are ever sent or recieved. I does however seem to be
like you say, the socket is gets closed on QF, or maybe it fails to open in
the first place. I'm thinking something like the old connection is still
lingering about, and the port is held busy by the OS, or somesuch. That's
why I'd like to try prying more information about just what "connection
failed" means. :)


2008/5/22 Malinka Rellikwodahs <ael...@gm...>:

> the .NET quickfix is a Managed C++ wrapper to the C++ quickfix, so the .NET
> methods and classes just call the C++ methods and classes with some extra
> code for Garbage collection, so most likely you found the line that was
> causing the log in your log file
>
> now i'm fairly sure that what causes a log sequence like that is when QF
> tried to connect and send data to the other end the socket got closed on it,
> you can look at your message log and see what messages you sent and
> recieved, and verify if they are valid, also try pinging and telneting to
> your server if you can telnet to the server then they closed the connection
> on you after parsing the message and your message is wrong somehow (bad
> protocol behavior but happens), otherwise if you can't verify firewall
> settings on your end and contact the other end and verify firewall and such
>
> however if you really still want to change the log event then that c++ code
> you found is the place to change it
>
> On Thu, May 22, 2008 at 5:53 AM, Claes Gyllenswärd <let...@gm...>
> wrote:
>
>> QuickFIX Documentation:
>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>
>>
>>
>> I'm happily using quickfix and it works great.
>> Every evening, at 22.00, the remote side turns off it's systems, and I
>> need to wait until next morning when they come up again.
>> My application attempts to reconnect continously but fails.
>> The remote side say they never see any connection attempt at all, so I'm
>> guessing for some reason, I fail to open a new socket during morning. My log
>> simply says
>>
>> 20080522-08:46:09 : Connecting to xxx.xxx.xxx.xxx on port yyyyy
>> 20080522-08:46:31 : Connection failed
>>
>> Since "Connection Failed" doesn't tell me much, I started looking for
>> where the error occured, so I could add some extra error handling code.
>> The only place I can find this message "Connection Failed" is in the c++
>> source files. I use .net, so I'm guessing that's not really relevant in my
>> case.
>>
>>
>> Could anyone give me some ideas about what to look for, so I can gather
>> more information about my problem?
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Quickfix-users mailing list
>> Qui...@li...
>> https://lists.sourceforge.net/lists/listinfo/quickfix-users
>>
>>
>