BUG# Multiple Thread try to execute some Query

-----Ursprüngliche Nachricht----- Von: Christian Grün [mailto:christian.gruen at gmail.com] Gesendet: Montag, 24. September 2012 00:10 An: samuel.lacmene at buit-solutions.com Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query Dear Samuel Lacmene , sorry for the delay, and thanks for the bug report. First of all, I'd be interested if the bug persists with the latest stable snapshot [1]? If that should be the case, I'be glad if you could provide us with a small example [2] that allows us to reproduce the issue. Thanks in advance, Christian [1] http://files.basex.org/releases/latest/ [2] http://sscce.org/

On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > Dear Christian, > > Thank you for the answer. I have tried to reproduce the BUG with the last > Snapshot, but it still persists. > So, I wrote a small example based on the factbook.xml, the bug occurred in > the first 2 tests and then it has disappeared (See the example in the > attachment). > > I have remarked that, to have more chance to see the BUG, you have to stop > and start the basex-server and run the example. > > Best regards > Samuel > > > -----Ursprüngliche Nachricht----- > Von: Christian Grün [mailto:christian.gruen at gmail.com] > Gesendet: Montag, 24. September 2012 00:10 > An: samuel.lacmene at buit-solutions.com > Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > > > Dear Samuel Lacmene , > > sorry for the delay, and thanks for the bug report. First of all, I'd > be interested if the bug persists with the latest stable snapshot [1]? > If that should be the case, I'be glad if you could provide us with a > small example [2] that allows us to reproduce the issue. > > Thanks in advance, > Christian > > [1] http://files.basex.org/releases/latest/ > [2] http://sscce.org/

On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > Dear Christian, > > Thank you for the answer. I have tried to reproduce the BUG with the last > Snapshot, but it still persists. > So, I wrote a small example based on the factbook.xml, the bug occurred in > the first 2 tests and then it has disappeared (See the example in the > attachment). > > I have remarked that, to have more chance to see the BUG, you have to stop > and start the basex-server and run the example. > > Best regards > Samuel > > > -----Ursprüngliche Nachricht----- > Von: Christian Grün [mailto:christian.gruen at gmail.com] > Gesendet: Montag, 24. September 2012 00:10 > An: samuel.lacmene at buit-solutions.com > Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > > > Dear Samuel Lacmene , > > sorry for the delay, and thanks for the bug report. First of all, I'd > be interested if the bug persists with the latest stable snapshot [1]? > If that should be the case, I'be glad if you could provide us with a > small example [2] that allows us to reproduce the issue. > > Thanks in advance, > Christian > > [1] http://files.basex.org/releases/latest/ > [2] http://sscce.org/

On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > Dear Christian, > > Thank you for the answer. I have tried to reproduce the BUG with the last > Snapshot, but it still persists. > So, I wrote a small example based on the factbook.xml, the bug occurred in > the first 2 tests and then it has disappeared (See the example in the > attachment). > > I have remarked that, to have more chance to see the BUG, you have to stop > and start the basex-server and run the example. > > Best regards > Samuel > > > -----Ursprüngliche Nachricht----- > Von: Christian Grün [mailto:christian.gruen at gmail.com] > Gesendet: Montag, 24. September 2012 00:10 > An: samuel.lacmene at buit-solutions.com > Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > > > Dear Samuel Lacmene , > > sorry for the delay, and thanks for the bug report. First of all, I'd > be interested if the bug persists with the latest stable snapshot [1]? > If that should be the case, I'be glad if you could provide us with a > small example [2] that allows us to reproduce the issue. > > Thanks in advance, > Christian > > [1] http://files.basex.org/releases/latest/ > [2] http://sscce.org/

> I did not try it, because the bug occurs randomly. You should try it a lot > of time to trigger it. > Another possibility to increase the probability to see the bug is to run > complex requests.

