[jira] Resolved: (JCR-2862) Jackrabbit logs a NullPointerException on shutdown if the version manager wasn't initialized

[ https://issues.apache.org/jira/browse/JCR-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2862. - Resolution: Fixed Jackrabbit logs a NullPointerException on shutdown if the version manager

[jira] Updated: (JCR-2862) Jackrabbit logs a NullPointerException on shutdown if the version manager wasn't initialized

[ https://issues.apache.org/jira/browse/JCR-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2862: Fix Version/s: 2.2.2 Jackrabbit logs a NullPointerException on shutdown if the version manager

[jira] Updated: (JCR-2860) Make version recovery extensible

[ https://issues.apache.org/jira/browse/JCR-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2860: Fix Version/s: 2.2.2 Make version recovery extensible

[jira] Resolved: (JCR-2860) Make version recovery extensible

[ https://issues.apache.org/jira/browse/JCR-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2860. - Resolution: Fixed Make version recovery extensible

[jira] Created: (JCR-2860) Make version recovery extensible

Make version recovery extensible Key: JCR-2860 URL: https://issues.apache.org/jira/browse/JCR-2860 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-core

[jira] Commented: (JCR-2860) Make version recovery extensible

[ https://issues.apache.org/jira/browse/JCR-2860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979573#action_12979573 ] Thomas Mueller commented on JCR-2860: - Fixed in the trunk - I will update the Fix Version

[jira] Commented: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12979597#action_12979597 ] Thomas Mueller commented on JCR-2857: - Revision 1057220 and revision 1057229. The

[jira] Commented: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978215#action_12978215 ] Thomas Mueller commented on JCR-2857: - One solution to ensure uniqueness is to use a

[jira] Commented: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977678#action_12977678 ] Thomas Mueller commented on JCR-2857: - Sequential node ids are much faster than random

[jira] Created: (JCR-2857) Support sequential (non-random) node ids

Support sequential (non-random) node ids Key: JCR-2857 URL: https://issues.apache.org/jira/browse/JCR-2857 Project: Jackrabbit Content Repository Issue Type: Improvement Reporter: Thomas

[jira] Updated: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2857: Component/s: jackrabbit-core Description: Currently, node ids are generated using a

[jira] Updated: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2857: Attachment: jcr-2857.patch This patch is a first version of the node id factory. The default

[jira] Commented: (JCR-2819) FileDataStore not crash safe

[ https://issues.apache.org/jira/browse/JCR-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967123#action_12967123 ] Thomas Mueller commented on JCR-2819: - it sounds like it is only covering the

[jira] Updated: (JCR-2740) On missing child node, automatically remove the entry

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2740: Description: If a node points to a non-existing child node (which is a repository inconsistency),

[jira] Updated: (JCR-2740) On missing child node, automatically remove the entry (when a session attribute is set)

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2740: Description: If a node points to a non-existing child node (which is a repository inconsistency),

[jira] Resolved: (JCR-2740) On missing child node, automatically remove the entry (when a session attribute is set)

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2740. - Resolution: Fixed On missing child node, automatically remove the entry (when a session

[jira] Updated: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2740: Attachment: jcr-2740-c.patch New patch (should now be correct). On missing child node,

[jira] Commented: (JCR-2819) FileDataStore not crash safe

[ https://issues.apache.org/jira/browse/JCR-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935244#action_12935244 ] Thomas Mueller commented on JCR-2819: - As you may know, there was a discussion about how

[jira] Updated: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2740: Attachment: jcr-2740-b.patch This new patch only fixes the problem when a session attribute is set.

[jira] Created: (JCR-2816) Repository is not unlocked if version manager init failed and assertions are enabled

Repository is not unlocked if version manager init failed and assertions are enabled Key: JCR-2816 URL: https://issues.apache.org/jira/browse/JCR-2816 Project:

[jira] Resolved: (JCR-2816) Repository is not unlocked if version manager init failed and assertions are enabled

[ https://issues.apache.org/jira/browse/JCR-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2816. - Resolution: Fixed Fix Version/s: 2.2.0 I removed the assertion in revision 1037668.

[jira] Updated: (JCR-2676) FileDataStore should check for lastModified error result

[ https://issues.apache.org/jira/browse/JCR-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2676: Fix Version/s: 2.2.0 FileDataStore should check for lastModified error result

[jira] Assigned: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2809: --- Assignee: Thomas Mueller Lock expires almost immediately ---

[jira] Commented: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930968#action_12930968 ] Thomas Mueller commented on JCR-2809: - I agree with Felix, repeated multiplication by

[jira] Commented: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930980#action_12930980 ] Thomas Mueller commented on JCR-2809: - There is one more bug when using XA: the timeout

[jira] Commented: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930982#action_12930982 ] Thomas Mueller commented on JCR-2809: - The existing ConcurrentLocking* tests are not

[jira] Updated: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2809: Attachment: jcr-2809-lockTimeout.patch Proposed patch Lock expires almost immediately

[jira] Resolved: (JCR-2809) Lock expires almost immediately

[ https://issues.apache.org/jira/browse/JCR-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2809. - Resolution: Fixed Fix Version/s: 2.2.0 Fixed in the trunk Lock expires almost immediately

[jira] Created: (JCR-2811) Allow to override LockManager creation

Allow to override LockManager creation -- Key: JCR-2811 URL: https://issues.apache.org/jira/browse/JCR-2811 Project: Jackrabbit Content Repository Issue Type: New Feature Components:

[jira] Resolved: (JCR-2811) Allow to override LockManager creation

[ https://issues.apache.org/jira/browse/JCR-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2811. - Resolution: Fixed Implemented in the trunk. Allow to override LockManager creation

[jira] Resolved: (JCR-2781) FileDataStore performance improvements

[ https://issues.apache.org/jira/browse/JCR-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2781. - Resolution: Fixed Fixed in revision #1022094 - I currently don't see any other obvious way to

[jira] Updated: (JCR-2396) File Journal workaround for misbehaving NFS implementations

[ https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2396: Status: Patch Available (was: Open) I don't plan to commit the patch currently, because it is only

[jira] Updated: (JCR-2396) File Journal workaround for misbehaving NFS implementations

[ https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2396: Resolution: Won't Fix Status: Resolved (was: Patch Available) File Journal workaround for

[jira] Resolved: (JCR-2033) Node.orderBefore is slow

[ https://issues.apache.org/jira/browse/JCR-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2033. - Resolution: Won't Fix I don't plan to work in this issue for Jackrabbit 2.x. We should ensure it's

[jira] Resolved: (JCR-2477) Log / trace wrapper: upgrade to JCR API 2.0

[ https://issues.apache.org/jira/browse/JCR-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2477. - Resolution: Fixed I think this issue is fixed now. If it doesn't work for you, please open a new

[jira] Resolved: (JCR-2049) A tool to support large or long running transactions

[ https://issues.apache.org/jira/browse/JCR-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2049. - Resolution: Won't Fix It seems this tool is not as important as I thought. I don't plan to

[jira] Created: (JCR-2808) Hop 0 sample app doesn't exit because of on-daemon thread pool-1-thread-1

Hop 0 sample app doesn't exit because of on-daemon thread pool-1-thread-1 - Key: JCR-2808 URL: https://issues.apache.org/jira/browse/JCR-2808 Project: Jackrabbit Content

[jira] Commented: (JCR-2808) Hop 0 sample app doesn't exit because of on-daemon thread pool-1-thread-1

[ https://issues.apache.org/jira/browse/JCR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929569#action_12929569 ] Thomas Mueller commented on JCR-2808: - I couldn't find where the thread is created.

[jira] Commented: (JCR-2808) Hop 0 sample app doesn't exit because of on-daemon thread pool-1-thread-1

[ https://issues.apache.org/jira/browse/JCR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929573#action_12929573 ] Thomas Mueller commented on JCR-2808: - The problem is DynamicPooledExecutor, which

[jira] Resolved: (JCR-2808) Hop 0 sample app doesn't exit because of on-daemon thread pool-1-thread-1

[ https://issues.apache.org/jira/browse/JCR-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2808. - Resolution: Fixed Fix Version/s: 2.2.0 Assignee: Thomas Mueller Hop 0 sample app

[jira] Updated: (JCR-2781) FileDataStore performance improvements

[ https://issues.apache.org/jira/browse/JCR-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2781: Fix Version/s: 2.2.0 FileDataStore performance improvements --

[jira] Assigned: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2740: --- Assignee: Thomas Mueller On missing child node, automatically rename entry when trying to add

[jira] Commented: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12929586#action_12929586 ] Thomas Mueller commented on JCR-2740: - I think it doesn't make much sense to move the

[jira] Updated: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

[ https://issues.apache.org/jira/browse/JCR-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2740: Attachment: jcr-2740.patch Could those that are familiar with NodeImpl please have a look at the

[jira] Created: (JCR-2795) Initializing SeededSecureRandom may be slow

Initializing SeededSecureRandom may be slow --- Key: JCR-2795 URL: https://issues.apache.org/jira/browse/JCR-2795 Project: Jackrabbit Content Repository Issue Type: Bug Components:

[jira] Created: (JCR-2786) Cluster sync not always done when calling session.refresh(..)

Cluster sync not always done when calling session.refresh(..) - Key: JCR-2786 URL: https://issues.apache.org/jira/browse/JCR-2786 Project: Jackrabbit Content Repository Issue Type:

[jira] Commented: (JCR-2786) Cluster sync not always done when calling session.refresh(..)

[ https://issues.apache.org/jira/browse/JCR-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921378#action_12921378 ] Thomas Mueller commented on JCR-2786: - The easiest solution is to call syncCount++ before

[jira] Resolved: (JCR-2786) Cluster sync not always done when calling session.refresh(..)

[ https://issues.apache.org/jira/browse/JCR-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2786. - Resolution: Fixed Cluster sync not always done when calling session.refresh(..)

[jira] Commented: (JCR-2786) Cluster sync not always done when calling session.refresh(..)

[ https://issues.apache.org/jira/browse/JCR-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921395#action_12921395 ] Thomas Mueller commented on JCR-2786: - Hi Jukka - what do you suggest? Having some way

[jira] Commented: (JCR-2695) Jackrabbit performance test suite

[ https://issues.apache.org/jira/browse/JCR-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920467#action_12920467 ] Thomas Mueller commented on JCR-2695: - I created JCR-2781 to speed up the FileDataStore.

[jira] Created: (JCR-2781) FileDataStore performance improvements

FileDataStore performance improvements -- Key: JCR-2781 URL: https://issues.apache.org/jira/browse/JCR-2781 Project: Jackrabbit Content Repository Issue Type: Improvement Components:

[jira] Commented: (JCR-2762) Optimize bundle serialization

[ https://issues.apache.org/jira/browse/JCR-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919754#action_12919754 ] Thomas Mueller commented on JCR-2762: - I would rename the methods from readInt() /

[jira] Commented: (JCR-2760) Use hash codes instead of sequence numbers for string indexes

[ https://issues.apache.org/jira/browse/JCR-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917912#action_12917912 ] Thomas Mueller commented on JCR-2760: - +1 looks good to me for Jackrabbit 2.x. I think

[jira] Commented: (JCR-2760) Use hash codes instead of sequence numbers for string indexes

[ https://issues.apache.org/jira/browse/JCR-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916051#action_12916051 ] Thomas Mueller commented on JCR-2760: - I'm not sure if this is really a big problem, so

[jira] Updated: (JCR-2746) Deadlock triggered by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2746: Summary: Deadlock triggered by ObservationDispatcher (was: Deadlock caused by

[jira] Commented: (JCR-2746) Deadlock caused by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912864#action_12912864 ] Thomas Mueller commented on JCR-2746: - The bug in DefaultISMLocking was introduces with

[jira] Created: (JCR-2752) The jackrabbit-pool- thread prevents the process from stopping

The jackrabbit-pool- thread prevents the process from stopping Key: JCR-2752 URL: https://issues.apache.org/jira/browse/JCR-2752 Project: Jackrabbit Content Repository Issue

[jira] Resolved: (JCR-2752) The jackrabbit-pool- thread prevents the process from stopping

[ https://issues.apache.org/jira/browse/JCR-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2752. - Resolution: Fixed The jackrabbit-pool- thread prevents the process from stopping

[jira] Commented: (JCR-2746) Deadlock triggered by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912917#action_12912917 ] Thomas Mueller commented on JCR-2746: - The deadlock in DefaultISMLocking is now tracked

[jira] Resolved: (JCR-2753) Deadlock in DefaultISMLocking

[ https://issues.apache.org/jira/browse/JCR-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2753. - Fix Version/s: 2.2.0 Resolution: Fixed Reverted the changes made by revision 995411 and

[jira] Updated: (JCR-2746) Deadlock triggered by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2746: Attachment: TestObservationEndlessLoop.java Test case to get the endless loop. Deadlock triggered

[jira] Updated: (JCR-2746) Sleep in possibly endless loop in ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2746: Summary: Sleep in possibly endless loop in ObservationDispatcher (was: Deadlock triggered by

[jira] Commented: (JCR-2746) Sleep in possibly endless loop in ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912970#action_12912970 ] Thomas Mueller commented on JCR-2746: - Sleeping no longer happens in a loop. Also,

[jira] Resolved: (JCR-2746) Sleep in possibly endless loop in ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2746. - Resolution: Fixed Sleep in possibly endless loop in ObservationDispatcher

[jira] Commented: (JCR-2746) Deadlock caused by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912473#action_12912473 ] Thomas Mueller commented on JCR-2746: - Thread.sleep can't be the root cause of a new

[jira] Assigned: (JCR-2746) Deadlock caused by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2746: --- Assignee: Thomas Mueller Deadlock caused by ObservationDispatcher

[jira] Commented: (JCR-2746) Deadlock caused by ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912477#action_12912477 ] Thomas Mueller commented on JCR-2746: - There seems to be a bug in DefaultISMLocking: 1)

[jira] Created: (JCR-2749) Closing a session twice shouldn't write a warning in the log

Closing a session twice shouldn't write a warning in the log Key: JCR-2749 URL: https://issues.apache.org/jira/browse/JCR-2749 Project: Jackrabbit Content Repository Issue Type:

[jira] Updated: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2749: Assignee: Thomas Mueller Fix Version/s: 2.2.0 Affects Version/s: 2.2.0

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909660#action_12909660 ] Thomas Mueller commented on JCR-2749: - The warning (with stack trace) is even logged if

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909667#action_12909667 ] Thomas Mueller commented on JCR-2749: - If we do really want a warning in the log (which I

[jira] Updated: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-2749: Attachment: sessionClose.txt Proposed patch Closing a session twice shouldn't write a warning in

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909670#action_12909670 ] Thomas Mueller commented on JCR-2749: - I don't think the problem only occurs with

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909683#action_12909683 ] Thomas Mueller commented on JCR-2749: - The main problem is fixed in revision 997244 - if

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12909700#action_12909700 ] Thomas Mueller commented on JCR-2749: - Thanks a lot Jukka, great that you found the root

[jira] Commented: (JCR-2749) Closing a session twice shouldn't write a warning in the log

[ https://issues.apache.org/jira/browse/JCR-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1291#action_1291 ] Thomas Mueller commented on JCR-2749: - Thanks for fixing the root cause of the problem!

[jira] Created: (JCR-2740) On missing child node, automatically rename entry when trying to add a node with the same name

On missing child node, automatically rename entry when trying to add a node with the same name -- Key: JCR-2740 URL: https://issues.apache.org/jira/browse/JCR-2740

[jira] Created: (JCR-2725) PostgreSQL: Failed to guess validation query

PostgreSQL: Failed to guess validation query Key: JCR-2725 URL: https://issues.apache.org/jira/browse/JCR-2725 Project: Jackrabbit Content Repository Issue Type: Bug Reporter: Thomas

[jira] Resolved: (JCR-2725) PostgreSQL: Failed to guess validation query

[ https://issues.apache.org/jira/browse/JCR-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2725. - Fix Version/s: 2.2.0 Resolution: Fixed PostgreSQL: Failed to guess validation query

[jira] Assigned: (JCR-2716) OracleDatabaseJournal should assume Oracle defaults

[ https://issues.apache.org/jira/browse/JCR-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2716: --- Assignee: Thomas Mueller OracleDatabaseJournal should assume Oracle defaults

[jira] Resolved: (JCR-2716) OracleDatabaseJournal should assume Oracle defaults

[ https://issues.apache.org/jira/browse/JCR-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2716. - Fix Version/s: 2.2.0 Resolution: Fixed Patch applied OracleDatabaseJournal should assume

[jira] Assigned: (JCR-2686) Data store garbage collection: interrupt mark

[ https://issues.apache.org/jira/browse/JCR-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2686: --- Assignee: Thomas Mueller Data store garbage collection: interrupt mark

[jira] Commented: (JCR-2686) Data store garbage collection: interrupt mark

[ https://issues.apache.org/jira/browse/JCR-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12899332#action_12899332 ] Thomas Mueller commented on JCR-2686: - Hi, You are right. Looking at the code, I'm not

[jira] Issue Comment Edited: (JCR-2688) Provide utility for handling large number of child nodes/properties

[ https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893130#action_12893130 ] Thomas Mueller edited comment on JCR-2688 at 7/28/10 6:27 AM: -- I

[jira] Commented: (JCR-2688) Provide utility for handling large number of child nodes/properties

[ https://issues.apache.org/jira/browse/JCR-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893130#action_12893130 ] Thomas Mueller commented on JCR-2688: - That about a test dependency? Provide utility

[jira] Commented: (JCR-2685) DbDataStore: table check fails on Oracle with multiple users

[ https://issues.apache.org/jira/browse/JCR-2685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12892254#action_12892254 ] Thomas Mueller commented on JCR-2685: - Hi, Thanks for the patch! It looks good (well, it

[jira] Resolved: (JCR-2673) Add support for hashed passwords in repository.xml

[ https://issues.apache.org/jira/browse/JCR-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2673. - Resolution: Incomplete The description of the requested feature is incomplete. Add support for

[jira] Resolved: (JCR-2676) FileDataStore should check for lastModified error result

[ https://issues.apache.org/jira/browse/JCR-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2676. - Resolution: Fixed Thanks for the patch! I have committed it in the trunk. FileDataStore should

[jira] Commented: (JCR-2682) Allow the FileDataStore to scale over several millions of files

[ https://issues.apache.org/jira/browse/JCR-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12892309#action_12892309 ] Thomas Mueller commented on JCR-2682: - Hi, Thanks for the patch! It it short, and easy

[jira] Commented: (JCR-2686) Data store garbage collection: interrupt mark

[ https://issues.apache.org/jira/browse/JCR-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12892329#action_12892329 ] Thomas Mueller commented on JCR-2686: - Could you check if calling close() does what you

[jira] Commented: (JCR-2677) Extend the FileDataStore implementation to support read-only media (eg. WORMs)

[ https://issues.apache.org/jira/browse/JCR-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12890217#action_12890217 ] Thomas Mueller commented on JCR-2677: - Ah, I get the problem... copy-methods() via

[jira] Assigned: (JCR-2676) FileDataStore should check for lastModified error result

[ https://issues.apache.org/jira/browse/JCR-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2676: --- Assignee: Thomas Mueller FileDataStore should check for lastModified error result

[jira] Commented: (JCR-2677) Extend the FileDataStore implementation to support read-only media (eg. WORMs)

[ https://issues.apache.org/jira/browse/JCR-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12889788#action_12889788 ] Thomas Mueller commented on JCR-2677: - That would be a nice feature. With WORM media you

[jira] Commented: (JCR-2677) Extend the FileDataStore implementation to support read-only media (eg. WORMs)

[ https://issues.apache.org/jira/browse/JCR-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12889806#action_12889806 ] Thomas Mueller commented on JCR-2677: - 2. The temp file is moved to the permanent target

[jira] Assigned: (JCR-2674) FileDataStore ignores return code from setLastModified

[ https://issues.apache.org/jira/browse/JCR-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2674: --- Assignee: Thomas Mueller FileDataStore ignores return code from setLastModified

[jira] Commented: (JCR-2674) FileDataStore ignores return code from setLastModified

[ https://issues.apache.org/jira/browse/JCR-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888769#action_12888769 ] Thomas Mueller commented on JCR-2674: - Thanks a lot for the patch! It is now committed

[jira] Resolved: (JCR-2674) FileDataStore ignores return code from setLastModified

[ https://issues.apache.org/jira/browse/JCR-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2674. - Fix Version/s: 2.2.0 Resolution: Fixed FileDataStore ignores return code from

[jira] Commented: (JCR-2673) Add support for hashed passwords in repository.xml

[ https://issues.apache.org/jira/browse/JCR-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888328#action_12888328 ] Thomas Mueller commented on JCR-2673: - Could you provide more information please, if

[jira] Commented: (JCR-2640) Internal repository context

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872226#action_12872226 ] Thomas Mueller commented on JCR-2640: - But modularization is about separation of

[jira] Resolved: (JCR-2641) SearchIndex

[ https://issues.apache.org/jira/browse/JCR-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2641. - Resolution: Not A Problem Please use the user list for questions. SearchIndex ---

<    1   2   3   4   5   6   7   8   9   10   >