[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 855 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#855)

Status: Still Failing

Check console output at 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/855/ to view 
the results.

Changes:
[tomekr] OAK-4273: Disable testConcurrentWithConflict on Derby

[angela] OAK-4302 : DefaultSyncContextTest contains duplicate test

[mduerig] OAK-3348: Cross gc sessions might introduce references to 
pre-compacted

[mduerig] OAK-3348: Cross gc sessions might introduce references to 
pre-compacted

[mduerig] OAK-3348: Cross gc sessions might introduce references to 
pre-compacted

[mduerig] OAK-3348: Cross gc sessions might introduce references to 
pre-compacted

[tomekr] OAK-4260 Implement migration from segment to segment-next

[mduerig] OAK-2833: Refactor TarMK Remove superfluous constructor

[mduerig] OAK-2833: Refactor TarMK Remove throws declaration from Javadoc for

[mduerig] OAK-2833: Refactor TarMK Proper string interpolation in logging 
(instead

[mduerig] OAK-2833: Refactor TarMK Simplify toString: not need for StringBuilder

[mduerig] OAK-2833: Refactor TarMK Make commitFairLock static and change to 
upper

[mduerig] OAK-2833: Refactor TarMK Remove unused field and methods. Rename 
method

[frm] OAK-4211 - Close the file and release the memory mapped buffer in

[frm] OAK-4304 - Delete temporary folders created by SegmentParserTest at the

[angela] OAK-4226 : Improve testing of DefaultSyncContext

[frm] OAK-4259 - Add a test fixture for the oak-segment-next module

[tripod] OAK-4048 [regression] SyncHandler.listIdentities() returns all users,

 

Test results:
3 tests failed.
FAILED:  
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.testProxyFlippedEndByteSSL

Error Message:
expected:<{ root = { ... } }> but was:<{ root : { } }>

Stack Trace:
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.useProxy(BrokenNetworkTest.java:143)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.testProxyFlippedEndByteSSL(BrokenNetworkTest.java:103)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 854 - Still Failing

[Apache Jenkins Server]

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build 
#854)

Status: Still Failing

Check console output at 
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/854/ to view 
the results.

Changes:
[tomekr] OAK-4273: Disable testConcurrentWithConflict on Derby

[davide] OAK-4272 - Release Oak 1.4.2

[davide] OAK-4136 - release profile in maven OAK-4148 - RAT plugin complains

[davide] OAK-4272 - Release Oak 1.4.2

[davide] [maven-release-plugin] prepare release jackrabbit-oak-1.4.2

[davide] [maven-release-plugin] prepare for next development iteration

[davide] OAK-4272 - Release Oak 1.4.2

 

Test results:
2 tests failed.
FAILED:  
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.testProxyFlippedStartByteSSL

Error Message:
expected:<{ root = { ... } }> but was:<{ root : { } }>

Stack Trace:
java.lang.AssertionError: expected:<{ root = { ... } }> but was:<{ root : { } }>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.useProxy(BrokenNetworkTest.java:143)
at 
org.apache.jackrabbit.oak.plugins.segment.standby.BrokenNetworkTest.testProxyFlippedStartByteSSL(BrokenNetworkTest.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


FAILED:  
org.apache.jackrabbit.oak.plugins.document.blob.RDBBlobStoreTest.testUpdateAndDelete[MyFixture:
 RDB-Derby(embedded)]

Error Message:
null

Stack Trace:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.jackrabbit.oak.plugins.document.blob.RDBBlobStoreTest.testUpdateAndDelete(RDBBlobStoreTest.java:187)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at 

Re: Oak 1.4.2 release plan

[Davide Giannella]

hello team,

spoke offline with members of the team and it seems that we had a couple
of issues there where not marked as blocker that would be way better to
have in 1.4.2.

Cancelled therefore the load and tags. Waiting for the issues to resolve.

Davide

On 22/04/2016 09:58, Davide Giannella wrote:
> Hello team,
>
> I'm planning to cut Oak 1.4.2 next Monday 25th April 2016.
>
> If there are any objections please let me know. Otherwise I will
> re-schedule any non-resolved issue for the next iteration.
>
> Thanks
> Davide
>
>
>

[ANNOUNCE] Apache Jackrabbit 2.2 deprecated

[Davide Giannella]

The Apache Jackrabbit Team has decided that since the 2.2 branch of the
project didn’t receive any activity since 2012 and looks like not being
used any more; to drop support and deprecate such version. Previous
branch, tags and releases will still be available for future references.

Regards
Davide

[VOTE] Please vote for the final name of oak-segment-next

[Michael Dürig]

Hi,

There is a couple of names that came up in the discussion [1]:

oak-local-store
oak-segment-file
oak-embedded-store
oak-segment-store
oak-segment-tar
oak-segment-next

Please vote which of the above six options you would like to see as the 
final name for oak-segment-next [2]:


Put +1 next to those names that you favour, put -1 to veto names and 
remove the remaining names. Please justify any veto as otherwise it is 
non binding.


The name with the most +1 votes and without any -1 vote will be chosen.

The vote is open for the next 72 hours.

Michael


[1] http://markmail.org/thread/ktk7szjxtucpqd2o
[2] https://issues.apache.org/jira/browse/OAK-4245

[jira] [Created] (JCR-3973) Deprecate Jackrabbit 2.2.x

[Davide Giannella (JIRA)]

Davide Giannella created JCR-3973:
-

 Summary: Deprecate Jackrabbit 2.2.x
 Key: JCR-3973
 URL: https://issues.apache.org/jira/browse/JCR-3973
 Project: Jackrabbit Content Repository
  Issue Type: Task
Reporter: Davide Giannella
Assignee: Davide Giannella


Deprecate the old jackrabbit 2.2.x by

- link will be removed from the download page
- news will be posted on the homepage
- [announce] will be sent to jr-user, jr-dev, oak-dev
- branch and tags WILL stay there

http://jackrabbit.markmail.org/thread/oopcxrk5q2xichaq



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3971:

Fix Version/s: 2.10.3
   2.8.2

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.8.2, 2.10.3, 2.12.2
>
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding resolved JCR-3971.
-
Resolution: Fixed

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.8.2, 2.10.3, 2.12.2
>
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding resolved JCR-3972.
-
Resolution: Fixed

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.8.2, 2.10.3, 2.12.2
>
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256235#comment-15256235
 ] 

Julian Sedding edited comment on JCR-3971 at 4/25/16 12:23 PM:
---

Fixed in trunk [r1740814|https://svn.apach.org/r1740814]. Original patch from 
[~baedke].

Merged to branches/2.10 in [r1740826|https://svn.apache.org/r1740826].
Merged to branches/2.8 in [r1740829|https://svn.apache.org/r1740829].


was (Author: jsedding):
Fixed in trunk [r1740814|https://svn.apach.org/r1740814]. Original patch from 
[~baedke].

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3972:

Fix Version/s: 2.10.3
   2.8.2

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.8.2, 2.10.3, 2.12.2
>
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256236#comment-15256236
 ] 

Julian Sedding edited comment on JCR-3972 at 4/25/16 12:23 PM:
---

Fixed in trunk [r1740815|https://svn.apach.org/r1740815]. Original patch from 
[~baedke].

Merged to branches/2.10 in [r1740828|https://svn.apache.org/r1740828].
Merged to branches/2.8 in [r1740831|https://svn.apache.org/r1740831].


was (Author: jsedding):
Fixed in trunk [r1740815|https://svn.apach.org/r1740815]. Original patch from 
[~baedke].

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3971:

Fix Version/s: 2.12.2

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3971:

Affects Version/s: 2.8.1
   2.10.2

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3972:

Fix Version/s: 2.12.2

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

 [ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Sedding updated JCR-3972:

Affects Version/s: 2.8.1
   2.10.2

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.8.1, 2.10.2, 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
> Fix For: 2.12.2
>
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256235#comment-15256235
 ] 

Julian Sedding commented on JCR-3971:
-

Fixed in trunk [r1740814|https://svn.apach.org/r1740814]. Original patch from 
[~baedke].

> Make read-permission cache-size in CompiledPermissionsImpl configurable
> ---
>
> Key: JCR-3971
> URL: https://issues.apache.org/jira/browse/JCR-3971
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
>
> Some use-cases require a larger read-permission cache size than the 
> hard-coded 5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

[ 
https://issues.apache.org/jira/browse/JCR-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256236#comment-15256236
 ] 

Julian Sedding commented on JCR-3972:
-

Fixed in trunk [r1740815|https://svn.apach.org/r1740815]. Original patch from 
[~baedke].

> Make size of ID-cache in CachingHierarchyManager configurable
> -
>
> Key: JCR-3972
> URL: https://issues.apache.org/jira/browse/JCR-3972
> Project: Jackrabbit Content Repository
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 2.12.1
>Reporter: Julian Sedding
>Assignee: Julian Sedding
>Priority: Minor
>
> Some use-cases require a larger ID cache to perform well than the hard-coded 
> 1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

adaptTo() 2016 - CfP & Earlybird & Recap

[Stefan Seifert]

Quick update for the adaptTo() 2016 conference in Berlin:

We decided to extend the Call for Papers deadline by 2 weeks (until 6th of 
May). http://adapt.to/cfp

Also, the Earlybird offer (-20%) ends this Friday. http://adapt.to/tickets

Feeling nostalgic? Check out our 2015 Recap. http://adobe.ly/1MCLKca

Kind regards on behalf of the adaptTo() Team

Stefan

adaptTo() 2016 - CfP & Earlybird & Recap

[Stefan Seifert]

Quick update for the adaptTo() 2016 conference in Berlin:

We decided to extend the Call for Papers deadline by 2 weeks (until 6th of 
May). http://adapt.to/cfp

Also, the Earlybird offer (-20%) ends this Friday. http://adapt.to/tickets

Feeling nostalgic? Check out our 2015 Recap. http://adobe.ly/1MCLKca

Kind regards on behalf of the adaptTo() Team

Stefan

Re: In search for a final name for oak-segment-next

[Davide Giannella]

On 22/04/2016 14:08, Francesco Mari wrote:
> As express offline, I would better choose a name that describes what the
> module does without leaking how the module works internally. My proposals
> are along the lines of "oak-local-store" and "oak-embedded-store". If
> having "segment" in the name is a major concern, I would opt for
> "oak-segment-store", as this name better describes what the module is
> supposed to be.

I like oak-segment-store if we want to express the "segment". If we want
to go on a more generic function oriented naming I prefer the
oak-embedded-store. The only caveat is that we, for any reason, come up
with another embedded store (which I don't think) to go along as option
with segment we could be in a small empass. Therefore I'd like
oak-segment-store.
>
> Since we are imagining the names of future NodeStore implementations, I
> find useless to have every first-level folder prefixed with "oak-". If I
> would lay out the project today, and assuming that our implementations
> would live in separate modules, I would opt for a structure like the
> following:
>
> /commons (oak-commons)
> /segment (oak-segment)
> /document/commons (oak-document-commons)
> /document/mongo (oak-document-mongo)
> /document/rdb (oak-document-rdb)
>
> Please note that I completely made up the names above to express my idea.

While I can agree on dropping the "oak" in first-level directories don't
really know if going for such restructure.

On both this and previous topic I don't have any strong opinions.

Davide

Re: Ability to Extend the SecurityProvideImpl Gone

[Angela Schreiber]

hi tyson

the 'SecurityProvideImpl' has been replaced by a more robust
approach that makes sure the 'SecurityProvider' on gets
registered as service once all mandatory security modules
are ready. this also allows assert that the repository
gets properly initialised.

you may find additional information in the following documentation
section:

http://jackrabbit.apache.org/oak/docs/security/introduction.html

the 'SecurityProviderRegistration' is key to the understanding of
security related OSGi setup, while the 'SecurityProvideImpl' only
remains in the code base for non-OSGi setups such as we have in the
unit tests.

hope that helps
angela


On 22/04/16 12:42, "Tyson Bowman"  wrote:

>Hi all
>I am trying to extend the SecurityProvider and PermissionProvider for a
>project and the code was working prior to them upgrading their oak
>version.
>After some investigation it appears that class was removed as a service
>and
>the registration class was added. There doesn't seem to be much
>documentation or explanation or this change and would love some advice or
>examples of how to ensure your security provider gets registered. Also
>there have been a few comments about this causing problems for others so
>hopefully this can be helpful for others as well.
>
>This change
>https://github.com/apache/jackrabbit-oak/commit/81614454d9b21977ad1930c714
>41ad8f577fe013#diff-8914e351c2be2e543280ae9c9ba54770
>
>
>Thanks
>
>Tyson

[jira] [Created] (JCR-3972) Make size of ID-cache in CachingHierarchyManager configurable

[Julian Sedding (JIRA)]

Julian Sedding created JCR-3972:
---

 Summary: Make size of ID-cache in CachingHierarchyManager 
configurable
 Key: JCR-3972
 URL: https://issues.apache.org/jira/browse/JCR-3972
 Project: Jackrabbit Content Repository
  Issue Type: Improvement
  Components: core
Affects Versions: 2.12.1
Reporter: Julian Sedding
Assignee: Julian Sedding
Priority: Minor


Some use-cases require a larger ID cache to perform well than the hard-coded 
1. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (JCR-3971) Make read-permission cache-size in CompiledPermissionsImpl configurable

[Julian Sedding (JIRA)]

Julian Sedding created JCR-3971:
---

 Summary: Make read-permission cache-size in 
CompiledPermissionsImpl configurable
 Key: JCR-3971
 URL: https://issues.apache.org/jira/browse/JCR-3971
 Project: Jackrabbit Content Repository
  Issue Type: Improvement
  Components: core
Affects Versions: 2.12.1
Reporter: Julian Sedding
Assignee: Julian Sedding
Priority: Minor


Some use-cases require a larger read-permission cache size than the hard-coded 
5000. This should be made configurable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)