> ----------------------------------------------------------------- > > > ..some first feedback: your example causes no problems when being run > from the command line. > > However, I managed to reproduce the bug when running your example from > within Eclipse. The error won’t occur when I suppress the dump to > stdout, or forward it to a file. > > Two questions that might help to narrow down the issue: > > - did you also use for Eclipse for testing? > - do you manage to reproduce the bug when running the example outside > Eclipse? > - what happens if you suppress the text output? > > Thanks, > Christian > ___________________________________ > > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene > <samuel.lacmene at buit-solutions.com> wrote: >> Dear Christian, >> >> Thank you for the answer. I have tried to reproduce the BUG with the last >> Snapshot, but it still persists. >> So, I wrote a small example based on the factbook.xml, the bug occurred in >> the first 2 tests and then it has disappeared (See the example in the >> attachment). >> >> I have remarked that, to have more chance to see the BUG, you have to stop >> and start the basex-server and run the example. >> >> Best regards >> Samuel >> >> >> -----Ursprüngliche Nachricht----- >> Von: Christian Grün [mailto:christian.gruen at gmail.com] >> Gesendet: Montag, 24. September 2012 00:10 >> An: samuel.lacmene at buit-solutions.com >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query >> >> >> Dear Samuel Lacmene , >> >> sorry for the delay, and thanks for the bug report. First of all, I'd >> be interested if the bug persists with the latest stable snapshot [1]? >> If that should be the case, I'be glad if you could provide us with a >> small example [2] that allows us to reproduce the issue. >> >> Thanks in advance, >> Christian >> >> [1] http://files.basex.org/releases/latest/ >> [2] http://sscce.org/

> I did not try it, because the bug occurs randomly. You should try it a lot > of time to trigger it. > Another possibility to increase the probability to see the bug is to run > complex requests.

> ----------------------------------------------------------------- > > > ..some first feedback: your example causes no problems when being run > from the command line. > > However, I managed to reproduce the bug when running your example from > within Eclipse. The error won’t occur when I suppress the dump to > stdout, or forward it to a file. > > Two questions that might help to narrow down the issue: > > - did you also use for Eclipse for testing? > - do you manage to reproduce the bug when running the example outside > Eclipse? > - what happens if you suppress the text output? > > Thanks, > Christian > ___________________________________ > > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene > <samuel.lacmene at buit-solutions.com> wrote: >> Dear Christian, >> >> Thank you for the answer. I have tried to reproduce the BUG with the last >> Snapshot, but it still persists. >> So, I wrote a small example based on the factbook.xml, the bug occurred in >> the first 2 tests and then it has disappeared (See the example in the >> attachment). >> >> I have remarked that, to have more chance to see the BUG, you have to stop >> and start the basex-server and run the example. >> >> Best regards >> Samuel >> >> >> -----Ursprüngliche Nachricht----- >> Von: Christian Grün [mailto:christian.gruen at gmail.com] >> Gesendet: Montag, 24. September 2012 00:10 >> An: samuel.lacmene at buit-solutions.com >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query >> >> >> Dear Samuel Lacmene , >> >> sorry for the delay, and thanks for the bug report. First of all, I'd >> be interested if the bug persists with the latest stable snapshot [1]? >> If that should be the case, I'be glad if you could provide us with a >> small example [2] that allows us to reproduce the issue. >> >> Thanks in advance, >> Christian >> >> [1] http://files.basex.org/releases/latest/ >> [2] http://sscce.org/

