[jira] [Created] (OAK-8625) oak-ugrade leaks empty test folders

2019-09-13 Thread Julian Reschke (Jira)
Julian Reschke created OAK-8625:
---

 Summary: oak-ugrade leaks empty test folders
 Key: OAK-8625
 URL: https://issues.apache.org/jira/browse/OAK-8625
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: upgrade
Reporter: Julian Reschke


This is because of using {{com.google.common.io.Files#createTempDir()}} without 
cleanup up afterwards.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8621) Build Jackrabbit Oak #2377 failed

2019-09-13 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929254#comment-16929254
 ] 

Hudson commented on OAK-8621:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#2379|https://builds.apache.org/job/Jackrabbit%20Oak/2379/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/2379/console]

> Build Jackrabbit Oak #2377 failed
> -
>
> Key: OAK-8621
> URL: https://issues.apache.org/jira/browse/OAK-8621
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #2377 has failed.
> First failed run: [Jackrabbit Oak 
> #2377|https://builds.apache.org/job/Jackrabbit%20Oak/2377/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2377/console]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OAK-8529) Deregister MBeans on SecurityProviderRegistration component deactivation

2019-09-13 Thread Robert Munteanu (Jira)


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

Robert Munteanu updated OAK-8529:
-
Summary: Deregister MBeans on SecurityProviderRegistration component 
deactivation   (was: Eagerly deregister MBeans on SecurityProviderRegistration 
deactivation)

> Deregister MBeans on SecurityProviderRegistration component deactivation 
> -
>
> Key: OAK-8529
> URL: https://issues.apache.org/jira/browse/OAK-8529
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: security
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: 1.18.0
>
>
> The SecurityProviderRegistration is prone to being activated and deactivated 
> during a regular Sling application startup ( for a prolonged discussion see 
> SLING-7811 ). The instance should fully cleanup after itself to make sure it 
> will be usable after an activate/deactive cycle.
> In practice the MBeans remain registered and prevent a further registration 
> with errors such as
> {noformat}6.08.2019 09:43:51.051 *ERROR* [CM Event Dispatcher (Fire 
> ConfigurationEvent: 
> pid=org.apache.jackrabbit.oak.security.authentication.AuthenticationConfigurationImpl)]
>  org.apache.aries.jmx.whiteboard.MBeanHolder register: Failure registering 
> MBean 
> org.apache.aries.jmx.util.shared.RegistrableStandardEmitterMBean@45011485 
> javax.management.InstanceAlreadyExistsException: 
> org.apache.jackrabbit.oak:name=LoginModule statistics,type=LoginModuleStats
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.aries.jmx.whiteboard.MBeanHolder.register(MBeanHolder.java:114)
> at 
> org.apache.aries.jmx.whiteboard.JmxWhiteboardSupport.registerMBean(JmxWhiteboardSupport.java:88)
> at 
> org.apache.aries.jmx.whiteboard.Activator$MBeanTracker.addingService(Activator.java:102)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
> at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
> at 
> org.apache.jackrabbit.oak.osgi.OsgiWhiteboard.register(OsgiWhiteboard.java:79)
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:115)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:99)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration.maybeRegister(SecurityProviderRegistration.java:539)
> at 
> org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration.activate(SecurityProviderRegistration.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> 

[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)


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

Julian Reschke updated OAK-8624:

Issue Type: Bug  (was: Task)

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)


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

Julian Reschke updated OAK-8624:

Priority: Minor  (was: Major)

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Minor
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)


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

Julian Reschke updated OAK-8624:

Attachment: OAK-8624.diff

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929187#comment-16929187
 ] 

Julian Reschke commented on OAK-8624:
-

Proposed change:  [^OAK-8624.diff] 

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
> Attachments: OAK-8624.diff
>
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)


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

Julian Reschke updated OAK-8624:

Description: 
This is because {{MapDBMapFactory}} is backed by temporary DB, but that one is 
never closed.

Fix:

- make it {{closeable}}
- adapt test case and use in {{RecoveryCommand}}

However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
never resets it. Thus, if the factory is indeed closed, subsequent tests will 
fail. So, in {{RecoveryCommand}}, restore the default factory when done.

> oak-run: tests leak mapd temp files
> ---
>
> Key: OAK-8624
> URL: https://issues.apache.org/jira/browse/OAK-8624
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: run
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> This is because {{MapDBMapFactory}} is backed by temporary DB, but that one 
> is never closed.
> Fix:
> - make it {{closeable}}
> - adapt test case and use in {{RecoveryCommand}}
> However, {{RecoveryCommand}} sets the {{MapFactory}} instance globally, and 
> never resets it. Thus, if the factory is indeed closed, subsequent tests will 
> fail. So, in {{RecoveryCommand}}, restore the default factory when done.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OAK-8624) oak-run: tests leak mapd temp files

