开云体育

My tws version is 1028, it logoffs itself daily instead of restarting it, it there any setting in config.ini yo deal with it?

I encounter this error when running start_tws.bat, any idea? 2024-04-03 17:02:49:625 IBC: Starting TWS java.lang.reflect.InaccessibleObjectException: Unable to make private static javax.swing.UIManager$LAFState javax.swing.UIManager.getLAFState() accessible: module java.desktop does not "opens javax.swing" to unnamed module @3ba9ad43 at java.base/java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:388) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:364) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:312) at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:203) at java.base/java.lang.reflect.Method.setAccessible(Method.java:197) at feature.search.recorder.JtsMultiLookAndFeel.a(JtsMultiLookAndFeel.java:107) at twslaunch.jclient.login.a.d(a.java:429) at twslaunch.jclient.login.l.a(l.java:450) at jclient.LoginFrame.main(LoginFrame.java:454) at ibcalpha.ibc.IbcTws.startTws(Unknown Source) at ibcalpha.ibc.IbcTws.startTwsOrGateway(Unknown Source) at ibcalpha.ibc.IbcTws.load(Unknown Source) at ibcalpha.ibc.IbcTws.main(Unknown Source)

Hi Richard - hope you are well. Everything working smoothly with the help of IBC on my dual setup until yesterday, and I can still connect to the paper account using the ib_insync API. For the live account I am getting timeout errors. Not sure if its an ibc issue but I thought I would check here first in case there is anything obvious in the ibc log files explaining the failure with the live account. Thanks

Hi I am able to login with paper trading. Now I went to config.ini file and changed TradingMode=live instead of 'paper'. Didn't change anything else. Login is the same for paper and live. But when I run StartTWS, it is still open paper trading in TWS, not live account. Please help. Thanks.

Hi All, I am getting the above error message when trying to execute "StartTWS.bat" using Windows 10 and 11. Do I need to set a PATH setting? See attached logfile Thanks.

Been using IBC for months with no issues. Suddenly one day it just stops working. Open the file and TWS loads, then...nothing. Doesn't autofill. Restarted the computer, tried moving from 10.23 to 10.25 and still nothing. Any suggestions? Thanks Logs below ================================================================================ ================================================================================ This log file is located at: C:\IBC\Logs\IBC-3.16.0_TWS-1023_THURSDAY.txt ================================================================================ Starting IBC version 3.16.0 on Thu 11/02/2023 at 21:50:38.92 Operating system: Microsoft Windows Server 2019 Standard 64-bit 10.0.17763 Arguments: TWS version = 1023 Program = TWS Entry point = ibcalpha.ibc.IbcTws /TwsPath = C:\Jts /TwsSettingsPath = /IbcPath = C:\IBC /Config = C:\Users\admin\Documents\IBC\config.ini /Mode = /JavaPath = /User = /PW = /FIXUser = /FIXPW = ================================= Generating the classpath Classpath=C:\Jts\1023\jars\jackson-core-2.12.3.jar;C:\Jts\1023\jars\jts4launch-1023.jar;C:\Jts\1023\jars\jxbrowser-7.29.jar;C:\Jts\1023\jars\jxbrowser-swing-7.29.jar;C:\Jts\1023\jars\jxbrowser-win64-7.29.jar;C:\Jts\1023\jars\locales.jar;C:\Jts\1023\jars\log4j-api-2.17.1.jar;C:\Jts\1023\jars\log4j-core-2.17.1.jar;C:\Jts\1023\jars\total-2020.jar;C:\Jts\1023\jars\twslaunch-1023.jar;C:\Jts\1023\jars\twslaunch-install4j-1.12.jar;C:\Jts\1023\.install4j\i4jruntime.jar;C:\IBC\IBC.jar Generating the JAVA VM options Java VM Options= -Xmx768m -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=20 -XX:ConcGCThreads=5 -XX:InitiatingHeapOccupancyPercent=70 -Dinstaller.uuid=8bcf9c60-dfac-403b-822f-d1cd33b9d908 -DvmOptionsPath=C:\Jts\1023\tws.vmoptions -Dsun.awt.nopixfmt=true -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Dtwslaunch.autoupdate.serviceImpl=com.ib.tws.twslaunch.install4j.Install4jAutoUpdateService -Dchannel=latest -Dexe4j.isInstall4j=true -Dinstall4jType=standalone -DjtsConfigDir=C:\Jts Finding autorestart file autorestart file found at C:\Jts\1023\iajkokhhkfokpbefffeopnfbopjjbaikdonojggf\autorestart AUTORESTART_OPTION is -Drestart=iajkokhhkfokpbefffeopnfbopjjbaikdonojggf Determining the location of java.exe Location of java.exe=c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin Renaming TWS or Gateway .exe file to prevent restart without IBC . Starting IBC with this command: "c:\users\admin\appdata\roaming\i4j_jres\oda-jk0qgtemvssflllp\1.8.0_202_64\bin\java.exe" -cp "C:\Jts\1023\jars\jackson-core-2.12.3.jar;C:\Jts\1023\jars\jts4launch-1023.jar;C:\Jts\1023\jars\jxbrowser-7.29.jar;C:\Jts\1023\jars\jxbrowser-swing-7.29.jar;C:\Jts\1023\jars\jxbrowser-win64-7.29.jar;C:\Jts\1023\jars\locales.jar;C:\Jts\1023\jars\log4j-api-2.17.1.jar;C:\Jts\1023\jars\log4j-core-2.17.1.jar;C:\Jts\1023\jars\total-2020.jar;C:\Jts\1023\jars\twslaunch-1023.jar;C:\Jts\1023\jars\twslaunch-install4j-1.12.jar;C:\Jts\1023\.install4j\i4jruntime.jar;C:\IBC\IBC.jar" -Xmx768m -XX:+UseG1GC -XX:MaxGCPauseMillis=200 -XX:ParallelGCThreads=20 -XX:ConcGCThreads=5 -XX:InitiatingHeapOccupancyPercent=70 -Dinstaller.uuid=8bcf9c60-dfac-403b-822f-d1cd33b9d908 -DvmOptionsPath=C:\Jts\1023\tws.vmoptions -Dsun.awt.nopixfmt=true -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Dtwslaunch.autoupdate.serviceImpl=com.ib.tws.twslaunch.install4j.Install4jAutoUpdateService -Dchannel=latest -Dexe4j.isInstall4j=true -Dinstall4jType=standalone -DjtsConfigDir=C:\Jts -Drestart=iajkokhhkfokpbefffeopnfbopjjbaikdonojggf ibcalpha.ibc.IbcTws "C:\Users\admin\Documents\IBC\config.ini" IBC Settings: AcceptBidAskLastSizeDisplayUpdateNotification= AcceptIncomingConnectionAction=reject AcceptNonBrokerageAccountWarning=no AllowBlindTrading=no AutoLogoffTime= AutoRestartTime= BindAddress= ClosedownAt= CommandPrompt= CommandServerPort=0 ConfirmCryptoCurrencyOrders=manual ControlFrom= DismissNSEComplianceNotice=yes DismissPasswordExpiryWarning=no ExistingSessionDetectedAction=manual ExitAfterSecondFactorAuth

