Common Errors

1. I noticed that some of the HTTP requests failed even though the Sports API was available at the time. What is wrong?

The feed and the Sports API only ensure "eventual consistency" meaning that a message associated with the sport event sent by the feed may refer to the sport event which is not YET available on the Sports API.

In such situations, the user should try to obtain the information at a later time. WARNING: Be sure not to associate a failed HTTP request with an "eventual consistency" limitation TO LIGHTLY, since this is rarely the cause.

2. Determining the state of the producers via log entries

SDK periodically creates execution log entries providing detailed information about all enabled producers.

.NET version

2018-03-05 12:58:46,734 INFO 7 ProducerRecoveryManager Status check: Producer=1(LO):[IsUp=False,Timestamp=01.01.0001-00:00:00.000(Started), Timing Info=[[Ping(Ok):age=00:00:01,918],[IsBehind(True):Alive(s)[all:age=00:08:17,088],NonAlives[all:latency=00:05:20,859]]].

The explanation can be found in .Net SDK - Common Logs Explained

Java version

2018-03-05 13:36:12,731 [INFO ] [uf-sdk-0] [c.s.u.s.impl.RecoveryManagerImpl] - Producers StatusCheck: (Producer[1 LO]:0:0:UP)(Producer[3 Ctrl]:7:7:UP)(Producer[4 BetPal]:5:6:UP)(Producer[5 PremiumCricket]:6:6:UP)

Explanation can be found in Java SDK - Common Logs Explained

3. When consuming feed messages I get the following error, what should I do?

The connection is shutdown. Cause: System.IO.EndOfStreamException: Unable to read beyond the end of the stream.

at RabbitMQ.Client.Impl.InboundFrame.ReadFrom(NetworkBinaryReader reader)

at RabbitMQ.Client.Framing.Impl.Connection.MainLoopIteration()

at RabbitMQ.Client.Framing.Impl.Connection.MainLoop()

Usually it indicates that the message being received is not processable, and no additional action needs to be taken. The customer should contact support.

4. Why did I receive OnUnparsableMessageReceived through SDK?

OnUnparsableMessageReceived was implemented to cover possible messages that can't be parsed by the SDK (or by your version of the SDK). The clients should most likely implement some logic to log such messages and be notified about them.

The message should be very rarely not be parsed, but some of the possible reasons for that to happen are invalid xml from the feed, or xml containing nodes SDK is not able to understand.