2019-09-13 Thread Julian Reschke (Jira)
Julian Reschke created OAK-8624:
---

 Summary: oak-run: tests leak mapd temp files
 Key: OAK-8624
 URL: https://issues.apache.org/jira/browse/OAK-8624
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: run
Reporter: Julian Reschke
Assignee: Julian Reschke






--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8621) Build Jackrabbit Oak #2377 failed

2019-09-13 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929174#comment-16929174
 ] 

Hudson commented on OAK-8621:
-

Previously failing build now is OK.
 Passed run: [Jackrabbit Oak 
#2378|https://builds.apache.org/job/Jackrabbit%20Oak/2378/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/2378/console]

> Build Jackrabbit Oak #2377 failed
> -
>
> Key: OAK-8621
> URL: https://issues.apache.org/jira/browse/OAK-8621
> Project: Jackrabbit Oak
>  Issue Type: Bug
>  Components: continuous integration
>Reporter: Hudson
>Priority: Major
>
> No description is provided
> The build Jackrabbit Oak #2377 has failed.
> First failed run: [Jackrabbit Oak 
> #2377|https://builds.apache.org/job/Jackrabbit%20Oak/2377/] [console 
> log|https://builds.apache.org/job/Jackrabbit%20Oak/2377/console]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Updated] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.

2019-09-13 Thread Thomas Mueller (Jira)


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

Thomas Mueller updated OAK-8245:

Fix Version/s: 1.18.0

> Add column for explained "statement" to "explain" Query result, next to 
> 'plan' column.
> --
>
> Key: OAK-8245
> URL: https://issues.apache.org/jira/browse/OAK-8245
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Affects Versions: 1.12.0, 1.8.12, 1.10.2
>Reporter: Mark Adamcin
>Assignee: Thomas Mueller
>Priority: Minor
> Fix For: 1.18.0
>
>
> The "explain" behavior of the core Query is very useful for helping to debug 
> JCR query execution planning. For xpath queries, the resulting "plan" column 
> refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 
> statement for execution. This SQL2 statement should be exposed through the 
> same API as the "plan", by way of an additional column named "statement" in 
> the single result row. 
> At this time, this underlying SQL2 statement is inaccessible to users of the 
> JCR Query interface, which can only provide the original XPath statement.
> To access the converted SQL2 statement, a class targeting the JCR API must 
> implement a regular expression match against a log stream retrieved via slf4j 
> MDC.
> This facility is not very portable, and an effective pattern on one version 
> of Oak may not be effective on a different version of Oak, for any number of 
> reasons.
> Also, the XPathToSQL2Converter package is not exported in an OSGi 
> environment, so client code cannot use that API to reconstruct the SQL2 
> statement in parallel.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.

2019-09-13 Thread Thomas Mueller (Jira)


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

Thomas Mueller resolved OAK-8245.
-
Resolution: Fixed

> Add column for explained "statement" to "explain" Query result, next to 
> 'plan' column.
> --
>
> Key: OAK-8245
> URL: https://issues.apache.org/jira/browse/OAK-8245
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Affects Versions: 1.12.0, 1.8.12, 1.10.2
>Reporter: Mark Adamcin
>Assignee: Thomas Mueller
>Priority: Minor
> Fix For: 1.18.0
>
>
> The "explain" behavior of the core Query is very useful for helping to debug 
> JCR query execution planning. For xpath queries, the resulting "plan" column 
> refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 
> statement for execution. This SQL2 statement should be exposed through the 
> same API as the "plan", by way of an additional column named "statement" in 
> the single result row. 
> At this time, this underlying SQL2 statement is inaccessible to users of the 
> JCR Query interface, which can only provide the original XPath statement.
> To access the converted SQL2 statement, a class targeting the JCR API must 
> implement a regular expression match against a log stream retrieved via slf4j 
> MDC.
> This facility is not very portable, and an effective pattern on one version 
> of Oak may not be effective on a different version of Oak, for any number of 
> reasons.
> Also, the XPathToSQL2Converter package is not exported in an OSGi 
> environment, so client code cannot use that API to reconstruct the SQL2 
> statement in parallel.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Comment Edited] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.

2019-09-13 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929170#comment-16929170
 ] 

Thomas Mueller edited comment on OAK-8245 at 9/13/19 12:53 PM:
---

http://svn.apache.org/r1866903 (trunk)
... it took more than a few days ...


was (Author: tmueller):
svn.apache.org/r1866903 (trunk)