On Thu, Sep 27, 2012 at 6:11 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > I have only tested it with Java 7. > > I have adjusted the PARALLEL option to 1, my test runs until now without > problem and I hope that it will stay so. > I will let you know, if this setting walk for me or not. > > Thank, > Samuel > > > -------------------------- > > >> I did not try it, because the bug occurs randomly. You should try it a lot >> of time to trigger it. >> Another possibility to increase the probability to see the bug is to run >> complex requests. > > I agree that this looks like a classical concurrency bug, but I still > have a hard time narrowing it down, as I didn't manage yet to > reproduce the problem without Eclipse and without stdout. Your test > looks actually pretty similar to numerous other test cases that we've > been using for a long time, e.g. the following one: > > https://github.com/BaseXdb/basex-tests/blob/master/src/test/java/org/basex/test/performance/ServerStressTest.java > > Maybe there's a small, but important difference that I missed by > comparing the approaches? > > One more thought.. Have you done some testing with Java 6? I may be > completely wrong, but I’m wondering if this bug is related to Java 7. > We came across some other concurrency issues that did not happen with > JDK/JRE 6 (some of which have already been fixed in the latest Java 7 > patches). > > Next, you could try to adjust the maximum number of parallel readers, > and see what happens. This can be done by editing the .basex > configuration file [1] and adjust the PARALLEL option [2]. If the > error should persist when setting the number to "1", this could > indicate that the problem is not related to our concurrency model, but > the (un)locking of database files. In the past, we had similar > problems with deleting and re-creating files. It may sound strange, > but File.delete() won't always delete a file, even if there is no lock > attached to it.. > > Christian > > [1] http://docs.basex.org/wiki/Configuration#Configuration_Files > [2] http://docs.basex.org/wiki/Options#PARALLEL > >> ----------------------------------------------------------------- >> >> >> ..some first feedback: your example causes no problems when being run >> from the command line. >> >> However, I managed to reproduce the bug when running your example from >> within Eclipse. The error won’t occur when I suppress the dump to >> stdout, or forward it to a file. >> >> Two questions that might help to narrow down the issue: >> >> - did you also use for Eclipse for testing? >> - do you manage to reproduce the bug when running the example outside >> Eclipse? >> - what happens if you suppress the text output? >> >> Thanks, >> Christian >> ___________________________________ >> >> On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene >> <samuel.lacmene at buit-solutions.com> wrote: >>> Dear Christian, >>> >>> Thank you for the answer. I have tried to reproduce the BUG with the last >>> Snapshot, but it still persists. >>> So, I wrote a small example based on the factbook.xml, the bug occurred >>> in >>> the first 2 tests and then it has disappeared (See the example in the >>> attachment). >>> >>> I have remarked that, to have more chance to see the BUG, you have to >>> stop >>> and start the basex-server and run the example. >>> >>> Best regards >>> Samuel >>> >>> >>> -----Ursprüngliche Nachricht----- >>> Von: Christian Grün [mailto:christian.gruen at gmail.com] >>> Gesendet: Montag, 24. September 2012 00:10 >>> An: samuel.lacmene at buit-solutions.com >>> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query >>> >>> >>> Dear Samuel Lacmene , >>> >>> sorry for the delay, and thanks for the bug report. First of all, I'd >>> be interested if the bug persists with the latest stable snapshot [1]? >>> If that should be the case, I'be glad if you could provide us with a >>> small example [2] that allows us to reproduce the issue. >>> >>> Thanks in advance, >>> Christian >>> >>> [1] http://files.basex.org/releases/latest/ >>> [2] http://sscce.org/

On Thu, Sep 27, 2012 at 6:11 PM, Samuel Lacmene < samuel.lacmene at buit-solutions.com> wrote: > I have only tested it with Java 7. > > I have adjusted the PARALLEL option to 1, my test runs until now without > problem and I hope that it will stay so. > I will let you know, if this setting walk for me or not. > > Thank, > Samuel > > > -------------------------- > > > > I did not try it, because the bug occurs randomly. You should try it a > lot > > of time to trigger it. > > Another possibility to increase the probability to see the bug is to run > > complex requests. > > I agree that this looks like a classical concurrency bug, but I still > have a hard time narrowing it down, as I didn't manage yet to > reproduce the problem without Eclipse and without stdout. Your test > looks actually pretty similar to numerous other test cases that we've > been using for a long time, e.g. the following one: > > > https://github.com/BaseXdb/basex-tests/blob/master/src/test/java/org/basex/test/performance/ServerStressTest.java > > Maybe there's a small, but important difference that I missed by > comparing the approaches? > > One more thought.. Have you done some testing with Java 6? I may be > completely wrong, but I’m wondering if this bug is related to Java 7. > We came across some other concurrency issues that did not happen with > JDK/JRE 6 (some of which have already been fixed in the latest Java 7 > patches). > > Next, you could try to adjust the maximum number of parallel readers, > and see what happens. This can be done by editing the .basex > configuration file [1] and adjust the PARALLEL option [2]. If the > error should persist when setting the number to "1", this could > indicate that the problem is not related to our concurrency model, but > the (un)locking of database files. In the past, we had similar > problems with deleting and re-creating files. It may sound strange, > but File.delete() won't always delete a file, even if there is no lock > attached to it.. > > Christian > > [1] http://docs.basex.org/wiki/Configuration#Configuration_Files > [2] http://docs.basex.org/wiki/Options#PARALLEL > > > ----------------------------------------------------------------- > > > > > > ..some first feedback: your example causes no problems when being run > > from the command line. > > > > However, I managed to reproduce the bug when running your example from > > within Eclipse. The error won’t occur when I suppress the dump to > > stdout, or forward it to a file. > > > > Two questions that might help to narrow down the issue: > > > > - did you also use for Eclipse for testing? > > - do you manage to reproduce the bug when running the example outside > > Eclipse? > > - what happens if you suppress the text output? > > > > Thanks, > > Christian > > ___________________________________ > > > > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene > > <samuel.lacmene at buit-solutions.com> wrote: > >> Dear Christian, > >> > >> Thank you for the answer. I have tried to reproduce the BUG with the > last > >> Snapshot, but it still persists. > >> So, I wrote a small example based on the factbook.xml, the bug occurred > in > >> the first 2 tests and then it has disappeared (See the example in the > >> attachment). > >> > >> I have remarked that, to have more chance to see the BUG, you have to > stop > >> and start the basex-server and run the example. > >> > >> Best regards > >> Samuel > >> > >> > >> -----Ursprüngliche Nachricht----- > >> Von: Christian Grün [mailto:christian.gruen at gmail.com] > >> Gesendet: Montag, 24. September 2012 00:10 > >> An: samuel.lacmene at buit-solutions.com > >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > >> > >> > >> Dear Samuel Lacmene , > >> > >> sorry for the delay, and thanks for the bug report. First of all, I'd > >> be interested if the bug persists with the latest stable snapshot [1]? > >> If that should be the case, I'be glad if you could provide us with a > >> small example [2] that allows us to reproduce the issue. > >> > >> Thanks in advance, > >> Christian > >> > >> [1] http://files.basex.org/releases/latest/ > >> [2] http://sscce.org/ > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk > >

