Can´t connect to initiator (QuickFix .NET wrapper -> QuickFixN) about quickfixn HOT 6 CLOSED

I tried to debug both old and new solutions, here are my results:
Old .NET QuickFix wrapper:

• OnCreate event is called after calling the constructor of initiator,
• calling start method
• toAdmin event fires and initiates the connection - with the new API this event is never called so I guess there is some kind of socket error but no exceptions are called.

from quickfixn.

I think I found the error in method SocketInitiator.OnStart:

Environment.TickCount is returning negative number on my system so the Connect method is never called.
I think this should be considered as bug since TickCount can return negative number:

"The value of this property is derived from the system timer and is stored as a 32-bit signed integer. Consequently, if the system runs continuously, TickCount will increment from zero to Int32.MaxValue for approximately 24.9 days, then jump to Int32.MinValue, which is a negative number, then increment back to zero during the next 24.9 days."
Source: http://msdn.microsoft.com/en-us/library/system.environment.tickcount.aspx

from quickfixn.

Simple solution should fix this issue (my connection work after this change):

    protected override void OnStart()
    {
        shutdownRequested_ = false;

        while(!shutdownRequested_)
        {
            int reconnectIntervalAsTicks = 1000 * reconnectInterval_;
            int nowTickCount = Environment.TickCount;
            if (nowTickCount < 0)
                nowTickCount *= -1;

            if ((nowTickCount - lastConnectTickCount) >= reconnectIntervalAsTicks)
            {
                Connect();
                lastConnectTickCount = nowTickCount;
            }

            Thread.Sleep(1 * 1000);
        }
    }

from quickfixn.

Dupe of #42.

By the way, the proper avenue for help is the mailing list.
http://quickfixn.org/help

Issues are for bug and new-feature tracking.

from quickfixn.

Thanks for answer. Next time I will use the mailing list. But to be accurate, it was a bug after all ;-) but it taked me more time to realize it...

from quickfixn.

No problem :)

from quickfixn.