> Add column for explained "statement" to "explain" Query result, next to 
> 'plan' column.
> --
>
> Key: OAK-8245
> URL: https://issues.apache.org/jira/browse/OAK-8245
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Affects Versions: 1.12.0, 1.8.12, 1.10.2
>Reporter: Mark Adamcin
>Assignee: Thomas Mueller
>Priority: Minor
>
> The "explain" behavior of the core Query is very useful for helping to debug 
> JCR query execution planning. For xpath queries, the resulting "plan" column 
> refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 
> statement for execution. This SQL2 statement should be exposed through the 
> same API as the "plan", by way of an additional column named "statement" in 
> the single result row. 
> At this time, this underlying SQL2 statement is inaccessible to users of the 
> JCR Query interface, which can only provide the original XPath statement.
> To access the converted SQL2 statement, a class targeting the JCR API must 
> implement a regular expression match against a log stream retrieved via slf4j 
> MDC.
> This facility is not very portable, and an effective pattern on one version 
> of Oak may not be effective on a different version of Oak, for any number of 
> reasons.
> Also, the XPathToSQL2Converter package is not exported in an OSGi 
> environment, so client code cannot use that API to reconstruct the SQL2 
> statement in parallel.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8245) Add column for explained "statement" to "explain" Query result, next to 'plan' column.

2019-09-13 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929170#comment-16929170
 ] 

Thomas Mueller commented on OAK-8245:
-

svn.apache.org/r1866903 (trunk)

> Add column for explained "statement" to "explain" Query result, next to 
> 'plan' column.
> --
>
> Key: OAK-8245
> URL: https://issues.apache.org/jira/browse/OAK-8245
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: query
>Affects Versions: 1.12.0, 1.8.12, 1.10.2
>Reporter: Mark Adamcin
>Assignee: Thomas Mueller
>Priority: Minor
>
> The "explain" behavior of the core Query is very useful for helping to debug 
> JCR query execution planning. For xpath queries, the resulting "plan" column 
> refers to the result of running XPathToSQL2Converter to produce a JCR-SQL2 
> statement for execution. This SQL2 statement should be exposed through the 
> same API as the "plan", by way of an additional column named "statement" in 
> the single result row. 
> At this time, this underlying SQL2 statement is inaccessible to users of the 
> JCR Query interface, which can only provide the original XPath statement.
> To access the converted SQL2 statement, a class targeting the JCR API must 
> implement a regular expression match against a log stream retrieved via slf4j 
> MDC.
> This facility is not very portable, and an effective pattern on one version 
> of Oak may not be effective on a different version of Oak, for any number of 
> reasons.
> Also, the XPathToSQL2Converter package is not exported in an OSGi 
> environment, so client code cannot use that API to reconstruct the SQL2 
> statement in parallel.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8623) Improve collision handling performance

2019-09-13 Thread Marcel Reutegger (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929161#comment-16929161
 ] 

Marcel Reutegger commented on OAK-8623:
---

Added ignored tests that verify the new expected behaviour: 
http://svn.apache.org/r1866900

> Improve collision handling performance
> --
>
> Key: OAK-8623
> URL: https://issues.apache.org/jira/browse/OAK-8623
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: documentmk
>Reporter: Marcel Reutegger
>Assignee: Marcel Reutegger
>Priority: Major
>
> The current collision handling on conflict in the DocumentNodeStore can be 
> rather expensive when there are old branch commits which were not merged.
> A commit that includes documents with old branch commits that have not been 
> merged will always attempt to set a collision marker on the commit root 
> document for those changes.
> While it is difficult to tell whether a branch commit will be merged at some 
> point, at least those branch commits that were created before the most recent 
> startup of a cluster node cannot be merged. The collision handling logic 
> could be improved to take the start time of a cluster node into account.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OAK-8623) Improve collision handling performance

2019-09-13 Thread Marcel Reutegger (Jira)
Marcel Reutegger created OAK-8623:
-

 Summary: Improve collision handling performance
 Key: OAK-8623
 URL: https://issues.apache.org/jira/browse/OAK-8623
 Project: Jackrabbit Oak
  Issue Type: Improvement
  Components: documentmk
Reporter: Marcel Reutegger
Assignee: Marcel Reutegger


The current collision handling on conflict in the DocumentNodeStore can be 
rather expensive when there are old branch commits which were not merged.

A commit that includes documents with old branch commits that have not been 
merged will always attempt to set a collision marker on the commit root 
document for those changes.

While it is difficult to tell whether a branch commit will be merged at some 
point, at least those branch commits that were created before the most recent 
startup of a cluster node cannot be merged. The collision handling logic could 
be improved to take the start time of a cluster node into account.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-7151) Support indexed based excerpts on properties