-----Ursprüngliche Nachricht----- Von: Lukas Kircher [mailto:lukaskircher1 at gmail.com] Gesendet: Freitag, 28. September 2012 14:23 An: samuel.lacmene at buit-solutions.com Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query Hi Samuel, testing on my machine (OSX 10.8, Java 7) I can only report what you already came across yourself: - activating/deactivation output makes no difference - Java 6/7 makes no difference - limiting PARALLEL option to 1 seems to resolve the issue As we couldn't figure out the problem on the fly I've created an [issue] on Github. Feel free to add anything if you think it might help. Thanks for your report so far! I hope the current workaround is good enough to keep you going until we figured out the real problem. Cheers, Lukas [issued] https://github.com/BaseXdb/basex/issues/574 On Thu, Sep 27, 2012 at 6:11 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > I have only tested it with Java 7. > > I have adjusted the PARALLEL option to 1, my test runs until now without problem and I hope that it will stay so. > I will let you know, if this setting walk for me or not. > > Thank, > Samuel > > > -------------------------- > > > I did not try it, because the bug occurs randomly. You should try it a lot > > of time to trigger it. > > Another possibility to increase the probability to see the bug is to run > > complex requests. > > I agree that this looks like a classical concurrency bug, but I still > have a hard time narrowing it down, as I didn't manage yet to > reproduce the problem without Eclipse and without stdout. Your test > looks actually pretty similar to numerous other test cases that we've > been using for a long time, e.g. the following one: > > https://github.com/BaseXdb/basex-tests/blob/master/src/test/java/org/basex/test/performance/ServerStressTest.java > > Maybe there's a small, but important difference that I missed by > comparing the approaches? > > One more thought.. Have you done some testing with Java 6? I may be > completely wrong, but I’m wondering if this bug is related to Java 7. > We came across some other concurrency issues that did not happen with > JDK/JRE 6 (some of which have already been fixed in the latest Java 7 > patches). > > Next, you could try to adjust the maximum number of parallel readers, > and see what happens. This can be done by editing the .basex > configuration file [1] and adjust the PARALLEL option [2]. If the > error should persist when setting the number to "1", this could > indicate that the problem is not related to our concurrency model, but > the (un)locking of database files. In the past, we had similar > problems with deleting and re-creating files. It may sound strange, > but File.delete() won't always delete a file, even if there is no lock > attached to it.. > > Christian > > [1] http://docs.basex.org/wiki/Configuration#Configuration_Files > [2] http://docs.basex.org/wiki/Options#PARALLEL > > > ----------------------------------------------------------------- > > > > > > ..some first feedback: your example causes no problems when being run > > from the command line. > > > > However, I managed to reproduce the bug when running your example from > > within Eclipse. The error won’t occur when I suppress the dump to > > stdout, or forward it to a file. > > > > Two questions that might help to narrow down the issue: > > > > - did you also use for Eclipse for testing? > > - do you manage to reproduce the bug when running the example outside > > Eclipse? > > - what happens if you suppress the text output? > > > > Thanks, > > Christian > > ___________________________________ > > > > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene > > <samuel.lacmene at buit-solutions.com> wrote: > >> Dear Christian, > >> > >> Thank you for the answer. I have tried to reproduce the BUG with the last > >> Snapshot, but it still persists. > >> So, I wrote a small example based on the factbook.xml, the bug occurred in > >> the first 2 tests and then it has disappeared (See the example in the > >> attachment). > >> > >> I have remarked that, to have more chance to see the BUG, you have to stop > >> and start the basex-server and run the example. > >> > >> Best regards > >> Samuel > >> > >> > >> -----Ursprüngliche Nachricht----- > >> Von: Christian Grün [mailto:christian.gruen at gmail.com] > >> Gesendet: Montag, 24. September 2012 00:10 > >> An: samuel.lacmene at buit-solutions.com > >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > >> > >> > >> Dear Samuel Lacmene , > >> > >> sorry for the delay, and thanks for the bug report. First of all, I'd > >> be interested if the bug persists with the latest stable snapshot [1]? > >> If that should be the case, I'be glad if you could provide us with a > >> small example [2] that allows us to reproduce the issue. > >> > >> Thanks in advance, > >> Christian > >> > >> [1] http://files.basex.org/releases/latest/ > >> [2] http://sscce.org/ > > > > > _______________________________________________ > BaseX-Talk mailing list > BaseX-Talk at mailman.uni-konstanz.de > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk

