[jira] [Commented] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236835#comment-15236835 ] Unico Hommes commented on JCR-3958: --- Committed fix to 2.12 branch in revision 1738734. >

[jira] [Resolved] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3958. --- Resolution: Fixed Fix Version/s: 2.13.0 > Endless loop until async upload completes > ---

[jira] [Commented] (JCR-3965) RepositoryStatistics is reset per second for bundle cache size which should not be the case for the bundle cache stats

[ https://issues.apache.org/jira/browse/JCR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236827#comment-15236827 ] Unico Hommes commented on JCR-3965: --- Fix committed in 2.12 branch in revision 1738732. Fix

[jira] [Resolved] (JCR-3965) RepositoryStatistics is reset per second for bundle cache size which should not be the case for the bundle cache stats

[ https://issues.apache.org/jira/browse/JCR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3965. --- Resolution: Fixed > RepositoryStatistics is reset per second for bundle cache size which should > not b

[jira] [Updated] (JCR-3965) RepositoryStatistics is reset per second for bundle cache size which should not be the case for the bundle cache stats

[ https://issues.apache.org/jira/browse/JCR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3965: -- Fix Version/s: 2.12.2 > RepositoryStatistics is reset per second for bundle cache size which should > not

[jira] [Updated] (JCR-3965) RepositoryStatistics is reset per second for bundle cache size which should not be the case for the bundle cache stats

[ https://issues.apache.org/jira/browse/JCR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3965: -- Fix Version/s: 2.13.0 > RepositoryStatistics is reset per second for bundle cache size which should > not

[jira] [Commented] (JCR-3965) RepositoryStatistics is reset per second for bundle cache size which should not be the case for the bundle cache stats

[ https://issues.apache.org/jira/browse/JCR-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236822#comment-15236822 ] Unico Hommes commented on JCR-3965: --- Fix committed to trunk in revision 1738730. > Reposi

[jira] [Commented] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232151#comment-15232151 ] Unico Hommes commented on JCR-3958: --- Committed fix to 2.10 branch in revision 1738242. >

[jira] [Commented] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232146#comment-15232146 ] Unico Hommes commented on JCR-3958: --- Hi [~shgupta] and [~takahito.kikuchi], Thanks for re

[jira] [Commented] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226194#comment-15226194 ] Unico Hommes commented on JCR-3958: --- [~takahito.kikuchi] I committed a fix. Can you take a

[jira] [Commented] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226190#comment-15226190 ] Unico Hommes commented on JCR-3958: --- fix committed to trunk in revision 1737832. > Endles

[jira] [Assigned] (JCR-3958) Endless loop until async upload completes

[ https://issues.apache.org/jira/browse/JCR-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes reassigned JCR-3958: - Assignee: Unico Hommes > Endless loop until async upload completes > --

[jira] [Commented] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224153#comment-15224153 ] Unico Hommes commented on JCR-3833: --- [~takahito.kikuchi] I sill have doubts that with this

[jira] [Commented] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223779#comment-15223779 ] Unico Hommes commented on JCR-3833: --- [~takahito.kikuchi] Because the iterator is indeed or

[jira] [Commented] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223358#comment-15223358 ] Unico Hommes commented on JCR-3833: --- [~takahito.kikuchi] One possible solution is to keep

[jira] [Commented] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223026#comment-15223026 ] Unico Hommes commented on JCR-3833: --- [~takahito.kikuchi] The problem is that once you have

[jira] [Commented] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221559#comment-15221559 ] Unico Hommes commented on JCR-3833: --- [~shgupta] A change in java.util.AbstractMap from whi

[jira] [Commented] (JCR-3905) Journal sync after full re-index does not save journal revision

[ https://issues.apache.org/jira/browse/JCR-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729185#comment-14729185 ] Unico Hommes commented on JCR-3905: --- It appears that creating the initial index and then c

[jira] [Commented] (JCR-2483) Out of memory error while adding a new host due to large number of revisions

[ https://issues.apache.org/jira/browse/JCR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729118#comment-14729118 ] Unico Hommes commented on JCR-2483: --- The problem with the patch is that it uses a SQL stat

[jira] [Resolved] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3902. --- Resolution: Fixed > NodeTypeDefDiff incorrectly handles multiple residual property definitions > ---

[jira] [Updated] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3902: -- Fix Version/s: (was: 2.10.3) 2.10.2 > NodeTypeDefDiff incorrectly handles multiple

[jira] [Comment Edited] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708054#comment-14708054 ] Unico Hommes edited comment on JCR-3902 at 8/22/15 2:57 PM: Fix

[jira] [Commented] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708054#comment-14708054 ] Unico Hommes commented on JCR-3902: --- Fix consists of using the same strategy to find the b

[jira] [Commented] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

[ https://issues.apache.org/jira/browse/JCR-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708053#comment-14708053 ] Unico Hommes commented on JCR-3902: --- Committed to trunk in revision 1697087. Committed to

[jira] [Created] (JCR-3902) NodeTypeDefDiff incorrectly handles multiple residual property definitions

Unico Hommes created JCR-3902: - Summary: NodeTypeDefDiff incorrectly handles multiple residual property definitions Key: JCR-3902 URL: https://issues.apache.org/jira/browse/JCR-3902 Project: Jackrabbit Co

[jira] [Updated] (JCR-3880) Allow to add/remove group members by ID

[ https://issues.apache.org/jira/browse/JCR-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3880: -- Fix Version/s: (was: 2.10.2) 2.11.0 > Allow to add/remove group members by ID > ---

[jira] [Updated] (JCR-3885) Extend set of Actions in JackrabbitSession to reflect other operations than regular read/write

[ https://issues.apache.org/jira/browse/JCR-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3885: -- Fix Version/s: (was: 2.10.2) 2.11.0 > Extend set of Actions in JackrabbitSession to

[jira] [Updated] (JCR-3894) Add PrincipalSetPolicy interface to Jackrabbit Security API

[ https://issues.apache.org/jira/browse/JCR-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3894: -- Fix Version/s: (was: 2.10.2) 2.11.0 > Add PrincipalSetPolicy interface to Jackrabbi

[jira] [Updated] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3888: -- Fix Version/s: 2.11.0 > Possible dead lock in SharedItemStateManager in clustered environment > --

[jira] [Updated] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3888: -- Fix Version/s: (was: 2.10.3) 2.10.2 > Possible dead lock in SharedItemStateManager

[jira] [Updated] (JCR-3860) Properly expose missing values in TimeSeries implementations

[ https://issues.apache.org/jira/browse/JCR-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3860: -- Fix Version/s: (was: 2.10.3) 2.10.2 > Properly expose missing values in TimeSeries

[jira] [Updated] (JCR-3863) org.apache.jackrabbit.api.observation should have its version incremented

[ https://issues.apache.org/jira/browse/JCR-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3863: -- Fix Version/s: (was: 2.10.3) > org.apache.jackrabbit.api.observation should have its version increment

[jira] [Updated] (JCR-3863) org.apache.jackrabbit.api.observation should have its version incremented

[ https://issues.apache.org/jira/browse/JCR-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3863: -- Fix Version/s: 2.10.2 > org.apache.jackrabbit.api.observation should have its version incremented > --

[jira] [Commented] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655177#comment-14655177 ] Unico Hommes commented on JCR-3888: --- Committed to trunk in revision 1694169. > Possible d

[jira] [Resolved] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3888. --- Resolution: Fixed > Possible dead lock in SharedItemStateManager in clustered environment >

[jira] [Commented] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655034#comment-14655034 ] Unico Hommes commented on JCR-3888: --- It's like I thought, the fix reveals a bug somewhere

[jira] [Commented] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653652#comment-14653652 ] Unico Hommes commented on JCR-3888: --- This deadlock is quite serious. Might want to hold of

[jira] [Updated] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3888: -- Description: When using clustering SharedItemStateManager#Update#begin sets a lock on the database (line

[jira] [Created] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

Unico Hommes created JCR-3888: - Summary: Possible dead lock in SharedItemStateManager in clustered environment Key: JCR-3888 URL: https://issues.apache.org/jira/browse/JCR-3888 Project: Jackrabbit Content

[jira] [Commented] (JCR-3888) Possible dead lock in SharedItemStateManager in clustered environment

[ https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597452#comment-14597452 ] Unico Hommes commented on JCR-3888: --- Fix committed to trunk in revision 1687018. > Possib

[jira] [Commented] (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR

[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531187#comment-14531187 ] Unico Hommes commented on JCR-2598: --- Hi Sam, The validateHierarchy flag checks the consist

[jira] [Commented] (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR

[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526806#comment-14526806 ] Unico Hommes commented on JCR-2598: --- You mentioned version 2.6.2 before. Is that the versi

[jira] [Commented] (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR

[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526658#comment-14526658 ] Unico Hommes commented on JCR-2598: --- Hi Sam, I can't think of a way to test that. Did you

[jira] [Commented] (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR

[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526621#comment-14526621 ] Unico Hommes commented on JCR-2598: --- Hi [~stanges], Several bugs in this area have been i

[jira] [Resolved] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3814. --- Resolution: Fixed > IllegalStateException in LockManager#unlock > --

[jira] [Reopened] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes reopened JCR-3814: --- > IllegalStateException in LockManager#unlock > --- > >

[jira] [Resolved] (JCR-3840) NodeTypeDefDiff does not take same-name child type definitions into account

[ https://issues.apache.org/jira/browse/JCR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3840. --- Resolution: Fixed > NodeTypeDefDiff does not take same-name child type definitions into account > --

[jira] [Updated] (JCR-3840) NodeTypeDefDiff does not take same-name child type definitions into account

[ https://issues.apache.org/jira/browse/JCR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3840: -- Fix Version/s: 2.9.1 2.8.1 2.6.6 > NodeTypeDefDiff does not take sam

[jira] [Updated] (JCR-3840) NodeTypeDefDiff does not take same-name child type definitions into account

[ https://issues.apache.org/jira/browse/JCR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3840: -- Description: The following is a legal cnd, accepted both by jackrabbit, and not prohibited by the JCR spe

[jira] [Updated] (JCR-3840) NodeTypeDefDiff does not take same-name child type definitions into account

[ https://issues.apache.org/jira/browse/JCR-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3840: -- Summary: NodeTypeDefDiff does not take same-name child type definitions into account (was: ChildTypeDefDi

[jira] [Created] (JCR-3840) ChildTypeDefDiff does not take same-name child type definitions into account

Unico Hommes created JCR-3840: - Summary: ChildTypeDefDiff does not take same-name child type definitions into account Key: JCR-3840 URL: https://issues.apache.org/jira/browse/JCR-3840 Project: Jackrabbit

[jira] [Resolved] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3833. --- Resolution: Fixed > Compatibility with Java 8 > - > > Key: JCR-3

[jira] [Updated] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3833: -- Fix Version/s: 2.9.1 2.8.1 > Compatibility with Java 8 > - > >

[jira] [Resolved] (JCR-3525) Enable consistency checker to run in fix mode in a live cluster

[ https://issues.apache.org/jira/browse/JCR-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3525. --- Resolution: Fixed Fix Version/s: 2.8 Assignee: (was: Unico Hommes) > Enable consiste

[jira] [Updated] (JCR-3834) DecimalField calculates wrong string from BigDecimal with scale of Integer.MIN_VALUE

[ https://issues.apache.org/jira/browse/JCR-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3834: -- Assignee: (was: Unico Hommes) > DecimalField calculates wrong string from BigDecimal with scale of >

[jira] [Updated] (JCR-3835) Overwriting Cache Entry Warnings on Java 8

[ https://issues.apache.org/jira/browse/JCR-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3835: -- Assignee: (was: Unico Hommes) > Overwriting Cache Entry Warnings on Java 8 > -

[jira] [Commented] (JCR-3834) DecimalField calculates wrong string from BigDecimal with scale of Integer.MIN_VALUE

[ https://issues.apache.org/jira/browse/JCR-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236731#comment-14236731 ] Unico Hommes commented on JCR-3834: --- Committed test case and skipping DecimalConvertTest#t

[jira] [Commented] (JCR-3835) Overwriting Cache Entry Warnings on Java 8

[ https://issues.apache.org/jira/browse/JCR-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236730#comment-14236730 ] Unico Hommes commented on JCR-3835: --- Added test ReplacePropertyWhileOthersReadTest to list

[jira] [Updated] (JCR-3835) Overwriting Cache Entry Warnings on Java 8

[ https://issues.apache.org/jira/browse/JCR-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3835: -- Description: The test ReplacePropertyWhileOthersReadTest sometimes fails on Java 8 because of such warning

[jira] [Assigned] (JCR-3835) Overwriting Cache Entry Warnings on Java 8

[ https://issues.apache.org/jira/browse/JCR-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes reassigned JCR-3835: - Assignee: Unico Hommes > Overwriting Cache Entry Warnings on Java 8 > -

[jira] [Assigned] (JCR-3834) DecimalField calculates wrong string from BigDecimal with scale of Integer.MIN_VALUE

[ https://issues.apache.org/jira/browse/JCR-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes reassigned JCR-3834: - Assignee: Unico Hommes > DecimalField calculates wrong string from BigDecimal with scale of > Inte

[jira] [Created] (JCR-3835) Overwriting Cache Entry Warnings on Java 8

Unico Hommes created JCR-3835: - Summary: Overwriting Cache Entry Warnings on Java 8 Key: JCR-3835 URL: https://issues.apache.org/jira/browse/JCR-3835 Project: Jackrabbit Content Repository Issue

[jira] [Created] (JCR-3834) DecimalField calculates wrong string from BigDecimal with scale of Integer.MIN_VALUE

Unico Hommes created JCR-3834: - Summary: DecimalField calculates wrong string from BigDecimal with scale of Integer.MIN_VALUE Key: JCR-3834 URL: https://issues.apache.org/jira/browse/JCR-3834 Project: Jac

[jira] [Updated] (JCR-3833) Compatibility with Java 8

[ https://issues.apache.org/jira/browse/JCR-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3833: -- Fix Version/s: (was: 2.9.1) (was: 2.8.1) (was: 2.6.6) >

[jira] [Created] (JCR-3833) Compatibility with Java 8

Unico Hommes created JCR-3833: - Summary: Compatibility with Java 8 Key: JCR-3833 URL: https://issues.apache.org/jira/browse/JCR-3833 Project: Jackrabbit Content Repository Issue Type: Task

[jira] [Resolved] (JCR-3821) SeededSecureRandom thread can prevent Jackrabbit from shutting down

[ https://issues.apache.org/jira/browse/JCR-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3821. --- Resolution: Fixed > SeededSecureRandom thread can prevent Jackrabbit from shutting down > --

[jira] [Commented] (JCR-3821) SeededSecureRandom thread can prevent Jackrabbit from shutting down

[ https://issues.apache.org/jira/browse/JCR-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172288#comment-14172288 ] Unico Hommes commented on JCR-3821: --- Committed fix on branch 2.6 in revision 1631997. > S

[jira] [Commented] (JCR-3821) SeededSecureRandom thread can prevent Jackrabbit from shutting down

[ https://issues.apache.org/jira/browse/JCR-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172286#comment-14172286 ] Unico Hommes commented on JCR-3821: --- Committed fix on branch 2.8 in revision 1631996. > S

[jira] [Commented] (JCR-3821) SeededSecureRandom thread can prevent Jackrabbit from shutting down

[ https://issues.apache.org/jira/browse/JCR-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172283#comment-14172283 ] Unico Hommes commented on JCR-3821: --- Committed fix on trunk in revision 1631995. > Seeded

[jira] [Created] (JCR-3821) SeededSecureRandom thread can prevent Jackrabbit from shutting down

Unico Hommes created JCR-3821: - Summary: SeededSecureRandom thread can prevent Jackrabbit from shutting down Key: JCR-3821 URL: https://issues.apache.org/jira/browse/JCR-3821 Project: Jackrabbit Content R

[jira] [Resolved] (JCR-3818) Use SimpleFSDirectory by default

[ https://issues.apache.org/jira/browse/JCR-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3818. --- Resolution: Fixed > Use SimpleFSDirectory by default > > >

[jira] [Commented] (JCR-3818) Use SimpleFSDirectory by default

[ https://issues.apache.org/jira/browse/JCR-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170631#comment-14170631 ] Unico Hommes commented on JCR-3818: --- Committed to 2.8 branch in revision 1631659. > Use S

[jira] [Commented] (JCR-3818) Use SimpleFSDirectory by default

[ https://issues.apache.org/jira/browse/JCR-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170630#comment-14170630 ] Unico Hommes commented on JCR-3818: --- Committed to trunk in revision 1631658. > Use Simple

[jira] [Created] (JCR-3818) Use SimpleFSDirectory by default

Unico Hommes created JCR-3818: - Summary: Use SimpleFSDirectory by default Key: JCR-3818 URL: https://issues.apache.org/jira/browse/JCR-3818 Project: Jackrabbit Content Repository Issue Type: Impr

[jira] [Updated] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3814: -- Fix Version/s: 2.9 > IllegalStateException in LockManager#unlock > ---

[jira] [Resolved] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3814. --- Resolution: Fixed > IllegalStateException in LockManager#unlock > --

[jira] [Commented] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164986#comment-14164986 ] Unico Hommes commented on JCR-3814: --- fix committed to 2.6 branch in revision 1630366. > I

[jira] [Commented] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164985#comment-14164985 ] Unico Hommes commented on JCR-3814: --- fix committed to 2.8 branch in revision 1630365. > I

[jira] [Commented] (JCR-3814) IllegalStateException in LockManager#unlock

[ https://issues.apache.org/jira/browse/JCR-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164982#comment-14164982 ] Unico Hommes commented on JCR-3814: --- fix committed to trunk in revision 1630363. > Illega

[jira] [Created] (JCR-3814) IllegalStateException in LockManager#unlock

Unico Hommes created JCR-3814: - Summary: IllegalStateException in LockManager#unlock Key: JCR-3814 URL: https://issues.apache.org/jira/browse/JCR-3814 Project: Jackrabbit Content Repository Issue

[jira] [Resolved] (JCR-3811) AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3811. --- Resolution: Fixed > AppendRecord should allow reattempting database insertions of journal records > sho

[jira] [Commented] (JCR-3811) AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137155#comment-14137155 ] Unico Hommes commented on JCR-3811: --- Fixed on trunk in revision 1625518. Fixed on branch 2

[jira] [Updated] (JCR-3811) AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3811: -- Fix Version/s: 2.9 2.8.1 2.6.6 > AppendRecord should allow reattempt

[jira] [Updated] (JCR-3811) AppendRecord should allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3811: -- Summary: AppendRecord should allow reattempting database insertions of journal records should the initial

[jira] [Updated] (JCR-3811) AppendRecord should use TempFileInputStream to allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3811: -- Affects Version/s: 2.6.5 2.9 2.8. > AppendRecord should use

[jira] [Created] (JCR-3811) AppendRecord should use TempFileInputStream to allow reattempting database insertions of journal records should the initial attempt fail

Unico Hommes created JCR-3811: - Summary: AppendRecord should use TempFileInputStream to allow reattempting database insertions of journal records should the initial attempt fail Key: JCR-3811 URL: https://issues.apac

[jira] [Assigned] (JCR-3811) AppendRecord should use TempFileInputStream to allow reattempting database insertions of journal records should the initial attempt fail

[ https://issues.apache.org/jira/browse/JCR-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes reassigned JCR-3811: - Assignee: Unico Hommes > AppendRecord should use TempFileInputStream to allow reattempting database

[jira] [Resolved] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

[ https://issues.apache.org/jira/browse/JCR-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3809. --- Resolution: Fixed > ConnectionHelper swallows exception when it fails to reset binary streams > after a

[jira] [Commented] (JCR-3810) StreamWrapper can attempt to reset other types of InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135554#comment-14135554 ] Unico Hommes commented on JCR-3810: --- Fixed in branch 2.6 in revision 1625323. > StreamWra

[jira] [Updated] (JCR-3810) StreamWrapper can attempt to reset other types of InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3810: -- Fix Version/s: 2.9.1 2.8.1 2.6.6 > StreamWrapper can attempt to rese

[jira] [Resolved] (JCR-3810) StreamWrapper can attempt to reset other types of InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes resolved JCR-3810. --- Resolution: Fixed > StreamWrapper can attempt to reset other types of InputStreams > ---

[jira] [Commented] (JCR-3810) StreamWrapper can attempt to reset plain InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135550#comment-14135550 ] Unico Hommes commented on JCR-3810: --- Fixed in 2.8 branch in revision 1625322. > StreamWra

[jira] [Updated] (JCR-3810) StreamWrapper can attempt to reset other types of InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3810: -- Summary: StreamWrapper can attempt to reset other types of InputStreams (was: StreamWrapper can attempt t

[jira] [Commented] (JCR-3810) StreamWrapper can attempt to reset plain InputStreams

[ https://issues.apache.org/jira/browse/JCR-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135543#comment-14135543 ] Unico Hommes commented on JCR-3810: --- Fixed in trunk in revision 1625321. > StreamWrapper

[jira] [Created] (JCR-3810) StreamWrapper can attempt to reset plain InputStreams

Unico Hommes created JCR-3810: - Summary: StreamWrapper can attempt to reset plain InputStreams Key: JCR-3810 URL: https://issues.apache.org/jira/browse/JCR-3810 Project: Jackrabbit Content Repository

[jira] [Commented] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

[ https://issues.apache.org/jira/browse/JCR-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135453#comment-14135453 ] Unico Hommes commented on JCR-3809: --- Fixed in 2.6 branch in revision 1625284. > Connectio

[jira] [Updated] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

[ https://issues.apache.org/jira/browse/JCR-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Unico Hommes updated JCR-3809: -- Fix Version/s: 2.9.1 2.8.1 2.6.6 > ConnectionHelper swallows excepti

[jira] [Commented] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

[ https://issues.apache.org/jira/browse/JCR-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135442#comment-14135442 ] Unico Hommes commented on JCR-3809: --- Fixed in 2.8 branch on revision 1625281. > Connectio

[jira] [Commented] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

[ https://issues.apache.org/jira/browse/JCR-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135436#comment-14135436 ] Unico Hommes commented on JCR-3809: --- Fixed in trunk in revision 1625277. > ConnectionHelp

[jira] [Created] (JCR-3809) ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution

Unico Hommes created JCR-3809: - Summary: ConnectionHelper swallows exception when it fails to reset binary streams after a failed SQL statement execution Key: JCR-3809 URL: https://issues.apache.org/jira/browse/JCR-38

  1   2   3   >