2019-09-13 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-7151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929146#comment-16929146
 ] 

Thomas Mueller commented on OAK-7151:
-

[~catholicon] I just saw this is still open... is there any work left?

> Support indexed based excerpts on properties
> 
>
> Key: OAK-7151
> URL: https://issues.apache.org/jira/browse/OAK-7151
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: lucene
>Reporter: Vikas Saurabh
>Assignee: Vikas Saurabh
>Priority: Major
> Fix For: 1.18.0
>
> Attachments: OAK-7151.patch, OAK-7151.xpath-new-syntax.patch, 
> OAK-7151.xpath.patch
>
>
> As discovered in OAK-4401 we fallback to {{SimpleExcerptProvider}} when 
> requesting excerpts for properties.
> The issue as highlighted in [~teofili]'s comment \[0] is that we at time of 
> query we don't have information about which all columns/fields would be 
> required for excerpts.
> A possible approach is that the query specified explicitly which columns 
> would be required in facets (of course, node level excerpt would still be 
> supported). This issue is to track that improvement.
> Note: this is *not* a substitute for OAK-4401 which is about doing saner 
> highlighting when {{SimpleExcerptProvider}} comes into play e.g. despite this 
> issue excerpt for non-stored fields (properties which aren't configured with 
> {{useInExcerpt}} in the index definition}, we'd need to fallback to 
> {{SimpleExcerptProvider}}.
> /[~tmueller]
> \[0]: 
> https://issues.apache.org/jira/browse/OAK-4401?focusedCommentId=15299857=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15299857



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8529) Eagerly deregister MBeans on SecurityProviderRegistration deactivation

2019-09-13 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929143#comment-16929143
 ] 

Robert Munteanu commented on OAK-8529:
--

[~angela] - I was actually wrong and this was not a race condition. The problem 
was that the {{deactivate}} method did not close the Closer, which meant that 
registered services would be dangling after a deactivate in case they did not 
go through the {{maybeUnregister()}} method. This is the case for instance with 
the {{AuthenticationConfiguration}} reference. I have updated the pull request 
with the change and with a failing test (that passes after my change).

Please see https://github.com/apache/jackrabbit-oak/pull/139/files .

Thanks!

> Eagerly deregister MBeans on SecurityProviderRegistration deactivation
> --
>
> Key: OAK-8529
> URL: https://issues.apache.org/jira/browse/OAK-8529
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: security
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: 1.18.0
>
>
> The SecurityProviderRegistration is prone to being activated and deactivated 
> during a regular Sling application startup ( for a prolonged discussion see 
> SLING-7811 ). The instance should fully cleanup after itself to make sure it 
> will be usable after an activate/deactive cycle.
> In practice the MBeans remain registered and prevent a further registration 
> with errors such as
> {noformat}6.08.2019 09:43:51.051 *ERROR* [CM Event Dispatcher (Fire 
> ConfigurationEvent: 
> pid=org.apache.jackrabbit.oak.security.authentication.AuthenticationConfigurationImpl)]
>  org.apache.aries.jmx.whiteboard.MBeanHolder register: Failure registering 
> MBean 
> org.apache.aries.jmx.util.shared.RegistrableStandardEmitterMBean@45011485 
> javax.management.InstanceAlreadyExistsException: 
> org.apache.jackrabbit.oak:name=LoginModule statistics,type=LoginModuleStats
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.aries.jmx.whiteboard.MBeanHolder.register(MBeanHolder.java:114)
> at 
> org.apache.aries.jmx.whiteboard.JmxWhiteboardSupport.registerMBean(JmxWhiteboardSupport.java:88)
> at 
> org.apache.aries.jmx.whiteboard.Activator$MBeanTracker.addingService(Activator.java:102)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
> at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
> at 
> org.apache.jackrabbit.oak.osgi.OsgiWhiteboard.register(OsgiWhiteboard.java:79)
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:115)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:99)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration.maybeRegister(SecurityProviderRegistration.java:539)
> at 
> 

[jira] [Resolved] (OAK-8622) Remove the version of the maven-resources-plugin from the fast profile

2019-09-13 Thread Robert Munteanu (Jira)


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

Robert Munteanu resolved OAK-8622.
--
Resolution: Fixed

Fixed in https://svn.apache.org/r1866896

