Multi-threading in SoapUI Mock Service
Hello Friends, I'm trying to mock a game management system using SoapUI Mock service. I'm concurrently logging multiple players but the requests are failing due to concurrency exception. Does SoapU...
Forum Discussion
Hi Ole,
Here is the complete information on this issue. I have attached the following files which will help you to reproduce the error.
“Gaming Simulator.xml” : SoapUI project document with Mock Service code along with a test case to test the load
“Message Log of Mock Service.JPG” : This is the exception we are encountering while testing the load on Mock Service.
“Login-Logout Screenshot.JPG” : Even though we are using synchronized block of code, multiple threads are executing the synchronized code simultaneously. We have included log.info messages to trace this and as you can see in the bottom of the picture, “Login inside” string is displayed twice continuously which makes it evident that concurrency is not handled properly even through we are using synchronized block of code
"Error Log.txt" : Has the stack trace of the exception we are getting in "error log"
Thank you for your support and any pointers to resolve this issue would be of great help!
Thanks,
Arun
Here is the complete information on this issue. I have attached the following files which will help you to reproduce the error.
“Gaming Simulator.xml” : SoapUI project document with Mock Service code along with a test case to test the load
“Message Log of Mock Service.JPG” : This is the exception we are encountering while testing the load on Mock Service.
“Login-Logout Screenshot.JPG” : Even though we are using synchronized block of code, multiple threads are executing the synchronized code simultaneously. We have included log.info messages to trace this and as you can see in the bottom of the picture, “Login inside” string is displayed twice continuously which makes it evident that concurrency is not handled properly even through we are using synchronized block of code
"Error Log.txt" : Has the stack trace of the exception we are getting in "error log"
Thank you for your support and any pointers to resolve this issue would be of great help!
Thanks,
Arun
