Is there any way through coding or configuration to create FIX session which lasts for more than a week.
I checked the Configuring QuickFIX, but i cannot find any information there.
I don't think any version of QuickFIX allows this.
However, I'm unaware of any FIX party that uses a longer-than-weeklong session. (I'm not even sure if the FIX specification permits that.)
You can have session as long as you want. In QuickFixJ there is a configuration
NonStopSession=Y
(https://www.quickfixj.org/usermanual/1.6.4/usage/configuration.html).
In your application, who is terminating the connection? Is it Acceptor or Initiator?
You can configure start day as monday and end day as sunday to run the session for entire week.
Please look for startDay and EndDay at https://www.quickfixj.org/usermanual/1.6.4/usage/configuration.html
Related
I have a question about the RTC on STM43F429. I have a board that manages the RTC date and Time with a battery backup.
After some test I have this problem: after a reset , when I try to read the RTC time for the first time, the RTC seems stopped (I see hh:mm:ss stipped) but if I look at the internal RTC register (with debugger) all is OK... so I cant read the current time.
To solve this I have to read the date before and then I can read the time and the RTC is running correctly.. I don't understand why I have to read the date before to read the time. Can someone explay this? Thanks
You need wait when data from RTC will be synchronised with their shadow registers, it is every two RTC clocks, and can be checked with RTC_ISR.RSF (Registers Synchronisation Flag).
More info is in Reference manual section 26.3.2 Real-time clock and calendar.
It seems QuickFIX has not log rotation feature.
Is it possible to do it somehow?
This post shows the rotation might have been released longtime ago. There mayn't be any config change to be made, maybe you need to implement it yourself as described in the post.
Here it explains that it isn't possible to rotate without shutting down your engine. Your engine would have the old hook to the logfile and when it sees that the log file doesn't exist, probably would crash. In the same post it explains that divide your multiple seesions for each day, 7 logs for 7 dys in the week. Should be a plausible method to do it, when you shouldn't be restarting your engine in the middle of a day.
Microsoft word allows us to add datetime stamp which will update datetime and sync up with system datetime. I am looking for a similar item. Is there a countdown item available?
Usage: When I send a document to my colleague I mention this event will happen in 5 minutes.
Ex: I will kick the build in 5 minutes.
I am trying to express the same in the following way
Build will happen in 5:00 Minutes
after a second
Build will happen in 4:59 Minutes
after five minute
Build will happen in 0:00 Minutes
or
Build happend
Does MSword capable of doing this?
Thanks,
Esen
There is no count down timer control kind of thing available. You have to write a macro to do that for you. Even if you use macro, unless the receipt user enable its content he wont see it. I would suggest use a javascript and send email with html body
Is there any way to increase the maximum time that a plugin can execute for?
It's 2 minutes by default. I found that here.
The limit is there to help protect the performance of the server, so the correct approach here is to re-engineer your solution (e.g. move your intensive logic out into a workflow or a web service and call it asynchonrously).
I'm not aware of any setting, flag or registry entry that will extend the two-minute timeout, though if you must persevere, you may find it possible to fudge a solution by wrapping your logic in a try/catch block, catching System.TimeoutExceptionand continuing your code. Maybe (untested).
I'd like to add that it seems that the time limit only applies when a plugin is registered in a sandbox / partial trust mode.
We had this kind of an issue and solved it by registering the plugin in fully trusted (non-sandbox) mode. I verified this by using Thread.Sleep function to wait 2 minutes before even starting to executing any plugin logic. In total almost 4 minutes were spent but the plugin still managed to do well when in non-sandbox mode. In a sandbox mode it threw us a 2 minutes exception.
According to E-learning material from Microsoft sandbox plugins in CRM 2013 has only 30 seconds limit instead of 120 seconds. I haven't tested that out yet.
When I test some web page using fiddler, sometimes the clientconnected time in the statistics tab is several seconds earlier than the clientDoneReqest time, so it makes the over all time much longer than the actual time it takes to load the page. is this a known issue or I missed something?
thanks.
This is a known issue which is introduced by the fact that the latest version makes much better reuse of client sockets.
You're now seeing the time when the original client socket was opened, for a prior request. In an upcoming version of Fiddler (v.2.2.9) it will be much more clear what's going on, as a new timestamp will be introduced for the client request.