Fix Port Binding Issue During Testing

[neeetman]

This PR addresses the issue where tests would fail if the designated port was already in use.

[INFO ] 2023-10-25 07:18:47,185 [main]  com.oltpbenchmark.benchmarks.resourcestresser.TestResourceStresserBenchmark setUp - starting HSQLDB server for test [testGetTransactionType] on port [9099]
[Server@191774d6]: [Thread[HSQLDB Server @191774d6,5,main]]: run()/openServerSocket(): 
java.net.BindException: Address already in use

Changes:

• Modified the setUp method in TestResourceStresserBenchmark class.
• Added logic to try different ports using ServerSocket to find an available port.
• The system will attempt up to MAX_TRIES to find an open port before throwing an exception.
• The the system will make a thorough effort in finding an available port.

[apavlo]

@neeetman What problem is this trying to solve in testing? If the port is in use, then the test environment is wrong not the code.

[neeetman]

@neeetman What problem is this trying to solve in testing? If the port is in use, then the test environment is wrong not the code.

Each test requires applying for a new port. However, sometimes other services running on the server might already be occupying that port. It might be better to consider skipping the occupied ports instead of directly terminating the test with an error.

[bpkroth]

LGTM. Minor tweak suggested.

[bpkroth]

@neeetman, just noticed you closed this before merging. Any particular reason?

[neeetman]

@neeetman, just noticed you closed this before merging. Any particular reason?

Sorry, I previously noticed that 'Some checks were not successful,' so I closed it.

[bpkroth]

@neeetman, just noticed you closed this before merging. Any particular reason?

Sorry, I previously noticed that 'Some checks were not successful,' so I closed it.

Ah, for future, just ping back about that. Happy to help look into those.

That one looks spurious. Seems to have failed in the nightly run a few times as well, so probably needs separate investigation. I'll file an issue on that one and follow up separately.

#405