From: SourceForge.net <no...@so...> - 2008-04-11 16:37:26
|
Bugs item #1940340, was opened at 2008-04-11 16:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=117691&aid=1940340&group_id=17691 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Gregory (grosensteel) Assigned to: Nobody/Anonymous (nobody) Summary: Query concurrency issue using SOAP api Initial Comment: Exist Version: 1.2.0 rev 7233 Problem Description: While running 2 concurrent xquery transactions through one user's session using the SOAP api, the results get mismatched (one xquery transaction gets the second xquery transaction's results) Procedure: 1. Setup 2 threads, where each thread will repeatedly run the same query and report the query in conjunction with the result. 2. Run both threads simultaneously against the exist database 3. Take a look at one thread. Notice that the query result is sometimes the result from the other thread's execution. Question: Does exists support concurrent xquery transactions on the same user's session through the SOAP api? If not, please propose a workaround or post some sample code on how to run concurrent xquery transactions against the exist database. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=117691&aid=1940340&group_id=17691 |