On Thu, Oct 4, 2012 at 5:22 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > Thank you guys. This configuration resolves the problem for me. > > -----Ursprüngliche Nachricht----- > Von: Lukas Kircher [mailto:lukaskircher1 at gmail.com] > Gesendet: Freitag, 28. September 2012 14:23 > > An: samuel.lacmene at buit-solutions.com > Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > > > Hi Samuel, > > testing on my machine (OSX 10.8, Java 7) I can only report > what you already came across yourself: > > - activating/deactivation output makes no difference > - Java 6/7 makes no difference > - limiting PARALLEL option to 1 seems to resolve the issue > > As we couldn't figure out the problem on the fly I've created > an [issue] on Github. Feel free to add anything if you think it > might help. > > Thanks for your report so far! I hope the current workaround > is good enough to keep you going until we figured out the real > problem. > > > Cheers, > Lukas > > > [issued] https://github.com/BaseXdb/basex/issues/574 > > > On Thu, Sep 27, 2012 at 6:11 PM, Samuel Lacmene > <samuel.lacmene at buit-solutions.com> wrote: >> >> I have only tested it with Java 7. >> >> I have adjusted the PARALLEL option to 1, my test runs until now without >> problem and I hope that it will stay so. >> I will let you know, if this setting walk for me or not. >> >> Thank, >> Samuel >> >> >> -------------------------- >> >> >> > I did not try it, because the bug occurs randomly. You should try it a >> > lot >> > of time to trigger it. >> > Another possibility to increase the probability to see the bug is to run >> > complex requests. >> >> I agree that this looks like a classical concurrency bug, but I still >> have a hard time narrowing it down, as I didn't manage yet to >> reproduce the problem without Eclipse and without stdout. Your test >> looks actually pretty similar to numerous other test cases that we've >> been using for a long time, e.g. the following one: >> >> >> https://github.com/BaseXdb/basex-tests/blob/master/src/test/java/org/basex/test/performance/ServerStressTest.java >> >> Maybe there's a small, but important difference that I missed by >> comparing the approaches? >> >> One more thought.. Have you done some testing with Java 6? I may be >> completely wrong, but I’m wondering if this bug is related to Java 7. >> We came across some other concurrency issues that did not happen with >> JDK/JRE 6 (some of which have already been fixed in the latest Java 7 >> patches). >> >> Next, you could try to adjust the maximum number of parallel readers, >> and see what happens. This can be done by editing the .basex >> configuration file [1] and adjust the PARALLEL option [2]. If the >> error should persist when setting the number to "1", this could >> indicate that the problem is not related to our concurrency model, but >> the (un)locking of database files. In the past, we had similar >> problems with deleting and re-creating files. It may sound strange, >> but File.delete() won't always delete a file, even if there is no lock >> attached to it.. >> >> Christian >> >> [1] http://docs.basex.org/wiki/Configuration#Configuration_Files >> [2] http://docs.basex.org/wiki/Options#PARALLEL >> >> > ----------------------------------------------------------------- >> > >> > >> > ..some first feedback: your example causes no problems when being run >> > from the command line. >> > >> > However, I managed to reproduce the bug when running your example from >> > within Eclipse. The error won’t occur when I suppress the dump to >> > stdout, or forward it to a file. >> > >> > Two questions that might help to narrow down the issue: >> > >> > - did you also use for Eclipse for testing? >> > - do you manage to reproduce the bug when running the example outside >> > Eclipse? >> > - what happens if you suppress the text output? >> > >> > Thanks, >> > Christian >> > ___________________________________ >> > >> > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene >> > <samuel.lacmene at buit-solutions.com> wrote: >> >> Dear Christian, >> >> >> >> Thank you for the answer. I have tried to reproduce the BUG with the >> >> last >> >> Snapshot, but it still persists. >> >> So, I wrote a small example based on the factbook.xml, the bug occurred >> >> in >> >> the first 2 tests and then it has disappeared (See the example in the >> >> attachment). >> >> >> >> I have remarked that, to have more chance to see the BUG, you have to >> >> stop >> >> and start the basex-server and run the example. >> >> >> >> Best regards >> >> Samuel >> >> >> >> >> >> -----Ursprüngliche Nachricht----- >> >> Von: Christian Grün [mailto:christian.gruen at gmail.com] >> >> Gesendet: Montag, 24. September 2012 00:10 >> >> An: samuel.lacmene at buit-solutions.com >> >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some >> >> Query >> >> >> >> >> >> Dear Samuel Lacmene , >> >> >> >> sorry for the delay, and thanks for the bug report. First of all, I'd >> >> be interested if the bug persists with the latest stable snapshot [1]? >> >> If that should be the case, I'be glad if you could provide us with a >> >> small example [2] that allows us to reproduce the issue. >> >> >> >> Thanks in advance, >> >> Christian >> >> >> >> [1] http://files.basex.org/releases/latest/ >> >> [2] http://sscce.org/ >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >

