Thread Safety issues in Mock Service as WAR
I am working with a client and was hoping to propose the use of SoapUI v3.6.1 mock services as a viable alternative to hand coded mock services. They use these mock services to provide stubs for back...
Forum Discussion
Ole,
Thanks... we'll check out the next nightly and give you some feedback on that tomorrow.
Another suggestion though, it might be more ideal to allow the user to just turn off the "request" tracking feature completely via the web.xml. In this particular case we're using the mock service to fake a backend system so we can do load testing against our service consumer which sits in front of it. During load testing we'd never want to track requests. We'd want the mock to be as fast as possible so that we're measuring the performance of our code, not the limitations of the mock. Adding a synchronization block in there is going to hamper the mock's performance.
Again, I appreciate your attention to this particular issue.
Thanks... we'll check out the next nightly and give you some feedback on that tomorrow.
Another suggestion though, it might be more ideal to allow the user to just turn off the "request" tracking feature completely via the web.xml. In this particular case we're using the mock service to fake a backend system so we can do load testing against our service consumer which sits in front of it. During load testing we'd never want to track requests. We'd want the mock to be as fast as possible so that we're measuring the performance of our code, not the limitations of the mock. Adding a synchronization block in there is going to hamper the mock's performance.
Again, I appreciate your attention to this particular issue.