> Remove the version of the maven-resources-plugin from the fast profile
> --
>
> Key: OAK-8622
> URL: https://issues.apache.org/jira/browse/OAK-8622
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: parent
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: 1.18.0
>
>
> The {{oak-parent}} pom contains a version for the {{maven-resources-plugin}} 
> in the _fast_ profile. This can lead to problems when executing that profile, 
> since the version of the plugin is otherwise inherited from the Maven parent 
> pom.
> For instance, with Maven 3.5.4 I get the following error when building Oak 
> with the _fast_ profile:
> {noformat}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources 
> (default-resources) on project oak-it-osgi: Execution default-resources of 
> goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources failed: 
> An API incompatibility was encountered while executing 
> org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources: 
> java.lang.NoSuchMethodError: 'void 
> org.apache.maven.shared.filtering.MavenResourcesExecution.setAddDefaultExcludes(boolean)'
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-resources-plugin:3.1.0-1339233906
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = 
> file:/home/robert/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/3.1.0/maven-resources-plugin-3.1.0.jar
> [ERROR] urls[1] = 
> file:/home/robert/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
> [ERROR] urls[2] = 
> file:/home/robert/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
> [ERROR] urls[3] = 
> file:/home/robert/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[4] = 
> file:/home/robert/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> [ERROR] urls[5] = 
> file:/home/robert/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
> [ERROR] urls[6] = 
> file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
> [ERROR] urls[7] = 
> file:/home/robert/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> [ERROR] urls[8] = 
> file:/home/robert/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> [ERROR] urls[9] = 
> file:/home/robert/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[10] = 
> file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
> [ERROR] urls[11] = 
> file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[12] = 
> file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[13] = 
> file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-utils/3.1.0/plexus-utils-3.1.0.jar
> [ERROR] urls[14] = 
> file:/home/robert/.m2/repository/commons-io/commons-io/2.5/commons-io-2.5.jar
> [ERROR] urls[15] = 
> file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.24/plexus-interpolation-1.24.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
> {noformat}
> Removing the version fixes the problem for me.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (OAK-8622) Remove the version of the maven-resources-plugin from the fast profile

2019-09-13 Thread Robert Munteanu (Jira)
Robert Munteanu created OAK-8622:


 Summary: Remove the version of the maven-resources-plugin from the 
fast profile
 Key: OAK-8622
 URL: https://issues.apache.org/jira/browse/OAK-8622
 Project: Jackrabbit Oak
  Issue Type: Task
  Components: parent
Reporter: Robert Munteanu
Assignee: Robert Munteanu
 Fix For: 1.18.0


The {{oak-parent}} pom contains a version for the {{maven-resources-plugin}} in 
the _fast_ profile. This can lead to problems when executing that profile, 
since the version of the plugin is otherwise inherited from the Maven parent 
pom.

For instance, with Maven 3.5.4 I get the following error when building Oak with 
the _fast_ profile:

{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources 
(default-resources) on project oak-it-osgi: Execution default-resources of goal 
org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources failed: An API 
incompatibility was encountered while executing 
org.apache.maven.plugins:maven-resources-plugin:3.1.0:resources: 
java.lang.NoSuchMethodError: 'void 
org.apache.maven.shared.filtering.MavenResourcesExecution.setAddDefaultExcludes(boolean)'
[ERROR] -
[ERROR] realm =
plugin>org.apache.maven.plugins:maven-resources-plugin:3.1.0-1339233906
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/home/robert/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/3.1.0/maven-resources-plugin-3.1.0.jar
[ERROR] urls[1] = 
file:/home/robert/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
[ERROR] urls[2] = 
file:/home/robert/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[3] = 
file:/home/robert/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[4] = 
file:/home/robert/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
[ERROR] urls[5] = 
file:/home/robert/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
[ERROR] urls[6] = 
file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
[ERROR] urls[7] = 
file:/home/robert/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[8] = 
file:/home/robert/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[9] = 
file:/home/robert/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[10] = 
file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.7.1/plexus-component-annotations-1.7.1.jar
[ERROR] urls[11] = 
file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[12] = 
file:/home/robert/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[13] = 
file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-utils/3.1.0/plexus-utils-3.1.0.jar
[ERROR] urls[14] = 
file:/home/robert/.m2/repository/commons-io/commons-io/2.5/commons-io-2.5.jar
[ERROR] urls[15] = 
file:/home/robert/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.24/plexus-interpolation-1.24.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import  from realm ClassRealm[maven.api, parent: null]]
{noformat}

Removing the version fixes the problem for me.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8529) Eagerly deregister MBeans on SecurityProviderRegistration deactivation

2019-09-13 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929122#comment-16929122
 ] 

Robert Munteanu commented on OAK-8529:
--

[~angela] - I believe this to be a race condition, so providing a test will not 
be that easy. However, when reviewing my code I saw that the proposed change is 
incorrect, as it may close the closer too early. I'll try and come up with an 
updated patch.

