Re: [jr3] Synchronized sessions

2010-02-26 Thread Felix Meschberger
Hi, On 26.02.2010 19:11, Jukka Zitting wrote: > Hi, > > On Fri, Feb 26, 2010 at 6:36 PM, Felix Meschberger wrote: >> Consider two threads T1 and T2 each modifying data from the same session: >> >> T1 makes some modifications >> T2 makes some modifications >> T1 saves the session (incl. both T

[jira] Updated: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)

2010-02-26 Thread Antonio Martinez (JIRA)
[ https://issues.apache.org/jira/browse/JCR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Martinez updated JCR-2426: -- Attachment: deadlock_jackrabbit1.6.txt > Deadlock in lucene (Jackrabbit 1.4.4) >

[jira] Commented: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)

2010-02-26 Thread Antonio Martinez (JIRA)
[ https://issues.apache.org/jira/browse/JCR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839069#action_12839069 ] Antonio Martinez commented on JCR-2426: --- Moving to a newer version of Java is too risky

Re: [jr3] Synchronized sessions

2010-02-26 Thread Guo Du
On Fri, Feb 26, 2010 at 6:11 PM, Jukka Zitting wrote: > All we're trying to achieve here is ensure internal consistency even > when clients do something like the above (for whatever reason, > intentional or not). jdbc connection is not thread safe. jcr session works similar way and I prefer foll

Re: [jr3] Synchronized sessions

2010-02-26 Thread Jukka Zitting
Hi, On Fri, Feb 26, 2010 at 6:36 PM, Felix Meschberger wrote: > Consider two threads T1 and T2 each modifying data from the same session: > >  T1 makes some modifications >  T2 makes some modifications >  T1 saves the session (incl. both T1's and T2's modifs) >  T2 makes some more modifications >

Re: [jr3] Synchronized sessions

2010-02-26 Thread Felix Meschberger
Hi, On 25.02.2010 16:33, Thomas Müller wrote: >> this creates a big potential for deadlocks > > Could you provide an example on how such a deadlock could look like? While I could not yet come up with such an example, I found another problem involving data inconsistency. Consider two threads T1

Re: [jr3] Synchronized sessions

2010-02-26 Thread Felix Meschberger
Hi, On 26.02.2010 14:38, Marcel Reutegger wrote: > Hi, > > On Thu, Feb 25, 2010 at 19:14, Felix Meschberger wrote: >> Hi, >> >> On 25.02.2010 17:55, Marcel Reutegger wrote: >>> Hi, >>> >>> On Thu, Feb 25, 2010 at 15:49, Felix Meschberger wrote: Hi, On 24.02.2010 21:19, Thomas Mül

Re: [jr3] Synchronized sessions

2010-02-26 Thread Marcel Reutegger
Hi, On Thu, Feb 25, 2010 at 19:14, Felix Meschberger wrote: > Hi, > > On 25.02.2010 17:55, Marcel Reutegger wrote: >> Hi, >> >> On Thu, Feb 25, 2010 at 15:49, Felix Meschberger wrote: >>> Hi, >>> >>> On 24.02.2010 21:19, Thomas Müller wrote: Hi, > deadlocks I think it's r

Re: [jr3] EventJournal / who merges changes

2010-02-26 Thread Thomas Müller
Hi Ian, Could you describe your use case? > probability of conflict when updating a multivalued property is reduced What methods do you call, and how should the conflict be resolved? Example: if you currently use the following code: 1) session1.getNode("test").setProperty("multi", new String[]{

Re: [jr3] EventJournal / who merges changes

2010-02-26 Thread Ian Boston
Sorry for top posting, I am not certain where to put this "request". Currently adding child nodes is almost serialised since its not possible to merge concurrent changes in a single multi valued property. *If* MVCC with abort on conflict is going to make this situation worse, then that IMHO woul

[jira] Resolved: (JCR-2522) unable to workspace import XML.

2010-02-26 Thread Tobias Bocanegra (JIRA)
[ https://issues.apache.org/jira/browse/JCR-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra resolved JCR-2522. --- Resolution: Fixed Fix Version/s: 2.1.0 fixed by accepting 2ndary mime type: "application

[jira] Created: (JCR-2522) unable to workspace import XML.

2010-02-26 Thread Tobias Bocanegra (JIRA)
unable to workspace import XML. --- Key: JCR-2522 URL: https://issues.apache.org/jira/browse/JCR-2522 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-jcr-server

[jira] Resolved: (JCR-2521) WorkspaceImporter throws exception

2010-02-26 Thread Tobias Bocanegra (JIRA)
[ https://issues.apache.org/jira/browse/JCR-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra resolved JCR-2521. --- Resolution: Fixed Fix Version/s: 2.1.0 fixed as suggested. > WorkspaceImporter throws e

[jira] Created: (JCR-2521) WorkspaceImporter throws exception

2010-02-26 Thread Tobias Bocanegra (JIRA)
WorkspaceImporter throws exception -- Key: JCR-2521 URL: https://issues.apache.org/jira/browse/JCR-2521 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core

Re: [jr3] Synchronized sessions

2010-02-26 Thread Jukka Zitting
Hi, On Thu, Feb 25, 2010 at 10:24 PM, Thomas Müller wrote: >> http://issues.apache.org/jira/browse/JCR-2443. > > Unfortunately this bug doesn't have a test case. Also I didn't find a > thread dump that shows what the problem was exactly. I can't say what > was the problem there. This problem was

Re: [jr3] Synchronized sessions

2010-02-26 Thread Andrey Adamovich
Hi! +1 for all that Thomas said. Andrey From: Thomas Müller To: dev@jackrabbit.apache.org Sent: Thu, 25 February, 2010 22:24:13 Subject: Re: [jr3] Synchronized sessions Hi > http://issues.apache.org/jira/browse/JCR-2443. Unfortunately this bug doesn't ha