Posted: Oct 28, 2011 @ 08:28 AM             Msg. 1 of 4

Broker is unavailable?
HIGH Priority Notification at Fri Oct 28 12:22:52 BRST 2011:
Broker unavailable
Open E Cry (OEC) is no longer available.

---

Rufo André Paganini

Posted: Oct 28, 2011 @ 08:59 AM             Msg. 2 of 4

we are receiving an error SendingTime accuracy problem. It's happen today at 12:22


Can you verify for us?

---

Rufo André Paganini

Posted: Oct 28, 2011 @ 09:31 AM             Msg. 3 of 4

Your heartbeats were marked correctly (around 12:22) and coincides with our clocks:
07:22:30.300 FIX.4.4:OEC->RPaganini2TM <- 8=FIX.4.4
9=57
35=0
34=1492
49=OEC
52=20111028-12:22:30
56=RPaganini2TM
10=197

07:22:30.335 FIX.4.4:OEC->RPaganini2TM -> 8=FIX.4.4
9=61
35=0
34=1480
49=RPaganini2TM
52=20111028-12:22:29.515
56=OEC
10=142


Then, your server dropped the connection:

07:22:52.534 FIX.4.4:OEC->RPaganini2TM Socket Error: Connection reset by peer.
07:22:52.534 FIX.4.4:OEC->RPaganini2TM Disconnecting

And then your server sent to us Logon request with 2 hours offset (14:22):
07:22:53.581 FIX.4.4:OEC->RPaganini2TM -> 8=FIX.4.4
9=89
35=A
34=1
49=RPaganini2TM
52=20111028-14:22:53.531

We do not check SendingTime accuracy and our server responded with Logon response with 12:22:

07:22:53.602 FIX.4.4:OEC->RPaganini2TM <- 8=FIX.4.4
9=72
35=A
34=1
49=OEC
52=20111028-12:22:53
56=RPaganini2TM
98=0
108=30
141=Y
10=127


Probably, your server excepted 14:22 from us by some reasons.

---

Victor Vins
Lead Software Developer

Posted: Oct 28, 2011 @ 12:01 PM             Msg. 4 of 4

Sorry VictorV. I believe it was our fault because I change the timezone windows configuration with the server running.

I got it working back after.

---

Rufo André Paganini