> Eagerly deregister MBeans on SecurityProviderRegistration deactivation
> --
>
> Key: OAK-8529
> URL: https://issues.apache.org/jira/browse/OAK-8529
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: security
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: 1.18.0
>
>
> The SecurityProviderRegistration is prone to being activated and deactivated 
> during a regular Sling application startup ( for a prolonged discussion see 
> SLING-7811 ). The instance should fully cleanup after itself to make sure it 
> will be usable after an activate/deactive cycle.
> In practice the MBeans remain registered and prevent a further registration 
> with errors such as
> {noformat}6.08.2019 09:43:51.051 *ERROR* [CM Event Dispatcher (Fire 
> ConfigurationEvent: 
> pid=org.apache.jackrabbit.oak.security.authentication.AuthenticationConfigurationImpl)]
>  org.apache.aries.jmx.whiteboard.MBeanHolder register: Failure registering 
> MBean 
> org.apache.aries.jmx.util.shared.RegistrableStandardEmitterMBean@45011485 
> javax.management.InstanceAlreadyExistsException: 
> org.apache.jackrabbit.oak:name=LoginModule statistics,type=LoginModuleStats
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.aries.jmx.whiteboard.MBeanHolder.register(MBeanHolder.java:114)
> at 
> org.apache.aries.jmx.whiteboard.JmxWhiteboardSupport.registerMBean(JmxWhiteboardSupport.java:88)
> at 
> org.apache.aries.jmx.whiteboard.Activator$MBeanTracker.addingService(Activator.java:102)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
> at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
> at 
> org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
> at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
> at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
> at 
> org.apache.jackrabbit.oak.osgi.OsgiWhiteboard.register(OsgiWhiteboard.java:79)
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:115)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:99)
>  [org.apache.jackrabbit.oak-core-spi:1.16.0]
> at 
> org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration.maybeRegister(SecurityProviderRegistration.java:539)
> at 
> org.apache.jackrabbit.oak.security.internal.SecurityProviderRegistration.activate(SecurityProviderRegistration.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  

[jira] [Resolved] (OAK-8530) Ensure MBean are deregistered if the repository fails to start

2019-09-13 Thread Robert Munteanu (Jira)


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

Robert Munteanu resolved OAK-8530.
--
Resolution: Fixed

Fixed in https://svn.apache.org/r1866895.

> Ensure MBean are deregistered if the repository fails to start
> --
>
> Key: OAK-8530
> URL: https://issues.apache.org/jira/browse/OAK-8530
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: 1.18.0
>
>
> When used in OSGi environments the repository service is unfortunately prone 
> to restarts ( see SLING-7811 for the gory details ). Besides the performance 
> problem, the repository typically fails to restart since MBeans that were 
> registered once were not deregistered. The failures happen before repository 
> is constructed, so there is no instance to close.
> A typical stack trace is
> {noformat}
> 06.08.2019 09:55:03.894 *ERROR* [Apache Sling Repository Startup Thread #4] 
> org.apache.aries.jmx.whiteboard.MBeanHolder register: Failure registering 
> MBean org.apache.jackrabbit.oak.management.RepositoryManager@5e05b159
> javax.management.InstanceAlreadyExistsException: 
> org.apache.jackrabbit.oak:name=repository manager,type=RepositoryManagement
>   at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
>   at 
> org.apache.aries.jmx.whiteboard.MBeanHolder.register(MBeanHolder.java:114)
>   at 
> org.apache.aries.jmx.whiteboard.JmxWhiteboardSupport.registerMBean(JmxWhiteboardSupport.java:88)
>   at 
> org.apache.aries.jmx.whiteboard.Activator$MBeanTracker.addingService(Activator.java:102)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
>   at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>   at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>   at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
>   at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
>   at 
> org.apache.jackrabbit.oak.osgi.OsgiWhiteboard.register(OsgiWhiteboard.java:79)
>   at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:115)
>  [org.apache.jackrabbit.oak-core-spi:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:99)
>  [org.apache.jackrabbit.oak-core-spi:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.Oak.createNewContentRepository(Oak.java:772) 
> [org.apache.jackrabbit.oak-core:1.18.0.SNAPSHOT]
>   at org.apache.jackrabbit.oak.Oak.createContentRepository(Oak.java:671) 
> [org.apache.jackrabbit.oak-core:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.jcr.Jcr.createContentRepository(Jcr.java:376) 
> [org.apache.jackrabbit.oak-jcr:1.18.0.SNAPSHOT]
>   at 
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:152)
>  [org.apache.sling.jcr.oak.server:1.2.2]
>   at 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:481)
>  [org.apache.sling.jcr.base:3.0.6]
>   at 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:86)
>  [org.apache.sling.jcr.base:3.0.6]
> 

