Even though I'm not currently running a statement on the server.
The creation of "/files" and "/files_2" contain the statements that block each other I guess.
I'm looking further into this today. Though after every sql statement it seems that all exit paths from the methods are covered and a "close" statement is being called - which should terminate the statement -- assuming that is what "close" is supposed to do. I can't explain why, when the update to /files has fully completed, the next read attempt on /files_2 hangs up. Especially since this is happening serially - not in parallel since it is happening in the same thread.
If you think of freeing locks by "terminate" the answer is "no". Locks are freed upon commit of the whole transaction.
I guess what I'm really after is confirmation of what the correct nodestore configuration is when I want to run multiple scopes/stores as is needed for the testsuite. And I did try running a separate db for each nodestore too, but I get exactly the same problem. Which indicates that the problem isn't localized to sharing a nodestore between stores.
Hard to believe. Do you get it running with only a single store
configured?
Yes. The jdbc config works fine with a single store. Which begs the question: can I disable the portions of the testsuite that require the second and third stores to be configured? How much of the testsuite will I lose if I do this? Preferably I'd like to use as much of the testsuite as possible.
Only very few testcases. You can only actively exclude them from the test run... I would have to look up how this can be done, so I'd recommend to simply let it run.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
