[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-tabpanel&focusedCommentId=12921378#action_12921378 ] Thomas Mueller commented on JCR-2786: - The easiest solution is to call syncCount++ before

[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] 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: jackrabbit-c

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

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

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

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

[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-tabpanel&focusedCommentId=12917912#action_12917912 ] Thomas Mueller commented on JCR-2760: - +1 looks good to me for Jackrabbit 2.x. I think f

[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-tabpanel&focusedCommentId=12916051#action_12916051 ] Thomas Mueller commented on JCR-2760: - I'm not sure if this is really a big problem, so t

[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) Sleep in possibly endless loop in ObservationDispatcher

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

[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 Observa

[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] 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 revi

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

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

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

Deadlock in DefaultISMLocking - Key: JCR-2753 URL: https://issues.apache.org/jira/browse/JCR-2753 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Reporter:

[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] 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] Commented: (JCR-2746) Deadlock caused by ObservationDispatcher

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

[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 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-tabpanel&focusedCommentId=12912477#action_12912477 ] Thomas Mueller commented on JCR-2746: - There seems to be a bug in DefaultISMLocking: 1)

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

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

[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-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-tabpanel&focusedCommentId=1291#action_1291 ] Thomas Mueller commented on JCR-2749: - Thanks for fixing the root cause of the problem!

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=12909670#action_12909670 ] Thomas Mueller commented on JCR-2749: - I don't think the problem only occurs with Transie

[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 t

[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-tabpanel&focusedCommentId=12909667#action_12909667 ] Thomas Mueller commented on JCR-2749: - If we do really want a warning in the log (which I

[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-tabpanel&focusedCommentId=12909660#action_12909660 ] Thomas Mueller commented on JCR-2749: - The warning (with stack trace) is even logged if t

[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] 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: Im

[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] Resolved: (JCR-2704) Wrong SQL-2 parsing

[ https://issues.apache.org/jira/browse/JCR-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2704. - Resolution: Duplicate It looks like a duplicate of JCR-2564 > Wrong SQL-2 parsing > --

[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] 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 M

[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-tabpanel&focusedCommentId=12899332#action_12899332 ] Thomas Mueller commented on JCR-2686: - Hi, You are right. Looking at the code, I'm not s

[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] 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-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] 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-tabpanel&focusedCommentId=12893130#action_12893130 ] Thomas Mueller commented on JCR-2688: - That about a test dependency? > Provide utility f

[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-tabpanel&focusedCommentId=12893130#action_12893130 ] Thomas Mueller edited comment on JCR-2688 at 7/28/10 6:27 AM: -- I

[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-tabpanel&focusedCommentId=12892329#action_12892329 ] Thomas Mueller commented on JCR-2686: - Could you check if calling close() does what you w

[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-tabpanel&focusedCommentId=12892309#action_12892309 ] Thomas Mueller commented on JCR-2682: - Hi, Thanks for the patch! It it short, and easy t

[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 c

[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 h

[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-tabpanel&focusedCommentId=12892254#action_12892254 ] Thomas Mueller commented on JCR-2685: - Hi, Thanks for the patch! It looks good (well, it

[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-tabpanel&focusedCommentId=12890217#action_12890217 ] Thomas Mueller commented on JCR-2677: - > Ah, I get the problem... copy-methods() via stre

[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-tabpanel&focusedCommentId=12889806#action_12889806 ] Thomas Mueller commented on JCR-2677: - > 2. The temp file is moved to the permanent targe

[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-tabpanel&focusedCommentId=12889788#action_12889788 ] Thomas Mueller commented on JCR-2677: - That would be a nice feature. With WORM media you

[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] 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 setLastModif

[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-tabpanel&focusedCommentId=12888769#action_12888769 ] Thomas Mueller commented on JCR-2674: - Thanks a lot for the patch! It is now committed (i

[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-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-tabpanel&focusedCommentId=12888328#action_12888328 ] Thomas Mueller commented on JCR-2673: - Could you provide more information please, if poss

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

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

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

[ https://issues.apache.org/jira/browse/JCR-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=12871530#action_12871530 ] Thomas Mueller commented on JCR-2640: - > exposing implementation details through public m

[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-tabpanel&focusedCommentId=12871183#action_12871183 ] Thomas Mueller commented on JCR-2640: - I see, Angela and Stefan don't like to make stuff

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

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

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

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

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

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

[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-tabpanel&focusedCommentId=12868123#action_12868123 ] Thomas Mueller commented on JCR-2396: - > Was this patch applied to the 2.x line? No, th

[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 or

[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-tabpanel&focusedCommentId=12865709#action_12865709 ] Thomas Mueller commented on JCR-2618: - > ItemNotFoundException: failed to build path of .

[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-tabpanel&focusedCommentId=12861383#action_12861383 ] Thomas Mueller commented on JCR-2619: - > It should support all values that a Calendar obj

[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-tabpanel&focusedCommentId=12861362#action_12861362 ] Thomas Mueller commented on JCR-2619: - > a 64-bit long is quite enough Yes, if we restri

[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-tabpanel&focusedCommentId=12861243#action_12861243 ] Thomas Mueller commented on JCR-2619: - You would need at least a long and an int to repre

[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 alwa

[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 cas

[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-tabpanel&focusedCommentId=12849651#action_12849651 ] Thomas Mueller commented on JCR-2584: - +1 I specially like the "version information" h

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

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

[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] 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-tabpanel&focusedCommentId=12846855#action_12846855 ] Thomas Mueller commented on JCR-2576: - Thanks a lot for the patch! I think the only remai

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

[ https://issues.apache.org/jira/browse/JCR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2450. - Resolution: Not A Problem Closing as "not a problem". Please re-open if the problem persists. > Us

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

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

[jira] Assigned: (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 reassigned JCR-2576: --- Assignee: Thomas Mueller > DbInputStream does not support mark()/reset() when exhausted. >

[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 NOT condi

[jira] Resolved: (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 resolved JCR-2561. - Resolution: Fixed Fix Version/s: 2.0.1 > SQL2 query - supplying column selector fails with N

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

SQL2 query: QOMFormatter create incorrect NOT conditions Key: JCR-2564 URL: https://issues.apache.org/jira/browse/JCR-2564 Project: Jackrabbit Content Repository Issue Type: Bug

[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 on getColumnNa

[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 an

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

Data store garbage collection: log deleted files and total size --- Key: JCR-2556 URL: https://issues.apache.org/jira/browse/JCR-2556 Project: Jackrabbit Content Repository Issue Ty

[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-tabpanel&focusedCommentId=12840074#action_12840074 ] Thomas Mueller commented on JCR-2524: - > Caching the most recently used DocIds and reuse

[jira] Commented: (JCR-2492) Garbage Collector remove data for active node

[ https://issues.apache.org/jira/browse/JCR-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834242#action_12834242 ] Thomas Mueller commented on JCR-2492: - Hi, I think your are right. I have added a commen

[jira] Commented: (JCR-1414) Data store garbage collection: inUse not correctly synchronized

[ https://issues.apache.org/jira/browse/JCR-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834241#action_12834241 ] Thomas Mueller commented on JCR-1414: - Revision 633844 also fixed a bug in BundleDbPersis

[jira] Resolved: (JCR-2492) Garbage Collector remove data for active node

[ https://issues.apache.org/jira/browse/JCR-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2492. - Resolution: Fixed There are other problems with version 1.4.x, see also JCR-1414 and specially JCR

[jira] Commented: (JCR-2063) FileDataStore: garbage collection can delete files that are still needed

[ https://issues.apache.org/jira/browse/JCR-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834216#action_12834216 ] Thomas Mueller commented on JCR-2063: - A workaround for implementations where this is not

[jira] Commented: (JCR-2493) Unit tests for persistence managers

[ https://issues.apache.org/jira/browse/JCR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834142#action_12834142 ] Thomas Mueller commented on JCR-2493: - With the H2 database, changing the database URL is

[jira] Commented: (JCR-2493) Unit tests for persistence managers

[ https://issues.apache.org/jira/browse/JCR-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834116#action_12834116 ] Thomas Mueller commented on JCR-2493: - To speed up the test, I will try to change the tes

[jira] Resolved: (JCR-2492) Garbage Collector remove data for active node

[ https://issues.apache.org/jira/browse/JCR-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2492. - Resolution: Cannot Reproduce I can not reproduce this problem. Please see: http://wiki.apache.org/j

[jira] Commented: (JCR-2482) Reduce number of compiler warning by adding @Override and generics where appropriate

[ https://issues.apache.org/jira/browse/JCR-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829071#action_12829071 ] Thomas Mueller commented on JCR-2482: - Ok, then I will use @Override as well. (But not 'f

[jira] Commented: (JCR-2482) Reduce number of compiler warning by adding @Override and generics where appropriate

[ https://issues.apache.org/jira/browse/JCR-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828981#action_12828981 ] Thomas Mueller commented on JCR-2482: - I'm wondering if it's really worth adding all thos

[jira] Commented: (JCR-2479) Adding a Mixin-type with mandatory properties after setting these properties throws exception

[ https://issues.apache.org/jira/browse/JCR-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805469#action_12805469 ] Thomas Mueller commented on JCR-2479: - For me, it is a bit strange that the mixing needs

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

Log / trace wrapper: upgrade to JCR API 2.0 --- Key: JCR-2477 URL: https://issues.apache.org/jira/browse/JCR-2477 Project: Jackrabbit Content Repository Issue Type: Improvement Components: sa

[jira] Commented: (JCR-2449) Slow performance due to JCR-2138 (Prevent persistence of faulty back-references)

[ https://issues.apache.org/jira/browse/JCR-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802773#action_12802773 ] Thomas Mueller commented on JCR-2449: - Hi Martijn, Thanks for your help. It's good to kn

[jira] Resolved: (JCR-2449) Slow performance due to JCR-2138 (Prevent persistence of faulty back-references)

[ https://issues.apache.org/jira/browse/JCR-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-2449. - Resolution: Fixed Fix Version/s: 2.0.0 Assignee: Thomas Mueller > Slow performance

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