thanks for pointing out your issue. I'm wondering if they aren't related in some way. In my case the code was working fine up until 12/16/22. Calls to historical work as expected BUT calls to reqMktData fail instantly. I'll go back and review my approach as you suggested but I am loathe to do so as it seems the most rational one. Submit all the symbols with an ID and unique identifier reqMktData to an asynch process and then wrapper the callbacks and handle them as they come in.

I'm considering wireshark as a last resort as I am confident that the protocol stack is working. This smacks to me of application level failure.

thanks again for you heads up on the bug.

Well, if you're seeing the same problem with a basic test case across different language APIs, I'd consider reaching for the usual tools like wireshark, strace to troubleshoot further. And, if the problem isn't with just your local configuration... I'm sure it will be confirmed by others [eventually] and probably fixed [at some point] by IB.

Otherwise, I personally, would consider some kind of creative workaround.

Again, good luck! Please keep us posted.

开云体育

As I said, I am asking for the forum's guidance in two regards:

1 has anyone else experienced IO issues since 12/16/22 ?

2 has the forum got any guidance as to how to resolve TCPIp type issues with TWS.?

?ANY help would be great setting up the debugging toolkit IRRESPECTIVE of language or api which are not relevant in this thread.

On Wed, Dec 21, 2022 at 06:13 PM, comicpilsen wrote:

this isn't a julia problem it's a TWS issue

You sound pretty sure of this so I'm guessing you must've confirmed the same thing is happening when you create a simple test case using one of the officially supported API/SDKs too... yes?

Anyway, wish I could help more but I'm still using the 9.x branch due to bug introduced in 10.x (specific to my own usage). Therefore... haven't seen the problem you're experiencing with Jib or exporting diags.

Good luck.

this isn't a julia problem it's a TWS issue and yes I they have helped me A LOT to narrow the cause down to the IO subsystem.

I'm asking if anyone else has noticed if TWS tcpip IO has been playing up recently. I am NOT asking for code support. Right now I am "TRYING" to use the TWS logs for the first time. What would be GREAT is that if anyone knows how to look at them remotely. I use Linux and not having any luck with the diagnostics on the TWS desktop. I try to export them but it just hangs.

Uhhh.... this sounds like a problem w/ Jib. Have you reached out to ?

Just started getting these "broken pipe" messages in code that's been working for months. Anyone know how to diagnose TWS socket issues like broken pipes. I don't even know which log to look at!!!

this code has been working for about 3 months without fault so this behavior started 12/16/22. NOW it just fails on the first call to reqMktData

I checked the HELP for the TWS desktop I am using as a gateway and the build is 10.20.1f 12/13/22 so it's NOT pacing problems. I know the connection is working because I have TWS desktop running as my gateway api and I can see the DATA indicator is consistently GREEN. I monitor the ISP feed ( 1GB/s) using a raspberry pi and that seems ok. I'm working on how to look at the TWS logs to see if they tell me anything.

┌ Warning: connection terminated
└ @ Jib.Reader ~/.julia/packages/Jib/JOmEj/src/reader.jl:70
[ Info: reader exiting
ERROR: LoadError: IOError: write: broken pipe (EPIPE)
Stacktrace:
  [1] uv_write(s::Sockets.TCPSocket, p::Ptr{UInt8}, n::UInt64)
    @ Base ./stream.jl:1064
  [2] unsafe_write(s::Sockets.TCPSocket, p::Ptr{UInt8}, n::UInt64)
    @ Base ./stream.jl:1118
  [3] unsafe_write
    @ ./io.jl:683 [inlined]
  [4] write
    @ ./io.jl:706 [inlined]
  [5] write_one(socket::Sockets.TCPSocket, buf::IOBuffer)
    @ Jib.Client ~/.julia/packages/Jib/JOmEj/src/client.jl:28
  [6] sendmsg

what is REALLY weird, other than the fact this JUST broke a few days ago, is that it ONLY happens with reqMktData whereas reqHistoricalData works fine.

for (idx, s) in enumerate(eachrow(symbol_list))

    contract = Contract(symbol=s.Sym, secType="STK" , exchange=s.exchange , currency="USD")
    reqMktData(ib, idx, contract,"106", false) # https://interactivebrokers.github.io/tws-api/tick_types.html
end

BUT this one works properly. They both share the same ZMQ configuration code and worked fine up until 12/16/22.

for (idx, s) in enumerate(eachrow(symbol_list))
  sleep(5)
    contract = Contract(symbol=s.Sym, secType="STK" , exchange=s.exchange , currency="USD")
  try
       reqHistoricalData(ib, idx ,contract,"","1 Y","1 day","TRADES",true,1,false )
  
  catch e
           println("something went wrong with : " , s.Sym)
           stk_send_msg = "STK" *  "~" * s.Sy * "~" * "CLOSE" * "~" * string( 999 ) #show there was an error
           ZMQ.send( stk_socket, stk_send_msg )
           continue
  end
end

开云体育

I looked at that before posting and the "export diagnostics" just sat there for about an hour. Is there no other way to look at the logs?

开云体育

I did look at this before asking but when I ran the "export diagnostics" it just sat there for about an hour. How do you use this system please??

Doing this via GUI is rather easy... select the menu option ACCOUNT, DIAGNOSTICS, then TWS Logs. It should be somewhat self explanatory from there.

Hi all never had to look at TWS logs before but now I need to. The issue is that I have NO idea how to do this. I am running a tws desktop on a linux laptop which I can access the drive on BUT I have No idea what I am looking for. I thought I could get the name of the api log file from the launcher but no luck.

2022-12-20 21:00:21.540 [SA] INFO  [JTS-PostAuthenticateS2-19] - performLogSwitch() [force=false]
2022-12-20 21:00:21.657 [SA] INFO  [JTS-PostAuthenticateS2-19] - Switching to a new encrypted log..

So what's the way to FIND the file and how can I view it please? If I have to DECRYPT it how do I go about doing that. thanks for any help