Ports

ants

I am not sure this is a bug so have posted it here. When you run an app using the TCPServer, say the MyServer example, and you use a fixed port, the first time it works fine. If you stop and restart the app then you are unable to access the server. If you use the random port option then it works every time but obviously the port changes. Its as if the port is not released after the server stops so running using a new port is okay. I have attempted to add the server.Stop() function when the server is closed down but it makes no difference.

ants

Also closing Objo down and restarting seems to release the port so it works again, once.

madamov

ants I know @Garry will ask this too probably, but how I read this is that you are running your app from Objo Studio by clicking on the Run button, not by building the application and running it directly from operating system?

Garry

Thanks for the clear report and @madamov's question was exactly the right one.

This is a genuine bug, and I've reproduced it. When you run a console project with Studio's Run button, the app executes inside the Studio process itself. When you press Stop, the interpreter stops, but the TCP listener your app created isn't being closed. This means the port stays bound by Studio until you quit Studio entirely. That explains everything you saw:

The first Run works, but the second can't get the port - it's still held by the previous run's listener inside Studio.
Random ports (Port = 0) work every time, because each run gets a fresh port from the OS.
Quitting and relaunching Studio frees the port and it works again - exactly once.
Calling server.Stop() makes no difference, because pressing Stop ends execution without running your app's own shutdown code.

Launching the built app directly (Build, then run it from Finder or the terminal) won't hit this, since the app is its own process and the OS reclaims its ports when it exits.

A fix is on the tracker: sockets (TCPServer and friends) will release their ports and connections when a run stops. In the meantime, the workarounds are the ones you've found - relaunch Studio to free the port, or test against a built copy of the app.

https://feedback.objo.dev/bug/1662

ants

I had tried doing a build and running it and this works with a fixed port as long as you don't test from the studio first because that locks out the port. The build option also frees up the port when you shut down and restart, I guess like studio.

Garry

Fixed in the next release.