Port parameter passed in as string leads to misleading error

[rlindner81]

I just came across some really odd behavior with version 2.0.0. We pass in a port parameter from the commandline, so it ends up being a string, which used to work fine in previous connect versions.

Now, we get a

Fatal error: Port 1234 is already in use by another process.

which is both wrong and misleading. If I pass in the same variable as Number the behavior is as expected.

[vekonypeter]

I experienced the same. It could be ok, to throw an error, when the port number is not Number typed, but the error message is really misleading.