-----Ursprüngliche Nachricht----- Von: Christian Grün [mailto:christian.gruen at gmail.com] Gesendet: Sonntag, 18. November 2012 23:30 An: samuel.lacmene at buit-solutions.com Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query Hi Samuel, it has been a while ago, but I finally had a look at the issue you reported [1], and I’d be glad if you could have a look at the latest snapshot [2]. I cannot promise anything, but at least I didn't manage anymore to reproduce the original bug in my last tests. Thanks in advance, Christian [1] https://github.com/BaseXdb/basex/issues/574 [2] http://files.basex.org/releases/latest/ On Thu, Oct 4, 2012 at 5:22 PM, Samuel Lacmene <samuel.lacmene at buit-solutions.com> wrote: > Thank you guys. This configuration resolves the problem for me. > > -----Ursprüngliche Nachricht----- > Von: Lukas Kircher [mailto:lukaskircher1 at gmail.com] > Gesendet: Freitag, 28. September 2012 14:23 > > An: samuel.lacmene at buit-solutions.com > Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some Query > > > Hi Samuel, > > testing on my machine (OSX 10.8, Java 7) I can only report > what you already came across yourself: > > - activating/deactivation output makes no difference > - Java 6/7 makes no difference > - limiting PARALLEL option to 1 seems to resolve the issue > > As we couldn't figure out the problem on the fly I've created > an [issue] on Github. Feel free to add anything if you think it > might help. > > Thanks for your report so far! I hope the current workaround > is good enough to keep you going until we figured out the real > problem. > > > Cheers, > Lukas > > > [issued] https://github.com/BaseXdb/basex/issues/574 > > > On Thu, Sep 27, 2012 at 6:11 PM, Samuel Lacmene > <samuel.lacmene at buit-solutions.com> wrote: >> >> I have only tested it with Java 7. >> >> I have adjusted the PARALLEL option to 1, my test runs until now without >> problem and I hope that it will stay so. >> I will let you know, if this setting walk for me or not. >> >> Thank, >> Samuel >> >> >> -------------------------- >> >> >> > I did not try it, because the bug occurs randomly. You should try it a >> > lot >> > of time to trigger it. >> > Another possibility to increase the probability to see the bug is to run >> > complex requests. >> >> I agree that this looks like a classical concurrency bug, but I still >> have a hard time narrowing it down, as I didn't manage yet to >> reproduce the problem without Eclipse and without stdout. Your test >> looks actually pretty similar to numerous other test cases that we've >> been using for a long time, e.g. the following one: >> >> >> https://github.com/BaseXdb/basex-tests/blob/master/src/test/java/org/basex/test/performance/ServerStressTest.java >> >> Maybe there's a small, but important difference that I missed by >> comparing the approaches? >> >> One more thought.. Have you done some testing with Java 6? I may be >> completely wrong, but I’m wondering if this bug is related to Java 7. >> We came across some other concurrency issues that did not happen with >> JDK/JRE 6 (some of which have already been fixed in the latest Java 7 >> patches). >> >> Next, you could try to adjust the maximum number of parallel readers, >> and see what happens. This can be done by editing the .basex >> configuration file [1] and adjust the PARALLEL option [2]. If the >> error should persist when setting the number to "1", this could >> indicate that the problem is not related to our concurrency model, but >> the (un)locking of database files. In the past, we had similar >> problems with deleting and re-creating files. It may sound strange, >> but File.delete() won't always delete a file, even if there is no lock >> attached to it.. >> >> Christian >> >> [1] http://docs.basex.org/wiki/Configuration#Configuration_Files >> [2] http://docs.basex.org/wiki/Options#PARALLEL >> >> > ----------------------------------------------------------------- >> > >> > >> > ..some first feedback: your example causes no problems when being run >> > from the command line. >> > >> > However, I managed to reproduce the bug when running your example from >> > within Eclipse. The error won’t occur when I suppress the dump to >> > stdout, or forward it to a file. >> > >> > Two questions that might help to narrow down the issue: >> > >> > - did you also use for Eclipse for testing? >> > - do you manage to reproduce the bug when running the example outside >> > Eclipse? >> > - what happens if you suppress the text output? >> > >> > Thanks, >> > Christian >> > ___________________________________ >> > >> > On Wed, Sep 26, 2012 at 3:31 PM, Samuel Lacmene >> > <samuel.lacmene at buit-solutions.com> wrote: >> >> Dear Christian, >> >> >> >> Thank you for the answer. I have tried to reproduce the BUG with the >> >> last >> >> Snapshot, but it still persists. >> >> So, I wrote a small example based on the factbook.xml, the bug occurred >> >> in >> >> the first 2 tests and then it has disappeared (See the example in the >> >> attachment). >> >> >> >> I have remarked that, to have more chance to see the BUG, you have to >> >> stop >> >> and start the basex-server and run the example. >> >> >> >> Best regards >> >> Samuel >> >> >> >> >> >> -----Ursprüngliche Nachricht----- >> >> Von: Christian Grün [mailto:christian.gruen at gmail.com] >> >> Gesendet: Montag, 24. September 2012 00:10 >> >> An: samuel.lacmene at buit-solutions.com >> >> Betreff: Re: [basex-talk] BUG# Multiple Thread try to execute some >> >> Query >> >> >> >> >> >> Dear Samuel Lacmene , >> >> >> >> sorry for the delay, and thanks for the bug report. First of all, I'd >> >> be interested if the bug persists with the latest stable snapshot [1]? >> >> If that should be the case, I'be glad if you could provide us with a >> >> small example [2] that allows us to reproduce the issue. >> >> >> >> Thanks in advance, >> >> Christian >> >> >> >> [1] http://files.basex.org/releases/latest/ >> >> [2] http://sscce.org/ >> >> _______________________________________________ >> BaseX-Talk mailing list >> BaseX-Talk at mailman.uni-konstanz.de >> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >> >