thank you for your efforts with the plugin, let's try to collaborate to get this done!
Since yesterday and with the idea to break down issues, i actually have two Z12 Zorro instances working on two different live accounts from Dukascopy, in two different AWS instances.
#1 in a T2.micro instance, the one you already got the log file #2 in a M3.medium instance, which has a complete different profile and should cope with 10 Zorros simultaniusly (at least).
Just according to Murphy, today I got some troubles with the M3.medium isntance as follows:
Weekend ends on 25.11. 23:00 [677: Mon 18-11-26 00:22] 11174.54/11227.7911174.54/11203.59 -6.18 [678: Mon 18-11-26 04:22] 11203.59/11242.0911200.49/11238.89 -6.18 [679: Mon 18-11-26 08:22] 11238.89/11339.4211234.99/11332.39 -1.48 Enter 1L UK100 Stop 568.7 Trail 568.7 at 08:22:01 {UK100:HU:l7901} Long 1@7024.03 Risk 627 ts at 08:22:01 Stop 6455 Trail 7593 TP 0.0 Com 0000 Mrg 0000 Net 0 Enter 1L UK100 Stop 0.25747 at 08:22:01 !ERROR java.util.concurrent.ExecutionException: com.dukascopy.api.JFException: state is CANCELED
Caused by: com.dukascopy.api.JFException: state is CANCELED
!java.util.concurrent.ExecutionException !com.dukascopy.api.JFException: state is CANCELED Error 075: (UK100:NET:L) - can't open 1@7024 Stop 1756 at 08:22:01 UK100 Pool: 0 Virtual: 1
I'll give you all messages i get from the plugin from these two different instances. Hopefully this helps you in the development.
According the jcl's team, they have good experience with 3 Zorro instances working on a T2.micro, but not with Dukascopy and not with a java based plugin I suppose.