[jira] [Commented] (OAK-8530) Ensure MBean are deregistered if the repository fails to start

2019-09-13 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929069#comment-16929069
 ] 

Robert Munteanu commented on OAK-8530:
--

I guess there are no objections :) I'll rebase, retest and push the change.

> Ensure MBean are deregistered if the repository fails to start
> --
>
> Key: OAK-8530
> URL: https://issues.apache.org/jira/browse/OAK-8530
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: core
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: 1.18.0
>
>
> When used in OSGi environments the repository service is unfortunately prone 
> to restarts ( see SLING-7811 for the gory details ). Besides the performance 
> problem, the repository typically fails to restart since MBeans that were 
> registered once were not deregistered. The failures happen before repository 
> is constructed, so there is no instance to close.
> A typical stack trace is
> {noformat}
> 06.08.2019 09:55:03.894 *ERROR* [Apache Sling Repository Startup Thread #4] 
> org.apache.aries.jmx.whiteboard.MBeanHolder register: Failure registering 
> MBean org.apache.jackrabbit.oak.management.RepositoryManager@5e05b159
> javax.management.InstanceAlreadyExistsException: 
> org.apache.jackrabbit.oak:name=repository manager,type=RepositoryManagement
>   at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
>   at 
> org.apache.aries.jmx.whiteboard.MBeanHolder.register(MBeanHolder.java:114)
>   at 
> org.apache.aries.jmx.whiteboard.JmxWhiteboardSupport.registerMBean(JmxWhiteboardSupport.java:88)
>   at 
> org.apache.aries.jmx.whiteboard.Activator$MBeanTracker.addingService(Activator.java:102)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
>   at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>   at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>   at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
>   at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
>   at 
> org.apache.jackrabbit.oak.osgi.OsgiWhiteboard.register(OsgiWhiteboard.java:79)
>   at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:115)
>  [org.apache.jackrabbit.oak-core-spi:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.spi.whiteboard.WhiteboardUtils.registerMBean(WhiteboardUtils.java:99)
>  [org.apache.jackrabbit.oak-core-spi:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.Oak.createNewContentRepository(Oak.java:772) 
> [org.apache.jackrabbit.oak-core:1.18.0.SNAPSHOT]
>   at org.apache.jackrabbit.oak.Oak.createContentRepository(Oak.java:671) 
> [org.apache.jackrabbit.oak-core:1.18.0.SNAPSHOT]
>   at 
> org.apache.jackrabbit.oak.jcr.Jcr.createContentRepository(Jcr.java:376) 
> [org.apache.jackrabbit.oak-jcr:1.18.0.SNAPSHOT]
>   at 
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:152)
>  [org.apache.sling.jcr.oak.server:1.2.2]
>   at 
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:481)
>  [org.apache.sling.jcr.base:3.0.6]
>   at 
> 

[jira] [Created] (OAK-8621) Build Jackrabbit Oak #2377 failed

2019-09-13 Thread Hudson (Jira)
Hudson created OAK-8621:
---

 Summary: Build Jackrabbit Oak #2377 failed
 Key: OAK-8621
 URL: https://issues.apache.org/jira/browse/OAK-8621
 Project: Jackrabbit Oak
  Issue Type: Bug
  Components: continuous integration
Reporter: Hudson


No description is provided