Hi, I'm sure this is pretty low on the list of priorities in the grand scheme of things, but I notice that we end up with several TWS "Tooltips" windows that only contain the text "N/A". Those are completely useless, and they don't disappear like regular Windows tooltips; they just hang around until one manually closes them. I was wondering if IBC could close these windows automatically as soon as they show up. They offer no useful information, and just clutter up the many windows we have open. Thanks Jimmy

During development of an automated trading engine, I've experienced an interesting situation: - using dockerized IB gateway+IBC I could connect from my client python software (using client ID 0) with no problem - many times I stopped and restarted the Docker containers for development triggering a new auth flow - suddenly on Friday I could no longer connect: my Python client was always disconnected. Error msg in IBGW logs: "client ID 0 already connected". However no other client was connected - Interestingly when running IBGW direct, outside Docker, I was able to connect. - today, after the weekly Sat system reset, I am again able to connect with no issue with the dockerized setup. No change was made to the code. Any insights on what may have caused this? Seems there may be a limit at IB of how many times a client can connect to an IBGW instance with a certain fingerprint (as it still worked when running IBGW outside Docker) until they do the weekly system reset?

Hi! I have started to get this error message after a couple of hours up time: /root/ibc/scripts/ibcstart.sh: line 504: 28 Killed "$java_path/java" -cp "$ibc_classpath" $java_vm_options$autorestart_option $entry_point "$ibc_ini" "$ib_user_id" "$ib_password" ${mode} IBC returned exit status 137 autorestart file not found Gateway finished The same environment has been running smoothly for months up until yesterday with: TWS version 10.19.2c IBC version 3.18.0 Any pointers or idees on what's going on?

Hi Richard, IBC Gateway had been working until this morning. However, now it does not populate the username and password fields and log in. It was a problem that I encountered when using Gateway 1023, so I stuck with 1019. It now seems to work for neither. I have attempted to fix it by updating to the latest IBC version, however the problem persists. I realise this seems to be a common issue, one that I have solved in the past deploying various fixes, but it seems to persist for me at the moment. I attach two log files; one for each gateway version. Thanks, Alistair

