Java crash in 64 bit windows

[Dyno Brium]

My JBT instance crashed yesterday during forward testing. My experience is that java crash more frequently in 64 bit windows system. Is there anyone have similar problem? How to avoid that?

I am also looking for a java profiler. I would like to know what kind of java profiler you prefer.

Thanks.

[k]

I've ran JBT for over a year and never experienced it crashing (live trading + foward testing) in windows 7 (64 bit edition).
Could it be your custom strategies?  You should probably post the stack trace.

[Marcus Williford]

I use jvisualvm lately, and wow it is great.   Seems a bit more advanced than the standard jconsole, so I switched.

Please post the stacktrace, and let us know what version you are using out of the repo.

--
You received this message because you are subscribed to the Google Groups "JBookTrader" group.

To view this discussion on the web visit https://groups.google.com/d/msg/jbooktrader/-/4RydCUBWGF0J.

To post to this group, send email to jbook...@googlegroups.com.
To unsubscribe from this group, send email to jbooktrader...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.

[Eugene Kononov]

Dyno, in addition to the stacktrace, please post your EventReport.html. I run JBT under 64-bit Windows as well, never had JBT crashed.

[Dyno Brium]

I found the problem was probably due to an older version of java in my PC. Java is automatic updated, but only for the 32bit version. 64bit version has never been updated. I have to manually update the 64bit version. After the update, no crash any more.

I updated TWS yesterday. My order for ES didn't execute this morning. The event log ends with this line:

02/07/13

10:23:26.986

LongDefender2012

Placing order 6

I check the TWS log. This is what happen around that time:

PS 10:23:26:995 JTS-CCPDispatcher-53: REQUESTING
PS 10:23:35:765 AWT-EventQueue-0: moving dialog to front:
PS 10:23:40:766 AWT-EventQueue-0: dialog is shown and registerd, doing nothing:

A warning window pop up from TWS. I don't remember the exact words in the window, probably about market order cap.

I don't know if there is something different in the latest version of TWS, or it is because of the pop up window. It also looks like JBooktrader does not remove the open order.

Does anybody have experience with non-executed order? please share your thoughts.

[Eugene Kononov]

A warning window pop up from TWS. I don't remember the exact words in the window, probably about market order cap. 

It also looks like JBooktrader does not remove the open order. 
Does anybody have experience with non-executed order? please share your thoughts.

By design, JBT will indefinitely wait for the order to be executed, before any other orders can be submitted. In your case, it looks like your "market order cap" was set too low. In my TWS configuration, I override it. See the attached image.