The build Jackrabbit Oak #2377 has failed.
First failed run: [Jackrabbit Oak 
#2377|https://builds.apache.org/job/Jackrabbit%20Oak/2377/] [console 
log|https://builds.apache.org/job/Jackrabbit%20Oak/2377/console]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Commented] (OAK-8603) Composite Node Store + Counter Index: allow indexing from scratch / reindex

2019-09-13 Thread Thomas Mueller (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929038#comment-16929038
 ] 

Thomas Mueller commented on OAK-8603:
-

Pull request (work in progress): 
https://github.com/apache/jackrabbit-oak/pull/149/files

> Composite Node Store + Counter Index: allow indexing from scratch / reindex
> ---
>
> Key: OAK-8603
> URL: https://issues.apache.org/jira/browse/OAK-8603
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
>  Labels: fabriziofortino
> Attachments: OAK-8603.patch
>
>
> When using the composite node store with a read-only portion of the 
> repository, the counter index does not allow to index from scratch / reindex.
> Index from scratch is needed in case the async checkpoint is lost. Reindex is 
> started by setting the "reindex" flag to true.
> Currently the failure is:
> {noformat}
> 05.09.2019 09:29:21.892 *WARN* [async-index-update-async] 
> org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate [async] The index 
> update is still failing
> java.lang.UnsupportedOperationException: This builder is read-only.
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.unsupported(ReadOnlyBuilder.java:44)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.child(ReadOnlyBuilder.java:189)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.child(ReadOnlyBuilder.java:34)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.leaveNew(NodeCounterEditor.java:162)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.leave(NodeCounterEditor.java:114)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.commit.CompositeEditor.leave(CompositeEditor.java:73)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> 

[jira] [Updated] (OAK-8603) Composite Node Store + Counter Index: allow indexing from scratch / reindex

2019-09-13 Thread Thomas Mueller (Jira)


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

Thomas Mueller updated OAK-8603:

Labels: fabriziofortino  (was: )

> Composite Node Store + Counter Index: allow indexing from scratch / reindex
> ---
>
> Key: OAK-8603
> URL: https://issues.apache.org/jira/browse/OAK-8603
> Project: Jackrabbit Oak
>  Issue Type: Improvement
>  Components: composite, indexing
>Reporter: Thomas Mueller
>Assignee: Thomas Mueller
>Priority: Major
>  Labels: fabriziofortino
> Attachments: OAK-8603.patch
>
>
> When using the composite node store with a read-only portion of the 
> repository, the counter index does not allow to index from scratch / reindex.
> Index from scratch is needed in case the async checkpoint is lost. Reindex is 
> started by setting the "reindex" flag to true.
> Currently the failure is:
> {noformat}
> 05.09.2019 09:29:21.892 *WARN* [async-index-update-async] 
> org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate [async] The index 
> update is still failing
> java.lang.UnsupportedOperationException: This builder is read-only.
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.unsupported(ReadOnlyBuilder.java:44)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.child(ReadOnlyBuilder.java:189)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.state.ReadOnlyBuilder.child(ReadOnlyBuilder.java:34)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.getBuilder(NodeCounterEditor.java:184)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.leaveNew(NodeCounterEditor.java:162)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.plugins.index.counter.NodeCounterEditor.leave(NodeCounterEditor.java:114)
>  [org.apache.jackrabbit.oak-core:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.commit.CompositeEditor.leave(CompositeEditor.java:73)
>  [org.apache.jackrabbit.oak-store-spi:1.16.0.R1866113]
>   at 
> org.apache.jackrabbit.oak.spi.commit.VisibleEditor.leave(VisibleEditor.java:59)
>  

[jira] [Commented] (OAK-8325) Document Jenkins jobs

2019-09-13 Thread Robert Munteanu (Jira)


[ 
https://issues.apache.org/jira/browse/OAK-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929031#comment-16929031
 ] 

Robert Munteanu commented on OAK-8325:
--

I've updated Jackrabbit-Oak-Windows to send notifications to 
oak-...@jackrabbit.apache.org, following [oak-...@jackrabbit.apache.org 
discussion|https://lists.apache.org/thread.html/9758a99781aecc5ceff04176abd5ae8e743cb0d3a797c5231bfdb8ce@%3Coak-dev.jackrabbit.apache.org%3E]
 .

> Document Jenkins jobs
> -
>
> Key: OAK-8325
> URL: https://issues.apache.org/jira/browse/OAK-8325
> Project: Jackrabbit Oak
>  Issue Type: Task
>  Components: doc
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>Priority: Major
>
> h3.  "Jackrabbit Oak"
> <[https://builds.apache.org/job/Jackrabbit%20Oak/]>
>  - builds <[https://svn.apache.org/repos/asf/jackrabbit/oak/trunk]>
>  - builds with JDK 1.8 (latest)
>  - clean install -Ppedantic,integrationTesting -Dmongo.port=9 
> -Dcheckstyle.skip=true -Dfindbugs.skip=true -DtrimStackTrace=false
>  - sends notifications to oak-...@jackrabbit.apache.org
>  - appears stable
> h3. "Apache Jackrabbit Oak matrix"
> <[https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/]>
>  - builds <[https://svn.apache.org/repos/asf/jackrabbit/oak/trunk]>
>  - various targets (4 * 3 * 2 = 24):
>  ** by JDK 1.8 (latest), JDK 11 (latest), JDK 12 (latest), JDK 13 (latest)
>  ** DOCUMENT_RDB, DOCUMENT_NS, SEGMENT_TAR
>  ** unittesting and integrationTesting
>  - additional profiles: rat, guava-latest, javadoc, guavabetachecks
>  - no notifications
>  - not very stable, docker related failures
> h3. "Apache Jackrabbit Oak (maintenance branch) matrix"
> 
> Similar to the above, but builds all maintenance branches, but only for JDK 
> 7, 8, and 11.
> h3. "Jackrabbit-Oak-Windows"
> 
> Builds seem to be stable, notifications go to [~mduerig] apparently.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)