+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-1830

Portfolio Trader fails to re-connect to IB

action_vote_minus_faded.png
1
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

If IB goes down, Portfolio Trader fails to re-connect properly after IB becomes available again.

Steps to reproduce this issue
  • launch IB Gateway
  • launch Portfolio Trader
  • enable auto-trading
  • wait for IB to go down, e.g. during scheduled system maintenance
  • wait for IB to become available again, e.g. after scheduled maintenance
    => Portfolio Trader reports an error in the log and auto-trading will no longer work, even though it still shows enabled.

Exiting and re-starting Portfolio Trader will fix this issue.

Exiting and re-starting IB Gateway does not fix this issue.

System information:
* IB Gateway 948.2b
* Portfolio Trader 9.0.10360.400
* data connection through MB Trading

Comments (1)
#1
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jul 28, 2017 - 12:12
Order and Position Tracker information that you attached will not help in this case, unfortunately.

We have tested it on our end following the provided steps, but it was not reproduced. In case the issue is still reproduced, please send us the Log files, collected via Feedback application: https://www.multicharts.com/trading-software/index.php/MultiCharts_Logs#How_to_Send_Log_Files_Using_Feedback_Application

Specify the time when IB was closed and when it was opened and how do you see that AT is not working exactly?
History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates