[Enhancement][Java Client] Unit Tests fails sometimes

[junw-33455432]

Java Client Unit Test is not stable, it fails on any ubuntu environment which GItHub Actions provided and may fail sometimes in Microsoft Windows enviroment.

[huihuiw01]

@junw-33455432 Please provide the failure details, which cases fail.

[junw-33455432]

@huihuiw01 Please refer to https://github.com/vmware/singleton/actions/runs/6938616428/job/18874632916 , most time the following test case fails
com.vmware.vip.i18n.TranslationMessageTest > testNamedArgs FAILED

[huihuiw01]

I reviewed the failed case, looks like no problem, and can run successfully at my local. Looks like there is something wrong with the ut run environment on github, because the failed case is not fixed, please refer to below link about the same PR's ut result:

https://github.com/vmware/singleton/actions/runs/7329156012/job/19958431397?pr=2940

https://github.com/vmware/singleton/actions/runs/7329156012/job/20117919603?pr=2940

And sometimes the smoke test failed:
https://github.com/huihuiw01/singleton/actions/runs/7329051478/job/19958213989

This issue blocks java client PR merge, @junw-33455432 Could you help take a look again?

[junw-33455432]

I reviewed the failed case, looks like no problem, and can run successfully at my local. Looks like there is something wrong with the ut run environment on github, because the failed case is not fixed, please refer to below link about the same PR's ut result: https://github.com/vmware/singleton/actions/runs/7329156012/job/19958431397?pr=2940

https://github.com/vmware/singleton/actions/runs/7329156012/job/20117919603?pr=2940

And sometimes the smoke test failed: https://github.com/huihuiw01/singleton/actions/runs/7329051478/job/19958213989

The Unit Test/Smoke Test running result seems not stable, to resolve these Unit Test/Smoke Test failures, you just re-run the failure step, it will pass after some re-run. I also tried different type JDK and OS, they have same behavior. If nothing we can do for now, let's leave it as current status as it's not a blocking issue.