Lieber Besucher, herzlich willkommen bei: INVESTOX-Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
Dienstag, 19. Februar 2008, 18:31
TWS Log File voll mit Meldungen, bei euch auch so?
Hallo, in meinem TWS Log File tauchen alle 2-5 Minuten diese Meldungen auf. Ist es auch bei anderen so und normal? 
Die Log-Files werden defaultmäßig abgelegt in C:\Jts\log.Thu.txt
Die Log-Files werden defaultmäßig abgelegt in C:\Jts\log.Thu.txt
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
WM 09:15:20:177 AWT-EventQueue-0: Updating application time WM 09:15:20:177 AWT-EventQueue-0: New CCP Offset: 574 ms WM 09:16:02:529 JTS-DeadlockMonitor-1: Memory: total=50925568 free=9435024 WM 09:21:07:571 JTS-DeadlockMonitor-1: Memory: total=50925568 free=9145680 WM 09:25:19:978 AWT-EventQueue-0: Updating application time WM 09:25:19:978 AWT-EventQueue-0: New CCP Offset: 689 ms WM 09:26:12:634 JTS-DeadlockMonitor-1: Memory: total=50925568 free=9106800 WM 09:31:17:679 JTS-DeadlockMonitor-1: Memory: total=50925568 free=8644808 WM 09:35:19:978 AWT-EventQueue-0: Updating application time WM 09:35:19:978 AWT-EventQueue-0: New CCP Offset: 803 ms WM 09:35:40:428 JTS-CCPPing-9: Warning: not received heartbeat at 6622000 WM 09:36:18:220 JTS-DeadlockMonitor-1: Memory: total=50925568 free=6607960 WM 09:41:19:680 JTS-DeadlockMonitor-1: Memory: total=50925568 free=6548072 WM 09:45:19:977 AWT-EventQueue-0: Updating application time WM 09:45:19:977 AWT-EventQueue-0: New CCP Offset: 919 ms WM 09:46:20:264 JTS-DeadlockMonitor-1: Memory: total=50925568 free=8735304 WM 09:46:40:032 JTS-CCPPing-9: Warning: not received heartbeat at 7279000 WM 09:51:20:737 JTS-DeadlockMonitor-1: Memory: total=50925568 free=8910984 WM 09:55:19:978 AWT-EventQueue-0: Updating application time WM 09:55:19:978 AWT-EventQueue-0: New CCP Offset: 1034 ms WM 09:56:20:851 JTS-DeadlockMonitor-1: Memory: total=50925568 free=8688936 WM 10:01:21:397 JTS-DeadlockMonitor-1: Memory: total=50925568 free=6413992 WM 10:02:06:757 JTS-CCPPing-9: Warning: not received heartbeat at 8203000 WM 10:05:19:978 AWT-EventQueue-0: Updating application time WM 10:05:19:978 AWT-EventQueue-0: New CCP Offset: 1149 ms WM 10:06:21:508 JTS-DeadlockMonitor-1: Memory: total=50925568 free=8251096 WM 10:11:21:648 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7336144 WM 10:15:20:178 AWT-EventQueue-0: Updating application time WM 10:15:20:178 AWT-EventQueue-0: New CCP Offset: 1064 ms WM 10:16:21:743 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7106320 WM 10:21:22:407 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7469176 WM 10:25:19:978 AWT-EventQueue-0: Updating application time WM 10:25:19:978 AWT-EventQueue-0: New CCP Offset: 1180 ms WM 10:26:22:843 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7145408 WM 10:31:22:936 JTS-DeadlockMonitor-1: Memory: total=50925568 free=6766024 WM 10:35:19:978 AWT-EventQueue-0: Updating application time WM 10:35:19:978 AWT-EventQueue-0: New CCP Offset: 1295 ms WM 10:36:23:094 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7583632 WM 10:40:06:608 JTS-CCPPing-9: Warning: not received heartbeat at 10479000 WM 10:41:23:333 JTS-DeadlockMonitor-1: Memory: total=50925568 free=7343016 WM 10:42:46:721 JTS-CCPPing-9: Warning: not received heartbeat at 10639000 |
Dienstag, 19. Februar 2008, 19:52
Hallo Gerasan,
das hatte ich bisher noch gar nicht bemerkt. Aber ich war erstaunt, was da so ab geht. Und bei mir werden zig Meldungen pro Minute oder sogar pro Sekunde erzeugt.
Tschüß,
Herbert
RD 22:45:55:253 JTS-MDPreAuthPing-44: Starting
RD 22:45:55:748 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:55:748 JTS-usfarmDispatcher-43: Received AUTH_PARAMS
RD 22:45:55:998 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:55:998 JTS-usfarmDispatcher-43: Received SERVER_PARAMS
RD 22:45:57:248 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:57:248 JTS-usfarmDispatcher-43: Received AUTH_RESULT
RD 22:45:57:248 JTS-usfarmDispatcher-43: Passed pwd authentication.
RD 22:45:57:649 JTS-usfarmDispatcher-43: Farm usfarm/mktgw1.ibllc.com/4000/3: Authenticated natively
RD 22:45:57:651 JTS-usfarmDispatcher-43: start ping with 60000 for: JTS-MDPing-46
RD 22:45:57:651 JTS-MDPreAuthPing-44: Terminating
RD 22:45:57:654 JTS-usfarmDispatcher-43: Received MD route table
RD 22:45:57:655 JTS-MDPing-46: Starting
RD 22:45:57:656 AWT-EventQueue-0: Checking market data
RD 22:46:11:337 JTS-CCPDispatcher-14: New CCP Offset: 188 ms
RD 22:46:20:675 AWT-EventQueue-0: SECDEF Sending reqId=FixSecDefReqBySymbol12 symbol=NZD 0 null
RD 22:46:21:003 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol12
RD 22:46:21:005 JTS-CCPDispatcher-14: Checking market data
RD 22:46:21:095 AWT-EventQueue-0: XML Sending query reqId=413 query=144 all mco=39453441 xmlQueryParamPair=null
RD 22:46:21:411 AWT-EventQueue-0: XML Received query response reqId=413
RD 22:46:29:914 AWT-EventQueue-0: Checking market data
RD 22:46:29:916 AWT-EventQueue-0: Sending market data Subscribe 39453441/IDEALPRO/21...
RD 22:46:30:903 AWT-EventQueue-0: Saving factory settings
RD 22:46:30:909 AWT-EventQueue-0: Saving settings to temporary file C:\Jts\djqvwietv\tws.tmp.xml
RD 22:46:31:091 AWT-EventQueue-0: Done saving settings
RD 22:46:43:697 JTS-SocketListener-16: ArEServer: Adding 9478776 with id 0
RD 22:46:43:697 JTS-EServerSocket-51: [0:0:39:1:0:0:0
YS] Starting new conversation with client on localhost/127.0.0.1
RD 22:46:43:698 JTS-EServerSocket-51: [0:37:39:1:0:0:0YS] TWS socket server version is 39
RD 22:46:43:698 JTS-EServerSocket-51: [0:37:39:1:0:0:0YS] Client version is 37
RD 22:46:43:711 JTS-EServerSocket-51: [255281497:37:39:1:0:0:0YS]
RD 22:46:43:816 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol14 symbol=EUR 0 IDEALPRO
RD 22:46:43:818 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol15 symbol=EUR 0 IDEALPRO
RD 22:46:43:819 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol16 symbol=EUR 0 IDEALPRO
RD 22:46:43:820 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol17 symbol=EUR 0 IDEALPRO
RD 22:46:43:821 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol18 symbol=EUR 0 IDEALPRO
RD 22:46:43:822 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol19 symbol=EUR 0 IDEALPRO
RD 22:46:43:823 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol20 symbol=GBP 0 IDEALPRO
RD 22:46:43:825 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol21 symbol=GBP 0 IDEALPRO
RD 22:46:43:826 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol22 symbol=GBP 0 IDEALPRO
RD 22:46:43:827 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol23 symbol=GBP 0 IDEALPRO
RD 22:46:43:828 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol24 symbol=GBP 0 IDEALPRO
RD 22:46:43:829 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol25 symbol=USD 0 IDEALPRO
RD 22:46:43:830 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol26 symbol=USD 0 IDEALPRO
RD 22:46:43:831 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol27 symbol=USD 0 IDEALPRO
RD 22:46:43:832 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol28 symbol=AUD 0 IDEALPRO
RD 22:46:43:833 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol29 symbol=AUD 0 IDEALPRO
RD 22:46:43:834 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol30 symbol=CHF 0 IDEALPRO
RD 22:46:43:835 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol31 symbol=NZD 0 IDEALPRO
RD 22:46:44:008 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol14
RD 22:46:44:010 JTS-CCPDispatcher-14: Checking market data
RD 22:46:44:012 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol15
RD 22:46:44:015 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol16
RD 22:46:44:017 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol17
RD 22:46:44:019 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol18
RD 22:46:44:020 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol19
RD 22:46:44:021 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol20
RD 22:46:44:212 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol21
RD 22:46:44:215 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol22
RD 22:46:44:216 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol23
RD 22:46:44:218 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol24
RD 22:46:44:219 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol25
das hatte ich bisher noch gar nicht bemerkt. Aber ich war erstaunt, was da so ab geht. Und bei mir werden zig Meldungen pro Minute oder sogar pro Sekunde erzeugt.
Tschüß,
Herbert
RD 22:45:55:253 JTS-MDPreAuthPing-44: Starting
RD 22:45:55:748 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:55:748 JTS-usfarmDispatcher-43: Received AUTH_PARAMS
RD 22:45:55:998 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:55:998 JTS-usfarmDispatcher-43: Received SERVER_PARAMS
RD 22:45:57:248 JTS-usfarmDispatcher-43: Received MD auth msg classid = 1
RD 22:45:57:248 JTS-usfarmDispatcher-43: Received AUTH_RESULT
RD 22:45:57:248 JTS-usfarmDispatcher-43: Passed pwd authentication.
RD 22:45:57:649 JTS-usfarmDispatcher-43: Farm usfarm/mktgw1.ibllc.com/4000/3: Authenticated natively
RD 22:45:57:651 JTS-usfarmDispatcher-43: start ping with 60000 for: JTS-MDPing-46
RD 22:45:57:651 JTS-MDPreAuthPing-44: Terminating
RD 22:45:57:654 JTS-usfarmDispatcher-43: Received MD route table
RD 22:45:57:655 JTS-MDPing-46: Starting
RD 22:45:57:656 AWT-EventQueue-0: Checking market data
RD 22:46:11:337 JTS-CCPDispatcher-14: New CCP Offset: 188 ms
RD 22:46:20:675 AWT-EventQueue-0: SECDEF Sending reqId=FixSecDefReqBySymbol12 symbol=NZD 0 null
RD 22:46:21:003 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol12
RD 22:46:21:005 JTS-CCPDispatcher-14: Checking market data
RD 22:46:21:095 AWT-EventQueue-0: XML Sending query reqId=413 query=144 all mco=39453441 xmlQueryParamPair=null
RD 22:46:21:411 AWT-EventQueue-0: XML Received query response reqId=413
RD 22:46:29:914 AWT-EventQueue-0: Checking market data
RD 22:46:29:916 AWT-EventQueue-0: Sending market data Subscribe 39453441/IDEALPRO/21...
RD 22:46:30:903 AWT-EventQueue-0: Saving factory settings
RD 22:46:30:909 AWT-EventQueue-0: Saving settings to temporary file C:\Jts\djqvwietv\tws.tmp.xml
RD 22:46:31:091 AWT-EventQueue-0: Done saving settings
RD 22:46:43:697 JTS-SocketListener-16: ArEServer: Adding 9478776 with id 0
RD 22:46:43:697 JTS-EServerSocket-51: [0:0:39:1:0:0:0
YS] Starting new conversation with client on localhost/127.0.0.1RD 22:46:43:698 JTS-EServerSocket-51: [0:37:39:1:0:0:0
YS] TWS socket server version is 39RD 22:46:43:698 JTS-EServerSocket-51: [0:37:39:1:0:0:0
YS] Client version is 37RD 22:46:43:711 JTS-EServerSocket-51: [255281497:37:39:1:0:0:0
YS] RD 22:46:43:816 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol14 symbol=EUR 0 IDEALPRO
RD 22:46:43:818 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol15 symbol=EUR 0 IDEALPRO
RD 22:46:43:819 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol16 symbol=EUR 0 IDEALPRO
RD 22:46:43:820 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol17 symbol=EUR 0 IDEALPRO
RD 22:46:43:821 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol18 symbol=EUR 0 IDEALPRO
RD 22:46:43:822 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol19 symbol=EUR 0 IDEALPRO
RD 22:46:43:823 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol20 symbol=GBP 0 IDEALPRO
RD 22:46:43:825 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol21 symbol=GBP 0 IDEALPRO
RD 22:46:43:826 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol22 symbol=GBP 0 IDEALPRO
RD 22:46:43:827 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol23 symbol=GBP 0 IDEALPRO
RD 22:46:43:828 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol24 symbol=GBP 0 IDEALPRO
RD 22:46:43:829 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol25 symbol=USD 0 IDEALPRO
RD 22:46:43:830 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol26 symbol=USD 0 IDEALPRO
RD 22:46:43:831 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol27 symbol=USD 0 IDEALPRO
RD 22:46:43:832 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol28 symbol=AUD 0 IDEALPRO
RD 22:46:43:833 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol29 symbol=AUD 0 IDEALPRO
RD 22:46:43:834 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol30 symbol=CHF 0 IDEALPRO
RD 22:46:43:835 JTS-EServerSocket-51: SECDEF Sending reqId=FixSecDefReqBySymbol31 symbol=NZD 0 IDEALPRO
RD 22:46:44:008 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol14
RD 22:46:44:010 JTS-CCPDispatcher-14: Checking market data
RD 22:46:44:012 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol15
RD 22:46:44:015 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol16
RD 22:46:44:017 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol17
RD 22:46:44:019 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol18
RD 22:46:44:020 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol19
RD 22:46:44:021 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol20
RD 22:46:44:212 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol21
RD 22:46:44:215 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol22
RD 22:46:44:216 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol23
RD 22:46:44:218 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol24
RD 22:46:44:219 JTS-CCPDispatcher-14: SECDEF Handling reqId=FixSecDefReqBySymbol25
Donnerstag, 27. März 2008, 19:24
Dieser Thread ist die Fortsetzung zu diesem. Da die Überschrift von dem altem thread überhaupt nicht passte, mache ich hier weiter.
Zunächst einmal danke für dem Tipp:
Diese Einstellung scheint einen Einfluß auf die Verbindung haben. Wie in altem Thread schon berichtet kurzzeitiges ab und wieder einschalten der Flags
behent das Problem das TWS sich alle 5 Minuten reconnected. Siehe Protokolle im alten Thread. Das Problem scheint jedoch nach einer Weile wieder aufzutreten. Z.B. heute habe ich die TWS Protokolle der letzten drei Tage angesehen und entdeckt, das das Problem wieder da ist. Protokolle von jedem Tag seit montag sind voll mit reconnect Meldungen, hier ist ein Auszug:
Nachdem ich im Laufenden Betrieb aber die zwei o.a. Checks ausgeschaltet habe und nach ca. 10-15 Minuten wieder eingeschaltet habe, verschwanden die Verbindungsabbrüche aus dem Protokoll. Es ist unklar wieso die o.a. Investox Einstellungen einen solchen Einfluss auf das "Reconnect" Problem haben, und wie soll man damit umgehen. Ich werde das weiter beobachten. Vielleicht gelingt es mir festzustellen, wann das Problem auftaucht.
Ich habe dabei Investox nicht neu gestartet. Danach sieht das Protokoll sauberer aus bis auf die Warnungen not received heartbeat:
Zunächst einmal danke für dem Tipp:
Zitat
das sieht ja ständiger Neuverbindung aus. Deaktivieren Sie unter Order/Broker/IB die automatische Neuverbindung. Ändert das etwas?
Viele Grüße
Andreas Knöpfel
Diese Einstellung scheint einen Einfluß auf die Verbindung haben. Wie in altem Thread schon berichtet kurzzeitiges ab und wieder einschalten der Flags
Automatisch wieder herstellen nach (Sekunden): 30
Automatische Neuverbindung alle (Minuten): 90
behent das Problem das TWS sich alle 5 Minuten reconnected. Siehe Protokolle im alten Thread. Das Problem scheint jedoch nach einer Weile wieder aufzutreten. Z.B. heute habe ich die TWS Protokolle der letzten drei Tage angesehen und entdeckt, das das Problem wieder da ist. Protokolle von jedem Tag seit montag sind voll mit reconnect Meldungen, hier ist ein Auszug:
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 |
QP 08:56:14:160 JTS-EServerSocket-199: null
QP 08:56:14:160 JTS-EServerSocket-199: ArEServer: Removing 20457864 with id 50209015
QP 08:56:14:160 JTS-EServerSocket-199: Checking market data and cleaning maps
QP 08:56:14:162 JTS-EServerSocket-199: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
QP 08:56:14:172 JTS-SocketListener-14: ArEServer: Adding 21066111 with id 0
QP 08:56:14:172 JTS-EServerSocket-212: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
QP 08:56:14:172 JTS-EServerSocket-212: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
QP 08:56:14:172 JTS-EServerSocket-212: [0:37:39:1:0:0:0:SYS] Client version is 37
QP 08:56:14:173 JTS-EServerSocket-212: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
QP 09:00:35:242 JTS-CCPPing-9: Warning: not received heartbeat at 4526000
QP 09:00:59:117 JTS-DeadlockMonitor-1: Memory:total=60,101KB free=25,296KB
QP 09:01:00:117 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
QP 09:01:00:117 JTS-DeadlockMonitor-1: GC:called=242 times CPU used=0,01%
QP 09:01:00:117 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
QP 09:01:18:874 JTS-EServerSocket-212: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
QP 09:01:18:875 JTS-EServerSocket-212: null
QP 09:01:18:875 JTS-EServerSocket-212: ArEServer: Removing 21066111 with id 50209015
QP 09:01:18:875 JTS-EServerSocket-212: Checking market data and cleaning maps
QP 09:01:18:876 JTS-EServerSocket-212: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
QP 09:01:18:879 JTS-SocketListener-14: ArEServer: Adding 30611371 with id 0
QP 09:01:18:880 JTS-EServerSocket-224: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
QP 09:01:18:880 JTS-EServerSocket-224: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
QP 09:01:18:880 JTS-EServerSocket-224: [0:37:39:1:0:0:0:SYS] Client version is 37
QP 09:01:18:880 JTS-EServerSocket-224: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
QP 09:03:05:262 JTS-CCPPing-9: Warning: not received heartbeat at 4676000
QP 09:05:18:979 JTS-CCPDispatcher-12: New CCP Offset: -752 ms
QP 09:05:19:000 AWT-EventQueue-0: Updating application time
QP 09:05:59:293 JTS-DeadlockMonitor-1: Memory:total=60,101KB free=24,780KB
QP 09:06:00:294 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
QP 09:06:00:294 JTS-DeadlockMonitor-1: GC:called=247 times CPU used=0,01%
QP 09:06:00:294 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
QP 09:06:24:549 JTS-EServerSocket-224: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
QP 09:06:24:550 JTS-EServerSocket-224: null
QP 09:06:24:550 JTS-EServerSocket-224: ArEServer: Removing 30611371 with id 50209015
QP 09:06:24:550 JTS-EServerSocket-224: Checking market data and cleaning maps
QP 09:06:24:551 JTS-EServerSocket-224: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
QP 09:06:24:554 JTS-SocketListener-14: ArEServer: Adding 14143330 with id 0
QP 09:06:24:554 JTS-EServerSocket-236: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
QP 09:06:24:554 JTS-EServerSocket-236: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
QP 09:06:24:554 JTS-EServerSocket-236: [0:37:39:1:0:0:0:SYS] Client version is 37
QP 09:06:24:555 JTS-EServerSocket-236: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
QP 09:10:59:571 JTS-DeadlockMonitor-1: Memory:total=60,101KB free=22,124KB
QP 09:11:00:571 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0,05%
QP 09:11:00:571 JTS-DeadlockMonitor-1: GC:called=260 times CPU used=0,01%
QP 09:11:00:571 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
QP 09:11:31:053 JTS-EServerSocket-236: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
QP 09:11:31:053 JTS-EServerSocket-236: null
|
Nachdem ich im Laufenden Betrieb aber die zwei o.a. Checks ausgeschaltet habe und nach ca. 10-15 Minuten wieder eingeschaltet habe, verschwanden die Verbindungsabbrüche aus dem Protokoll. Es ist unklar wieso die o.a. Investox Einstellungen einen solchen Einfluss auf das "Reconnect" Problem haben, und wie soll man damit umgehen. Ich werde das weiter beobachten. Vielleicht gelingt es mir festzustellen, wann das Problem auftaucht.
Ich habe dabei Investox nicht neu gestartet. Danach sieht das Protokoll sauberer aus bis auf die Warnungen not received heartbeat:
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 |
UY 18:55:22:978 JTS-CCPDispatcher-12: New CCP Offset: -644 ms UY 18:55:23:001 AWT-EventQueue-0: Updating application time UY 18:56:29:330 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=5,958KB UY 18:56:30:333 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,04% 5 min avg=0,04% 1 min avg=0.00% UY 18:56:30:333 JTS-DeadlockMonitor-1: GC:called=1711 times CPU used=0,01% UY 18:56:30:333 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:01:29:501 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=7,913KB UY 19:01:30:502 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,04% 5 min avg=0,01% 1 min avg=0.00% UY 19:01:30:502 JTS-DeadlockMonitor-1: GC:called=1719 times CPU used=0,01% UY 19:01:30:502 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:05:22:979 JTS-CCPDispatcher-12: New CCP Offset: -653 ms UY 19:05:23:000 AWT-EventQueue-0: Updating application time UY 19:06:29:564 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=6,248KB UY 19:06:30:564 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,04% 5 min avg=0,04% 1 min avg=0,05% UY 19:06:30:564 JTS-DeadlockMonitor-1: GC:called=1736 times CPU used=0,01% UY 19:06:30:564 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:11:29:671 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=5,675KB UY 19:11:30:675 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,03% 5 min avg=0.00% 1 min avg=0.00% UY 19:11:30:675 JTS-DeadlockMonitor-1: GC:called=1745 times CPU used=0,01% UY 19:11:30:675 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:15:22:980 JTS-CCPDispatcher-12: New CCP Offset: -663 ms UY 19:15:23:000 AWT-EventQueue-0: Updating application time UY 19:15:23:000 AWT-EventQueue-0: New CCP Offset: -664 ms UY 19:16:29:833 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=8,040KB UY 19:16:30:834 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,02% 5 min avg=0,02% 1 min avg=0.00% UY 19:16:30:834 JTS-DeadlockMonitor-1: GC:called=1761 times CPU used=0,01% UY 19:16:30:834 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:21:31:852 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=8,754KB UY 19:21:32:852 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,02% 5 min avg=0.00% 1 min avg=0.00% UY 19:21:32:853 JTS-DeadlockMonitor-1: GC:called=1770 times CPU used=0,01% UY 19:21:32:853 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:25:22:978 JTS-CCPDispatcher-12: New CCP Offset: -671 ms UY 19:25:23:000 AWT-EventQueue-0: Updating application time UY 19:26:32:686 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=5,577KB UY 19:26:33:688 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,02% 5 min avg=0,07% 1 min avg=0,05% UY 19:26:33:700 JTS-DeadlockMonitor-1: GC:called=1788 times CPU used=0,01% UY 19:26:33:700 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:28:56:670 JTS-CCPPing-9: Warning: not received heartbeat at 42193000 UY 19:31:32:721 JTS-DeadlockMonitor-1: Memory:total=55,575KB free=8,199KB UY 19:31:33:721 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=0,02% 5 min avg=0,02% 1 min avg=0.00% UY 19:31:33:721 JTS-DeadlockMonitor-1: GC:called=1796 times CPU used=0,01% UY 19:31:33:721 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=0.00% 5 min avg=0.00% 1 min avg=0.00% UY 19:31:36:716 JTS-CCPPing-9: Warning: not received heartbeat at 42353000 UY 19:34:26:720 JTS-CCPPing-9: Warning: not received heartbeat at 42523000 |
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »Gerasan« (27. März 2008, 19:50)
Donnerstag, 27. März 2008, 19:48
Auf Anfrage bei IB zu dem Log-Inhalt kam diese Antwort
Diese Warnungen escheinen sporadisch, mal öfters, mal weniger oft. Habt ihr das auch?
If see that your logs contain many instances of blocked heartbeat pings.
The deadlock monitor is nothing to be concerned about, its an internal process.
In regards to the heartbeat pings, there is something on your local network or PC blocking these pings.
Our servers send an heartbeat ping message to your TWS every 10 seconds, if your TWS does not respond within 30 seconds, then your TWS will be disconnected for inactivity. According to your log files, the TWS ping response is being blocked. The most common causes of this are as follows: A possible Firewall or security application blocking the ping. You may have a router connected, routers can be considered a physical hardware firewall. You can bypass the router and connect directly to your modem to test this. Also, the routers have a feature called "Denial of Service Attacks", if this feature is enabled, then it would also block the heartbeat pings, as the router will think someone is attempting to maliciously access your local network.
~Kevin
IB TAC
Diese Warnungen escheinen sporadisch, mal öfters, mal weniger oft. Habt ihr das auch?
Freitag, 28. März 2008, 17:58
Hallo Herbert, danke für die Info,
ich habe jetzt rausgefunden, daß die "zykischen Reconnects" etwas mit der Orderaufgabe zu tun haben. Heute morgen war TWS-Log sauber (keine Reconnects) bis ich eine offene Position im Ordermodul glattstellte. Protokoll InvOrderProt zeigt es. Meine manuelle Aktion begann um 28.03.2008 08:54:43.
ich habe jetzt rausgefunden, daß die "zykischen Reconnects" etwas mit der Orderaufgabe zu tun haben. Heute morgen war TWS-Log sauber (keine Reconnects) bis ich eine offene Position im Ordermodul glattstellte. Protokoll InvOrderProt zeigt es. Meine manuelle Aktion begann um 28.03.2008 08:54:43.
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
ID Group-ID WKN Broker Signaldatum Signalkurs Aufgabedatum Aktuelle Zeit Aktion Ordertyp Anzahl Limit 1 Limit 2 Orderstatus Ausgeführt am Gefillt Restanzahl Letzter Preis Durchschnittspreis Projekt System 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 27.03.2008 19:52:02 Long (Exit Short) Stop-Order 1 K/A 116,74 Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 57 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:01 27.03.2008 19:52:02 Long (Exit Short) Limit-Order 1 114,42 K/A Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 28.03.2008 07:50:00 Long (Exit Short) Stop-Order 1 K/A 116,74 Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 28.03.2008 08:54:45 Long (Exit Short) Stop-Order 1 K/A 116,74 Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 57 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:01 28.03.2008 08:54:45 Long (Exit Short) Limit-Order 1 114,42 K/A Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 28.03.2008 08:54:48 Long (Exit Short) Stop-Order 1 K/A 116,74 Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 57 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:01 28.03.2008 08:54:48 Long (Exit Short) Limit-Order 1 114,42 K/A Aktiv K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 58 0 FGBL1997-Aktuell IB 28.03.2008 08:55:18 115,61 28.03.2008 08:55:17 28.03.2008 08:55:18 Long (Exit Short) Bestens (at market) 1 K/A K/A Unbearbeitet K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 28.03.2008 08:55:18 Long (Exit Short) Stop-Order 1 K/A 116,74 Gestrichen K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 56 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:00 28.03.2008 08:55:18 Long (Exit Short) Stop-Order 1 K/A 116,74 Gestrichen K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 57 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:01 28.03.2008 08:55:19 Long (Exit Short) Limit-Order 1 114,42 K/A Gestrichen K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 57 53 FGBL1997-Aktuell IB K/A K/A 27.03.2008 19:52:01 28.03.2008 08:55:19 Long (Exit Short) Limit-Order 1 114,42 K/A Gestrichen K/A 0 1 K/A K/A PP Renko 123 v0.45 Test IB 58 0 FGBL1997-Aktuell IB 28.03.2008 08:55:18 115,61 28.03.2008 08:55:17 28.03.2008 08:55:19 Long (Exit Short) Bestens (at market) 1 K/A K/A Ausgeführt 28.03.2008 08:55:19 1 0 115,61 115,61 PP Renko 123 v0.45 Test IB 58 0 FGBL1997-Aktuell IB 28.03.2008 08:55:18 115,61 28.03.2008 08:55:17 28.03.2008 08:55:19 Long (Exit Short) Bestens (at market) 1 K/A K/A Ausgeführt 28.03.2008 08:55:19 1 0 115,61 115,61 PP Renko 123 v0.45 Test IB 58 0 FGBL1997-Aktuell IB 28.03.2008 08:55:18 115,61 28.03.2008 08:55:17 28.03.2008 08:55:19 Long (Exit Short) Bestens (at market) 1 K/A K/A Ausgeführt 28.03.2008 08:55:19 1 0 115,61 115,61 PP Renko 123 v0.45 Test IB 58 0 FGBL1997-Aktuell IB 28.03.2008 08:55:18 115,61 28.03.2008 08:55:17 28.03.2008 08:55:19 Long (Exit Short) Bestens (at market) 1 K/A K/A Ausgeführt 28.03.2008 08:55:19 1 0 115,61 115,61 PP Renko 123 v0.45 Test IB |
Freitag, 28. März 2008, 17:58
Genau ab dieser Zeit beginnen die "zykischen Reconnects" im TWS-Log:
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 |
FY 08:30:42:915 JTS-DeadlockMonitor-1: GC:called=198 times CPU used=0,02%
FY 08:30:42:915 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:35:20:996 JTS-CCPDispatcher-12: New CCP Offset: -20 ms
FY 08:35:21:000 AWT-EventQueue-0: Updating application time
FY 08:35:47:915 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=24,882KB
FY 08:35:48:916 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
FY 08:35:48:916 JTS-DeadlockMonitor-1: GC:called=203 times CPU used=0,02%
FY 08:35:48:916 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
FY 08:40:53:925 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=21,753KB
FY 08:40:54:926 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:40:54:926 JTS-DeadlockMonitor-1: GC:called=215 times CPU used=0,02%
FY 08:40:54:926 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:45:20:997 JTS-CCPDispatcher-12: New CCP Offset: 13 ms
FY 08:45:21:001 AWT-EventQueue-0: Updating application time
FY 08:45:59:924 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=23,908KB
FY 08:46:00:924 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:46:00:924 JTS-DeadlockMonitor-1: GC:called=219 times CPU used=0,02%
FY 08:46:00:924 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:50:59:952 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=22,560KB
FY 08:51:00:952 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
FY 08:51:00:952 JTS-DeadlockMonitor-1: GC:called=232 times CPU used=0,02%
FY 08:51:00:952 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=0.00%
FY 08:54:43:569 JTS-SocketListener-14: ArEServer: Adding 7685468 with id 0
FY 08:54:43:569 JTS-EServerSocket-183: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
FY 08:54:43:569 JTS-EServerSocket-183: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
FY 08:54:43:569 JTS-EServerSocket-183: [0:37:39:1:0:0:0:SYS] Client version is 37
FY 08:54:43:572 JTS-EServerSocket-183: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
FY 08:54:48:761 JTS-EServerSocket-183: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
FY 08:54:48:762 JTS-EServerSocket-183: null
FY 08:54:48:762 JTS-EServerSocket-183: ArEServer: Removing 7685468 with id 50209015
FY 08:54:48:762 JTS-EServerSocket-183: Checking market data and cleaning maps
FY 08:54:48:765 JTS-EServerSocket-183: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
FY 08:54:48:769 JTS-SocketListener-14: ArEServer: Adding 14508823 with id 0
FY 08:54:48:770 JTS-EServerSocket-185: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
FY 08:54:48:770 JTS-EServerSocket-185: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
FY 08:54:48:770 JTS-EServerSocket-185: [0:37:39:1:0:0:0:SYS] Client version is 37
FY 08:54:48:770 JTS-EServerSocket-185: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
FY 08:55:18:248 JTS-EServerSocket-185: SECDEF Sending reqId=FixSecDefReqBySymbol181 symbol=GBL 0 DTB
FY 08:55:18:797 JTS-CCPDispatcher-12: SECDEF Handling reqId=FixSecDefReqBySymbol181
FY 08:55:19:409 JTS-CCPDispatcher-12: New CCP Offset: 636 ms
FY 08:55:21:587 AWT-EventQueue-0: Updating application time
FY 08:55:21:587 AWT-EventQueue-0: New CCP Offset: 48 ms
FY 08:55:24:435 AWT-EventQueue-0: saveDailyCommision
FY 08:55:28:410 AWT-EventQueue-0: Checking market data and cleaning maps
FY 08:55:28:910 JTS-Fuse-bomb2-189: Checking market data and cleaning maps
FY 08:55:49:256 AWT-EventQueue-0: Checking market data and cleaning maps
FY 08:55:49:757 JTS-Fuse-bomb2-192: Checking market data and cleaning maps
FY 08:55:56:781 AWT-EventQueue-0: Checking market data
FY 08:55:58:492 AWT-EventQueue-0: Checking market data
FY 08:56:00:096 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=21,280KB
FY 08:56:01:096 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:56:01:096 JTS-DeadlockMonitor-1: GC:called=238 times CPU used=0,02%
FY 08:56:01:096 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 08:59:53:596 JTS-EServerSocket-185: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
FY 08:59:53:597 JTS-EServerSocket-185: null
FY 08:59:53:597 JTS-EServerSocket-185: ArEServer: Removing 14508823 with id 50209015
FY 08:59:53:597 JTS-EServerSocket-185: Checking market data and cleaning maps
FY 08:59:53:598 JTS-EServerSocket-185: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
FY 08:59:53:602 JTS-SocketListener-14: ArEServer: Adding 29996779 with id 0
FY 08:59:53:602 JTS-EServerSocket-205: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
FY 08:59:53:602 JTS-EServerSocket-205: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
FY 08:59:53:602 JTS-EServerSocket-205: [0:37:39:1:0:0:0:SYS] Client version is 37
FY 08:59:53:603 JTS-EServerSocket-205: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
FY 08:59:53:605 JTS-EServerSocket-205: Received live order with filled status
FY 09:01:06:105 JTS-DeadlockMonitor-1: Memory:total=59,904KB free=21,051KB
FY 09:01:07:105 JTS-DeadlockMonitor-1: CPU:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 09:01:07:105 JTS-DeadlockMonitor-1: GC:called=253 times CPU used=0,01%
FY 09:01:07:105 JTS-DeadlockMonitor-1: Finalizer:cur=0.00% avg=?% 30 min avg=?% 5 min avg=?% 1 min avg=?%
FY 09:04:59:749 JTS-EServerSocket-205: [50209015:37:39:1:0:0:0:SYS] Client{50209015} terminated conversation.
FY 09:04:59:749 JTS-EServerSocket-205: null
FY 09:04:59:749 JTS-EServerSocket-205: ArEServer: Removing 29996779 with id 50209015
FY 09:04:59:749 JTS-EServerSocket-205: Checking market data and cleaning maps
FY 09:04:59:750 JTS-EServerSocket-205: [50209015:37:39:1:0:0:0:SYS] Ending conversation with client{50209015} at 127.0.0.1/127.0.0.1
FY 09:04:59:761 JTS-SocketListener-14: ArEServer: Adding 33379524 with id 0
FY 09:04:59:761 JTS-EServerSocket-217: [0:0:39:1:0:0:0:SYS] Starting new conversation with client on 127.0.0.1/127.0.0.1
FY 09:04:59:761 JTS-EServerSocket-217: [0:37:39:1:0:0:0:SYS] TWS socket server version is 39
FY 09:04:59:761 JTS-EServerSocket-217: [0:37:39:1:0:0:0:SYS] Client version is 37
FY 09:04:59:762 JTS-EServerSocket-217: [50209015:37:39:1:0:0:0:SYS] Client ID is 50209015
FY 09:04:59:764 JTS-EServerSocket-217: Received live order with filled status
FY 09:05:20:996 JTS-CCPDispatcher-12: New CCP Offset: 82 ms
|