If you use the TimeZoneOffset to control when EOD runs it will open the same cache file after EOD runs. This problem only occurs when TimeZoneOffset is > 0.
Class: SocketEngine
Method: MessageCacheInit
Old Code: DateTime dtOpen = DateTime.Now.Date.AddHours(_iTimeZoneOffset);
New Code: DateTime dtOpen = DateTime.Now.AddHours(_iTimeZoneOffset).Date;
I must have added the TimeZoneOffset at the end and didn't realize what I was doing. Stripping out the time portion before adding the TimeZoneOffset causes it to open the same file after EOD runs which means MsgSeqNum did get reset.
Charles Easton
East Tech Incorporated
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you use the TimeZoneOffset to control when EOD runs it will open the same cache file after EOD runs. This problem only occurs when TimeZoneOffset is > 0.
Class: SocketEngine
Method: MessageCacheInit
Old Code: DateTime dtOpen = DateTime.Now.Date.AddHours(_iTimeZoneOffset);
New Code: DateTime dtOpen = DateTime.Now.AddHours(_iTimeZoneOffset).Date;
I must have added the TimeZoneOffset at the end and didn't realize what I was doing. Stripping out the time portion before adding the TimeZoneOffset causes it to open the same file after EOD runs which means MsgSeqNum did get reset.
Charles Easton
East Tech Incorporated