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

-core Reporter: Thomas Mueller Assignee: Thomas Mueller Fix For: 2.2.0 Currently, Repository.getLockManager() internally creates a new lock manager if needed. Jackrabbit should provide an extension point so that a JCR repository that extends it can create

[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

[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

[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

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

Repository Issue Type: Bug Reporter: Thomas Mueller When starting the sample app Hop 0 (or any other Hop sample app) if there is no repository directory, then the application doesn't exit because there is a non-daemon thread named pool-1-thread-1. -- This message is automatically

[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

[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

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

: jackrabbit-core Reporter: Thomas Mueller Assignee: Thomas Mueller Priority: Minor For systems where reading from /dev/random is very slow (so that the alternative seed algorithm is used), initializing the org.apache.jackrabbit.core.id.SeededSecureRandom singleton may

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

: Bug Components: clustering Reporter: Thomas Mueller Assignee: Thomas Mueller Session.refresh(..) is supposed to synchronize cluster changes, but this doesn't always happen, specially if the syncDelay is low. The reason is a wrong assumption in ClusterNode.sync

[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

-core Reporter: Thomas Mueller Assignee: Thomas Mueller Priority: Minor As seen in JCR-2695, the FileDataStore is slow on some file system. Some file operations such as File.exists() or File.isDirectory() can be replaced with try / catch, or by inspecting

[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

[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

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

Type: Bug Components: jackrabbit-core Affects Versions: 2.0.0 Reporter: Thomas Mueller Assignee: Thomas Mueller Priority: Minor Fix For: 2.2.0 If the repository is not closed, and a session is still logged in, then the process doesn't

[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

[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

[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

: Improvement Reporter: Thomas Mueller When closing a session twice the following warning is written to the log file: This session has already been closed. See the chained exception for a trace of where the session was closed. I think the second close() should simply be ignored

[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

[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

[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

[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

[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

Project: Jackrabbit Content Repository Issue Type: New Feature Components: jackrabbit-core Reporter: Thomas Mueller If a node points to a non-existing child node (which is a repository inconsistency), currently this child node is silently ignored for read

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

Mueller Assignee: Thomas Mueller When using PostgreSQL, the following warning appears in the log file: *WARN [org.apache.jackrabbit.core.util.db.ConnectionFactory] (main) Failed to guess validation query for URL jdbc:postgresql:... -- This message is automatically generated

[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

[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

[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

[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

[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

[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

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871530#action_12871530 ] Thomas Mueller commented on JCR-2640: - exposing implementation details through public

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871538#action_12871538 ] Thomas Mueller commented on JCR-2640: - our lives easier down the road if we want to go

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871546#action_12871546 ] Thomas Mueller commented on JCR-2640: - +0: I don't want to block this change, I just want

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871141#action_12871141 ] Thomas Mueller commented on JCR-2640: - I confess I don't understand what problem

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871158#action_12871158 ] Thomas Mueller commented on JCR-2640: - break the tight package-private coupling

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871167#action_12871167 ] Thomas Mueller commented on JCR-2640: - without having to expose Jackrabbit internals

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871183#action_12871183 ] Thomas Mueller commented on JCR-2640: - I see, Angela and Stefan don't like to make stuff

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

[ https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868123#action_12868123 ] Thomas Mueller commented on JCR-2396: - Was this patch applied to the 2.x line

[jira] Commented: (JCR-2618) Almost all application server threads were waiting for ReaderLock or WriterLock

[ https://issues.apache.org/jira/browse/JCR-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12865709#action_12865709 ] Thomas Mueller commented on JCR-2618: - ItemNotFoundException: failed to build path

[jira] Resolved: (JCR-2618) Almost all application server threads were waiting for ReaderLock or WriterLock

[ https://issues.apache.org/jira/browse/JCR-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2618. - Resolution: Cannot Reproduce Almost all application server threads were waiting for ReaderLock

[jira] Resolved: (JCR-2618) Almost all application server threads were waiting for ReaderLock or WriterLock

[ https://issues.apache.org/jira/browse/JCR-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2618. - Resolution: Cannot Reproduce From the stack trace, it doesn't look like a deadlock, it's just slow

[jira] Commented: (JCR-2619) improved internal representation of DATE values

[ https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861362#action_12861362 ] Thomas Mueller commented on JCR-2619: - a 64-bit long is quite enough Yes, if we

[jira] Commented: (JCR-2619) improved internal representation of DATE values

[ https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861383#action_12861383 ] Thomas Mueller commented on JCR-2619: - It should support all values that a Calendar

[jira] Commented: (JCR-2619) improved internal representation of DATE values

[ https://issues.apache.org/jira/browse/JCR-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861243#action_12861243 ] Thomas Mueller commented on JCR-2619: - You would need at least a long and an int

[jira] Deleted: (JCRTCK-20) shin

[ https://issues.apache.org/jira/browse/JCRTCK-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller deleted JCRTCK-20: - shin Key: JCRTCK-20 URL: https://issues.apache.org/jira

[jira] Resolved: (JCR-2592) javax.jcr.NodeIterator getsize always return -1

[ https://issues.apache.org/jira/browse/JCR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2592. - Resolution: Invalid Please use the user list for questions. javax.jcr.NodeIterator getsize

[jira] Resolved: (JCR-2583) Occasional testDataStoreGarbageCollection test failures

[ https://issues.apache.org/jira/browse/JCR-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2583. - Resolution: Fixed Maybe my change did fix the problem? Or it was not a problem within the test

[jira] Commented: (JCR-2583) Occasional testDataStoreGarbageCollection test failures

[ https://issues.apache.org/jira/browse/JCR-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849629#action_12849629 ] Thomas Mueller commented on JCR-2583: - Looking at the code, it seems the repository

[jira] Commented: (JCR-2584) Switch from log4j to Logback

[ https://issues.apache.org/jira/browse/JCR-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849651#action_12849651 ] Thomas Mueller commented on JCR-2584: - +1 I specially like the version information

[jira] Commented: (JCR-2450) UserManager inconsistency

[ https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846829#action_12846829 ] Thomas Mueller commented on JCR-2450: - This looks like a repository configuration problem

[jira] Commented: (JCR-2576) DbInputStream does not support mark()/reset() when exhausted.

[ https://issues.apache.org/jira/browse/JCR-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12846855#action_12846855 ] Thomas Mueller commented on JCR-2576: - Thanks a lot for the patch! I think the only

[jira] Resolved: (JCR-2576) DbInputStream does not support mark()/reset() when exhausted.

[ https://issues.apache.org/jira/browse/JCR-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2576. - Resolution: Fixed Fix Version/s: 2.0.1 DbInputStream does not support mark()/reset() when

[jira] Assigned: (JCR-2561) SQL2 query - supplying column selector fails with NPE on getColumnName()

[ https://issues.apache.org/jira/browse/JCR-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-2561: --- Assignee: Thomas Mueller SQL2 query - supplying column selector fails with NPE

[jira] Created: (JCR-2564) SQL2 query: QOMFormatter create incorrect NOT conditions

Components: jackrabbit-jcr-commons Reporter: Thomas Mueller Assignee: Thomas Mueller Then the following query is parsed: SELECT test.* FROM test WHERE (NOT test.name = 'Hello') AND test.id = 3 then the SQL statement generated, it becomes: SELECT test.* FROM test WHERE

[jira] Resolved: (JCR-2564) SQL2 query: QOMFormatter create incorrect NOT conditions

[ https://issues.apache.org/jira/browse/JCR-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2564. - Resolution: Fixed Fix Version/s: 2.0.1 SQL2 query: QOMFormatter create incorrect

[jira] Created: (JCR-2556) Data store garbage collection: log deleted files and total size

Type: Improvement Components: jackrabbit-core Reporter: Thomas Mueller Assignee: Thomas Mueller The data store garbage collection should list the names and the total size of all deleted files. -- This message is automatically generated by JIRA. - You can reply

[jira] Resolved: (JCR-2556) Data store garbage collection: log deleted files and total size

[ https://issues.apache.org/jira/browse/JCR-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2556. - Resolution: Fixed Fix Version/s: 2.1.0 Data store garbage collection: log deleted files

[jira] Commented: (JCR-2524) Reduce memory usage of DocIds

[ https://issues.apache.org/jira/browse/JCR-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12840074#action_12840074 ] Thomas Mueller commented on JCR-2524: - Caching the most recently used DocIds and reuse

<    5   6   7   8   9   10   11   12   13   14   >