Hello There, I was reading the guide for IBC and there is specified that is possible to have the 2 factor authentication login request only once a week. I am running TWS 1022 and I have set the auto-restart at 10:15 pm, also im running on windows the scheduled task that should restart IBC every day (the one that is also included with the IBC windows version) My question is, to have to accept only once a week the 2 factor notification... I should use the included TWS auto-restart or the scehduled task or both of them? Thanks, Federico

Hi, I am new to IBC, and I am trying to install IBC and run IBC. I'm running this on Linux Mint 21.1. I'll state what I did so far below: 1) Firstly, I've installed the TWS Offline stable 10.19.2a version from Interactive Brokers and installed it. 2) I've followed the IBC user guide and done the following: i) Downloaded IBCLinux-3.18.0.zip from Github ii) Typed the following commands in terminal as described in the user guide sudo unzip ~/Downloads/IBCLinux-3.6.0.zip -d \ /opt/ibc cd /opt/ibc sudo chmod o+x *.sh */*.sh iii) Copied a copy of config.ini from /opt/ibc to ~/ibc and changed the IbLoginID, Password, and TradingMode 3) After which, I've typed the following command into the terminal: cd /opt/ibc sh gatewaystart.sh Both sh twsstart.sh and sh gatewaystart.sh gives the following error: """ twsstart.sh: 181: [[: not found twsstart.sh: 183: [[: not found -e Error: no execute permission for scripts in /opt/ibc/scripts """ """ gatewaystart.sh: 193: [[: not found gatewaystart.sh: 195: [[: not found -e Error: no execute permission for scripts in /opt/ibc/scripts """ I'm rather stuck now, am I missing something with the execute permission with the two files in/opt/ibc/scripts? I would think that 'sudo chmod o+x *.sh */*.sh' would have already given the execute permission to both of these files? Or is there something to do with noexec? Many thanks for your time and love to learn more about this. - Ong

I’ve just released version 3.18.0 of IBC. You can get it from here: https://github.com/IbcAlpha/IBC/releases/tag/3.18.0 This Release introduces the ability to configure the API-Precautions settings in TWS and Gateway via new settings in config.ini. This is in response to issue #222 in the GitHub repository. These new settings are described in the API Precautions section of config.ini, and are as follows. See the notes in config.ini for further details: BypassOrderPrecautions BypassBondWarning BypassNegativeYieldToWorstConfirmation BypassCalledBondWarning BypassSameActionPairTradeWarning BypassPriceBasedVolatilityRiskWarning BypassUSStocksMarketDataInSharesWarning BypassRedirectOrderWarning BypassNoOverfillProtectionPrecaution These settings are intended for use in situations where the TWS/Gateway user interface is not easily accessible or where TWS/Gateway settings are not persisted between sessions, as happens with some Docker images. The Release also contains some minor IBC code improvements: see the commit history for details. If you do not need to use these new settings, it is not necessary to upgrade to this Release. To upgrade an existing installation, extract the IBC.jar and version files from the .zip file and overwrite the existing versions. Update your config.ini with the new API Precautions section from the config.ini file in the .zip. Richard

I’ve just released version 3.17.0-update.1 of IBC, which you can get here: https://github.com/IbcAlpha/IBC/releases/tag/3.17.0-update.1 This Release is a Windows-only update that fixes a couple of bugs in the start script for IBC. There are no changes to IBC's functionality. Fixes a problem on Windows where installing a new update of an already-installed TWS or Gateway prevents autorestart from succeeding Fixes a problem on Windows where using double backslashes in the TWS_SETTINGS_PATH prevents autorestart from succeeding. Windows users who have already installed IBC 3.17.0 should extract the StartIBC.bat file from the Scripts folder in the Windows .zip file to replace the existing file in the IBC\Scripts subfolder. Also extract the version file to replace the existing one in the IBC folder. Windows users wishing to install IBC 3.17.0 for the first time should do so using the .zip file from the IBC 3.17.0 release, and then update the files from this release as described above. Linux and macOS users should ignore this release. Richard

Hi, I was happily running TWS 1023.? (or something close) and TWS popped up a message saying that my version had to be upgraded because it would lose support on July 7. I dutifully upgraded to TWS 10.23.2a, and was able to log in fine without changes to my config.ini file. But I notice that now TWS will not auto-login during the week and requires my password 2FA every day. I have not investigated it at length; I just authenticate the normal way since I am sitting in front of the machine. Could anyone hazard a guess what is going on? My TWS 'auto restart' is correctly set in the TWS options. I want to believe that this new behavior has nothing to do with IBC... :-)