Nothing is impossible, Lou, but my money is still on some application (real or defunct) holding the port. And it could simply be the old TWS during restart in case it does not completely terminate.
Next time, use a slightly different option for the netstat command. Use "netstat -qno -p tcp" instead of "netstat -ano -p tcp"
- -a displays all connections and listening ports
- -q? displays all connections, listening ports, and bound nonlistening TCP ports. Bound nonlistening ports may or may not be associated with an active connection.
On my Windows10 laptop, -a shows 88 ports in use, while -q shows 111 ports in use. Each port can only be used once and when some process uses 9707 as a "bound nonlistening port", TWS cannot get it as a listening port.
闯ü谤驳别苍
toggle quoted message
Show quoted text
On Tue, Jul 12, 2022 at 05:33 PM, Lou Dudka wrote:
闯ü谤驳别苍,
OK, so Friday evening 07/08/22 I shut down everything and re-booted.? All times NYC.
I brought up both test and prod TWS.? Everything went fine, as expected, and there were no port conflicts.
Saturday, however, on the auto-reboot at 5:20 pm there was a port "conflict" on the test TWS this time.? I had a problem with prod last time.? "netstat -ano -p tcp " did not reveal any conflicts.
I brought down the test TWS and then up again.? No conflicts.? Both running on same machine.
I've been running with no conflicts ever since (Tuesday 07/12/22) with auto-reboots.
I'm leaning to a problem with TWS/auto-restart, and not a "real" networking port conflict.? I've had sporadic problems with TWS not coming up clean (thread #49333) and/or hanging on auto-restarts (no port conflicts) in the past.?? I've been trying to "watch" the auto-reboot live, but like a watched teapot, it never seems to boil ...
To the best of my knowledge I've changed nothing else (yeah, I know, we've all heard that one, LOL).
闯ü谤驳别苍, if I get another conflict I might take your suggestion to upgrade from 981.? I'm really short on time right now, so it would be a burden.
If all else fails I'll have to hang my head in shame from Richard and re-install IBC "on the sneak" and use Scheduler ... ah, those were the days, absolutely NO problems!
Thanks, as always, and Be Well,
Lou Dudka