UI Unresponsive

[PHOLAN]

I'm using the NT .Net API to place orders. Every 2 minutes, it queries the market position, cancels previous orders and places new ones.
There is a market subscription for a single instrument that retrieves the last price every 2 seconds.

The behavior being experienced is that the NT UI is not showing on the screen. You can see it minimized but, event when clicked on it, it does not maximize. The UI is however, responsive to the commands sent in a normal way.

Even when the data subscription is stopped, the UI still does not come back.

Any ideas?

Thanks

[NinjaTrader_Ray]

What do you mean by minimized? In Windows Task bar or just smaller version on your screen? If the latter, a screen shot would be of value.

[PHOLAN]

It just shows in the taskbar only. Clicking on it doesn't do anything.
The Windows TaskManager reports it as Non Responding, however, API calls to it responde successfully.
I have experienced the problem multiple times.

Thanks,
P

[NinjaTrader_Ray]

What if you right click on the task bar icon and select either "Restore" or "Maximize" ?

[PHOLAN]

they are both grayed out. Only close is available.

P

[NinjaTrader_Ray]

Never heard of that. What you can do is shut down NT and manually delete workspace files (you will lose them) to reset NT's Control Center location.

- Shut down NT
- Delete all files in the following folder My Documents\NinjaTrader 6.5.\workspaces
- Restart NT

[PHOLAN]

Ray,

It just happened again today with the first order. Right after cleaning the workspace.
NT was unresponsive and then came back. What I saw is that my place order was sent once but, it appeared as active 3 times under orders. All identical.

Onother thing that I noiced by looking at my log is that I sent the Cancel from the previous one and the place for the new one too close together and from different threads.

This brings me the question, can instructions to NT via the API be done async, multi-threading or they need to be queued and send one by one from the same thread?


P

[NinjaTrader_Dierk]

>> they need to be queued and send one by one from the same thread?
Yes, to be safe. We haven't tested any multi-threading on the .NET ATI.

[PHOLAN]

My Proxy is Multi-Thread so, I will FIFO the requests and send them sequentially to see what happens. I will report back.

Thanks Dierk

P

[PHOLAN]

Sending instructions sequentially worked. Introducing some Mutex and Synclocks solved that problem.

I'm now experiencing a new one from time to time. NT reports an open position but, the API reports none open. I restarted NT, verified that the instrument and account are correct and they were. Still the problem persisted.

Any thoughts?

Philip

[NinjaTrader_Dierk]

Hmm ... would not know what could cause that.

[PHOLAN]

I manually closed the position and reopened and it it then reported properly. Not sure what could cause the NT be out of sync with the API calls.

Can you think of any way of detecting when this happens so that I can send an SMS to myself?

[NinjaTrader_Dierk]

Sorry no. We would need a reproducible scenario to understand what's going on.

[PHOLAN]

Is it feasible to monitor the NT access database directly without manipulating it?
If so, what are the numeric field status codes?

I'm concerned with real live positions not being closed if they are not reported as open.

I looked at the database structure and if this happens again, I might be able to troubleshoot it and give you additional information.

Regards

[NinjaTrader_Dierk]

>> Is it feasible to monitor the NT access database directly without manipulating it?
Sorry no.