Synchronization issue with shared DataSinks
We are experiencing reproducible failures when using a shared [tt:2hywipcn]DataSink[/tt:2hywipcn] for our load tests.
The [tt:2hywipcn]DataSink[/tt:2hywipcn] writes various properties generated in previous steps (by Groovy scripts) and a [tt:2hywipcn]DataSource[/tt:2hywipcn] property to a CSV file (sothat we can identify what test data has been generated).
In most of the cases (up to 10 threads and 20 seconds it seems to work, but with more threads or longer running time we always get a failure) at the end of our test (we cannot say for sure because logging is disabled during load tests), the DataSink step fails with no further information on why.
The [tt:2hywipcn]DataSink[/tt:2hywipcn] is shared among working Threads, because we want one big CSV with all test ID's we generate, so we suspect it's a synchronization issue and writing to the file or closing the file is not well synchronized among the soapUI worker threads.
The file seems to be OK, so it is probably only a problem when closing the file - e.g., one Thread tries to close it but it is already closed so we get an IOException.
This bug in the [tt:2hywipcn]DataSink[/tt:2hywipcn] makes it hard for us to automatically detect whether the test has passed or not, we need a fix for this issue.
The [tt:2hywipcn]DataSink[/tt:2hywipcn] writes various properties generated in previous steps (by Groovy scripts) and a [tt:2hywipcn]DataSource[/tt:2hywipcn] property to a CSV file (sothat we can identify what test data has been generated).
In most of the cases (up to 10 threads and 20 seconds it seems to work, but with more threads or longer running time we always get a failure) at the end of our test (we cannot say for sure because logging is disabled during load tests), the DataSink step fails with no further information on why.
The [tt:2hywipcn]DataSink[/tt:2hywipcn] is shared among working Threads, because we want one big CSV with all test ID's we generate, so we suspect it's a synchronization issue and writing to the file or closing the file is not well synchronized among the soapUI worker threads.
The file seems to be OK, so it is probably only a problem when closing the file - e.g., one Thread tries to close it but it is already closed so we get an IOException.
This bug in the [tt:2hywipcn]DataSink[/tt:2hywipcn] makes it hard for us to automatically detect whether the test has passed or not, we need a fix for this issue.
