[jira] [Resolved] (SLING-7282) Enable packaging data support in stacktraces by default

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra resolved SLING-7282.

Resolution: Fixed

Done with 
[commit|https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-starter.git;a=commitdiff;h=bf41073f4176eefc59a5c8e71e179ea754846b02]

> Enable packaging data support in stacktraces by default
> ---
>
> Key: SLING-7282
> URL: https://issues.apache.org/jira/browse/SLING-7282
> Project: Sling
>  Issue Type: Improvement
>  Components: Launchpad
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Launchpad Builder 10
>
>
> Enable the support for including packaging data with stacktrace in logs by 
> default (SLING-3049)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7282) Enable packaging data support in stacktraces by default

2017-11-30 Thread Chetan Mehrotra (JIRA) 
Chetan Mehrotra created SLING-7282:
--

 Summary: Enable packaging data support in stacktraces by default
 Key: SLING-7282
 URL: https://issues.apache.org/jira/browse/SLING-7282
 Project: Sling
  Issue Type: Improvement
  Components: Launchpad
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
Priority: Minor
 Fix For: Launchpad Builder 10


Enable the support for including packaging data with stacktrace in logs by 
default (SLING-3049)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7239) LogbackManager may miss out some OSGi config at time of startup

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7239.
--

> LogbackManager may miss out some OSGi config at time of startup
> ---
>
> Key: SLING-7239
> URL: https://issues.apache.org/jira/browse/SLING-7239
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.1.0
>
>
> {{LogbackManager}} currently upon construction reads all the OSGi config and 
> configure them in Logback. Config which comes laters leads to logback reset. 
> However during the time when its getting constructed it has a logic to ignore 
> the reset flag initialization for startup. This may lead to a race condition 
> where some OSGi configs are picked up while it is getting constructed and 
> some OSGi config arriving later are not picked up. For e.g.
> # LogbackManager constructor is invoked
> # It constructs LogConfigManager which registers the managed services
> # ManagedServices receive some OSGi config and push them to LogConfigManager
> # LogbackManager picks them up and add them to Logback but still startup is 
> not finished i.e. started = true is not called
> # Some more OSGi config arrive - These would get ignored as 
> LogbackManager#configChanged would ignore the calls because started != true
> # LogbackManager startup completes and started = true
> So here configs at #5 would not be picked up unless at #7 some more OSGi 
> config arrive. Or some one modifies the config post system start



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-3049) Make Logback Stacktrace Packaging data support OSGi aware

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-3049.
--

> Make Logback Stacktrace Packaging data support OSGi aware
> -
>
> Key: SLING-3049
> URL: https://issues.apache.org/jira/browse/SLING-3049
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>  Labels: logback
> Fix For: Commons Log 5.1.0
>
> Attachments: SLING-3049.patch, 
> buildbot-exceptions-while-stopping-jetty.txt
>
>
> Logback provides a useful feature where it dumps the Class packaging Data 
> along with the stacktrace [1]. This provides a quick view of the location 
> from where classes in a given stacktrace are coming. Its default logic does 
> not work properly in OSGi env. Hence it would be useful to patch its logic to 
> become OSGi aware
> [1] http://logback.qos.ch/reasonsToSwitch.html#packagingData



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-6044) Conflicting LogManager and LogWriter if using the same logfile

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-6044.
--

> Conflicting LogManager and LogWriter if using the same logfile
> --
>
> Key: SLING-6044
> URL: https://issues.apache.org/jira/browse/SLING-6044
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Log 4.0.2
>Reporter: Jörg Hoh
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.1.0
>
> Attachments: SLING-6044-multiple-loggers-writers.jpg
>
>
> When you have a logmanager and a logwriter pointing to the same file, you get 
> an exception like this:
> {panel}
> 07.09.2016 17:33:31.126 *ERROR* [] CM Configuration Updater (Update: 
> pid=org.apache.sling.commons.log.LogManager) org.apache.felix.configadmin 
> Service [org.apache.felix.cm.ConfigurationAdmin,9, 
> [org.osgi.service.cm.ConfigurationAdmin]] 
> [org.osgi.service.cm.ManagedService, id=10, 
> bundle=7/slinginstall:c:\java\IBM\LibertyProfile\usr\servers\aem-1\sling\_\launchpad\startup\1\org.apache.sling.commons.log-4.0.0.jar]:
>  Updating property org.apache.sling.commons.log.file of configuration 
> org.apache.sling.commons.log.LogManager caused a problem: LogFile 
> C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log already 
> configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af
>  (org.osgi.service.cm.ConfigurationException: 
> org.apache.sling.commons.log.file : LogFile 
> C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log already 
> configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af)
>  
> org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.file 
> : LogFile C:\java\IBM\LibertyProfile\usr\servers\aem-1\aemlogs\logs\error.log 
> already configured by configuration 
> org.apache.sling.commons.log.LogManager.factory.writer.8402a603-bdef-4404-9ff1-0e0f592578af
>  
>         at 
> org.apache.sling.commons.log.logback.internal.config.GlobalConfigurator.updated(GlobalConfigurator.java:32)
>         at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:148)
>  
>         at 
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:81)
>  
>         at 
> org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1744)
>  
>         at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:103) 
>         at java.lang.Thread.run(Thread.java:744) 
> Caused by: 
> org.apache.sling.commons.log.logback.internal.config.ConfigurationException: 
>         at 
> org.apache.sling.commons.log.logback.internal.LogConfigManager.updateLogWriter(LogConfigManager.java:398)
>  
>         at 
> org.apache.sling.commons.log.logback.internal.LogConfigManager.updateGlobalConfiguration(LogConfigManager.java:327)
>  
>         at 
> org.apache.sling.commons.log.logback.internal.config.GlobalConfigurator.updated(GlobalConfigurator.java:30)
>  
>         ... 5 common frames omitted
> {panel}
> Obviously the Logmanager internally provides a Logwriter, so these conflict. 
> This should be documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7224) Switch to standard OSGi annotations

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7224.
--

> Switch to standard OSGi annotations
> ---
>
> Key: SLING-7224
> URL: https://issues.apache.org/jira/browse/SLING-7224
> Project: Sling
>  Issue Type: Task
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Commons Log 5.1.0
>
>
> Switch to official OSGi annotations



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7221) Update osgi core dependency to 6.0

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7221.
--

> Update osgi core dependency to 6.0
> --
>
> Key: SLING-7221
> URL: https://issues.apache.org/jira/browse/SLING-7221
> Project: Sling
>  Issue Type: Task
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Commons Log 5.1.0
>
>
> Update various dependencies in Commons Log. Particularly dependency on 
> osgi.core to 6.0



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-6482) Commons Log WebConsole: Exception when creating logger with an empty log file

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-6482.
--

> Commons Log WebConsole: Exception when creating logger with an empty log file
> -
>
> Key: SLING-6482
> URL: https://issues.apache.org/jira/browse/SLING-6482
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Log 5.0.0
>Reporter: Bjoern Weide
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Commons Log 5.1.0
>
> Attachments: SLING-6482-v01.patch
>
>
> When creating a new logger via WebConsole specifying an empty logfile it 
> causes an StringIndexOutOfBoundsException when (re-)opening the WebConsole.
> {noformat}
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
>   at java.lang.String.substring(String.java:1931)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.getPath(SlingLogPanel.java:791)
> ...
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-6577) StringIndexOutOfBoundsException in Sling Log Web Console when creating new logger with absolute file name

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-6577.
--

> StringIndexOutOfBoundsException in Sling Log Web Console when creating new 
> logger with absolute file name
> -
>
> Key: SLING-6577
> URL: https://issues.apache.org/jira/browse/SLING-6577
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Log 5.0.0
>Reporter: Konrad Windszus
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.1.0
>
>
> After adding a new logger via the web console exposed at 
> {{/system/console/slinglog}} with an absolute filename (one starting with 
> "/"), the following exception is thrown 
> {code}
> 28.02.2017 16:47:31.300 *ERROR* [qtp455076072-280] 
> org.apache.felix.http.jetty Exception while processing request to 
> /system/console/slinglog (java.lang.StringIndexOutOfBoundsException: String 
> index out of range: -42)
> java.lang.StringIndexOutOfBoundsException: String index out of range: -42
>   at java.lang.String.substring(String.java:1931)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.getPath(SlingLogPanel.java:791)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.appendOsgiConfiguredLoggerData(SlingLogPanel.java:221)
>   at 
> org.apache.sling.commons.log.logback.internal.SlingLogPanel.render(SlingLogPanel.java:110)
>   at 
> org.apache.sling.commons.log.webconsole.internal.LogWebConsolePlugin.renderContent(LogWebConsolePlugin.java:79)
>   at 
> org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:194)
> {code}
> This is related to the exception being mentioned in SLING-6482.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7220) Update Logback to 1.2.3 version

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7220.
--

> Update Logback to 1.2.3 version
> ---
>
> Key: SLING-7220
> URL: https://issues.apache.org/jira/browse/SLING-7220
> Project: Sling
>  Issue Type: Task
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.1.0
>
>
> Update Logback to 1.2.3 version
> See https://logback.qos.ch/news.html for release notes. Specially 1.2.0 
> release has significant performance improvements



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7222) Too frequent samples

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7222.
--

> Too frequent samples
> 
>
> Key: SLING-7222
> URL: https://issues.apache.org/jira/browse/SLING-7222
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Metrics RRD4J 1.0.0
>Reporter: Marcel Reutegger
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Commons Metrics RRD4J 1.0.2
>
> Attachments: SLING-7222.patch
>
>
> The metrics reporter sometimes logs error messages telling samples are 
> reported too frequently (more than once a second):
> {noformat}
> 29.10.2017 19:01:25.384 *ERROR* [metrics-RRD4JReporter-1-thread-1] 
> com.codahale.metrics.ScheduledReporter RuntimeException thrown from 
> RRD4JReporter#report. Exception was suppressed.
> java.lang.IllegalArgumentException: Bad sample time: 1509300085. Last update 
> time was 1509300085, at least one second step is required
> at org.rrd4j.core.RrdDb.store(RrdDb.java:517)
> at org.rrd4j.core.Sample.update(Sample.java:194)
> at 
> org.apache.sling.commons.metrics.rrd4j.impl.RRD4JReporter.report(RRD4JReporter.java:239)
> at 
> com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
> at 
> com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7223) Spikes in RRD after restart

2017-11-30 Thread Chetan Mehrotra (JIRA) 

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

Chetan Mehrotra closed SLING-7223.
--

> Spikes in RRD after restart
> ---
>
> Key: SLING-7223
> URL: https://issues.apache.org/jira/browse/SLING-7223
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons Metrics RRD4J 1.0.0
>Reporter: Marcel Reutegger
>Assignee: Chetan Mehrotra
> Fix For: Commons Metrics RRD4J 1.0.2
>
> Attachments: SLING-7223.patch
>
>
> Running the reporter for some time and then restarting the process shows 
> spikes in the collected data. These are caused by counter gauges that are 
> reset to zero after a restart. RRD interprets them as 32bit or 64bit integer 
> overflows and calculates incorrect values.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Sling Commons Log 5.1.0

2017-11-30 Thread Chetan Mehrotra 
 The vote passed with four binding +1 votes
Chetan Mehrotra


On Fri, Dec 1, 2017 at 11:54 AM, Chetan Mehrotra
 wrote:
> +1
> Chetan Mehrotra
>
>
> On Tue, Nov 28, 2017 at 2:39 PM, Karl Pauls  wrote:
>> +1
>>
>> regards,
>>
>> Karl
>>
>> On Monday, November 27, 2017, Stefan Seifert  wrote:
>>
>>> +1
>>>
>>>
>>
>> --
>> Karl Pauls
>> karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Metrics RRD4J 1.0.2

2017-11-30 Thread Chetan Mehrotra 
 The vote passed with three binding +1 votes
Chetan Mehrotra


On Fri, Dec 1, 2017 at 11:54 AM, Chetan Mehrotra
 wrote:
> +1
> Chetan Mehrotra
>
>
> On Fri, Nov 24, 2017 at 8:09 PM, Karl Pauls  wrote:
>> +1
>>
>> regards,
>>
>> Karl
>>
>> On Fri, Nov 24, 2017 at 3:25 PM, Robert Munteanu  wrote:
>>> On Fri, 2017-11-24 at 16:55 +0530, Chetan Mehrotra wrote:
 Please vote to approve this release:
>>>
>>> +1
>>>
>>> Robert
>>
>>
>>
>> --
>> Karl Pauls
>> karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Metrics RRD4J 1.0.2

2017-11-30 Thread Chetan Mehrotra 
+1
Chetan Mehrotra


On Fri, Nov 24, 2017 at 8:09 PM, Karl Pauls  wrote:
> +1
>
> regards,
>
> Karl
>
> On Fri, Nov 24, 2017 at 3:25 PM, Robert Munteanu  wrote:
>> On Fri, 2017-11-24 at 16:55 +0530, Chetan Mehrotra wrote:
>>> Please vote to approve this release:
>>
>> +1
>>
>> Robert
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Commons Log 5.1.0

2017-11-30 Thread Chetan Mehrotra 
+1
Chetan Mehrotra


On Tue, Nov 28, 2017 at 2:39 PM, Karl Pauls  wrote:
> +1
>
> regards,
>
> Karl
>
> On Monday, November 27, 2017, Stefan Seifert  wrote:
>
>> +1
>>
>>
>
> --
> Karl Pauls
> karlpa...@gmail.com

[jira] [Commented] (SLING-6702) Make MetricsService accessible as easily as a Logger

2017-11-30 Thread Chetan Mehrotra (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274004#comment-16274004
 ] 

Chetan Mehrotra commented on SLING-6702:


[~bdelacretaz] Should we resolve this issue?

> Make MetricsService accessible as easily as a Logger
> 
>
> Key: SLING-6702
> URL: https://issues.apache.org/jira/browse/SLING-6702
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: Commons Metrics 1.2.0
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: commons metrics 1.2.4
>
>
> Metrics are useful in all classes, not only OSGi components, so getting the 
> {{MetricsService}} should be as useful as getting a {{Logger}} for example.
> I'll add a public {{MetricsServiceFactory}} class to our metrics module, 
> usable like
> {code}
>   MetricsService ms = 
> MetricsServiceFactory.getMetricsService(this.getClass());
> {code}
> There's already a private {{MetricsServiceFactory}} class in that module, 
> I'll rename that to {{InternalMetricsServiceFactory}} to avoid confusion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7268) unable to create principals and use principals in ACLs on import

2017-11-30 Thread Eric Norman (JIRA) 

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

Eric Norman updated SLING-7268:
---
Fix Version/s: JCR ContentLoader 2.2.6

> unable to create principals and use principals in ACLs on import
> 
>
> Key: SLING-7268
> URL: https://issues.apache.org/jira/browse/SLING-7268
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Andres Bott
>Assignee: Eric Norman
>Priority: Minor
> Fix For: JCR ContentLoader 2.2.6
>
>
> Not able to use principals and ACLS on the same bundle when defining initial 
> content
> ie:
> {
>   "jcr:primaryType" : "sling:Folder",
>   "security:principals": [
> { "name": "*user*", "password": "mypassword"}
>   ],
>   "security:acl": [
> { "principal": "*user*", "granted": ["jcr:read","jcr:write"] }
>   ]
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7268) unable to create principals and use principals in ACLs on import

2017-11-30 Thread Eric Norman (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273331#comment-16273331
 ] 

Eric Norman commented on SLING-7268:


I committed a fix and a new test for your review at: 
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/commit/646984b82c72ccdac055bfaf7bd876adfc0a4664

> unable to create principals and use principals in ACLs on import
> 
>
> Key: SLING-7268
> URL: https://issues.apache.org/jira/browse/SLING-7268
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Andres Bott
>Assignee: Eric Norman
>Priority: Minor
>
> Not able to use principals and ACLS on the same bundle when defining initial 
> content
> ie:
> {
>   "jcr:primaryType" : "sling:Folder",
>   "security:principals": [
> { "name": "*user*", "password": "mypassword"}
>   ],
>   "security:acl": [
> { "principal": "*user*", "granted": ["jcr:read","jcr:write"] }
>   ]
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7279) Documentation for custom logging appenders is not relevant

2017-11-30 Thread Stefan Seifert (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273317#comment-16273317
 ] 

Stefan Seifert commented on SLING-7279:
---

i'm currently not in the details of this part of the logging configuration - 
perhaps you can provide a PR to the documentation page?
https://github.com/apache/sling-site/blob/master/src/main/jbake/content/documentation/development/logging.md

> Documentation for custom logging appenders is not relevant
> --
>
> Key: SLING-7279
> URL: https://issues.apache.org/jira/browse/SLING-7279
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Affects Versions: Commons Log 5.0.2
>Reporter: Denis Kurochkin
>Priority: Minor
>  Labels: logback
>
> Since SLING-3069 and SLING-3242 were implemented the examples in the 
> documentation became irrelevant
> https://sling.apache.org/documentation/development/logging.html#appenders-as-osgi-services
> suffixing with the colon and logging level is not supported
> In SLING-3242 added new approach for assigning Appender to the Logger with 
> the given loglevel
> I had spent a lot of time figuring out why examples from the official 
> documentation don't work on my env until I found these tickets, and I want 
> others to not repeat my way



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7281) Sling query doesn't release referenced resources

2017-11-30 Thread Stefan Seifert (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273306#comment-16273306
 ] 

Stefan Seifert commented on SLING-7281:
---

does the problem also occur when you use only sling query and not fsresource?

please keep in mind that fsresource was designed primary for making development 
easier, it was never tested for "heavy production usage" with serving lots of 
thousands or more nodes through it. there is also a simple in-memory cache 
integrated. this cache is limited by default to 10,000 entries - you might 
experiment with different values to see if has an effect. it is configurable 
via the "Apache Sling File System Resource Provider" configuration.

> Sling query doesn't release referenced resources
> 
>
> Key: SLING-7281
> URL: https://issues.apache.org/jira/browse/SLING-7281
> Project: Sling
>  Issue Type: Bug
>Reporter: Bart Wulteputte
> Attachments: Screen Shot 2017-11-30 at 16.30.33.png, Screen Shot 
> 2017-11-30 at 18.19.07.png
>
>
> We were using slingquery 3.0.0 and fsresource 2.1.8. I'm not sure if 
> fsresource actually has anything to do with it, but I'm just adding the info 
> to be complete.
> The exact call done is : 
> $(pageResource).searchStrategy(SearchStrategy.DFS).find("[expiryDate]");
> The goal was to look for subresources under pageResource which contains a 
> property which should be taken into account to do another action. However, 
> what we see is that items are traversed and never released. Something that 
> contains a <50 nodes starts eating up more and more of the heap without ever 
> releasing any references. As you can see from the visualVM screen, we chew 
> through 16GB of heap in less than half an hour
> I'm unsure how to deliver a reproducible case without disclosing customer 
> production data. My suspicion is that if you create a decent tree of nodes 
> and keep invoke the query statement X times you'll be able to see something 
> similar. In our case, we have a job which runs every minute and runs this 
> query for X items each time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-7268) unable to create principals and use principals in ACLs on import

2017-11-30 Thread Eric Norman (JIRA) 

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

Eric Norman reassigned SLING-7268:
--

Assignee: Eric Norman

> unable to create principals and use principals in ACLs on import
> 
>
> Key: SLING-7268
> URL: https://issues.apache.org/jira/browse/SLING-7268
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Andres Bott
>Assignee: Eric Norman
>Priority: Minor
>
> Not able to use principals and ACLS on the same bundle when defining initial 
> content
> ie:
> {
>   "jcr:primaryType" : "sling:Folder",
>   "security:principals": [
> { "name": "*user*", "password": "mypassword"}
>   ],
>   "security:acl": [
> { "principal": "*user*", "granted": ["jcr:read","jcr:write"] }
>   ]
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7268) unable to create principals and use principals in ACLs on import

2017-11-30 Thread Eric Norman (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273232#comment-16273232
 ] 

Eric Norman commented on SLING-7268:


It's still worth fixing since the same scenario would happen with the import 
POST operation if you use JSON input that creates a user or group and an ACE 
for that principal within the same transaction.

The solution appears to be the same as what was done to resolve SLING-6182 
using what  was pointed out in OAK-5496.   We cannot successfully use 
PrincipalManager#getPrincipal in oak without the session that created the 
principal getting saved first (and a subsequent index update).   The workaround 
is to fallback to the UserManager#getAuthorizable API to locate the principal.


> unable to create principals and use principals in ACLs on import
> 
>
> Key: SLING-7268
> URL: https://issues.apache.org/jira/browse/SLING-7268
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Andres Bott
>Priority: Minor
>
> Not able to use principals and ACLS on the same bundle when defining initial 
> content
> ie:
> {
>   "jcr:primaryType" : "sling:Folder",
>   "security:principals": [
> { "name": "*user*", "password": "mypassword"}
>   ],
>   "security:acl": [
> { "principal": "*user*", "granted": ["jcr:read","jcr:write"] }
>   ]
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7281) Sling query doesn't release referenced resources

2017-11-30 Thread Bart Wulteputte (JIRA) 
Bart Wulteputte created SLING-7281:
--

 Summary: Sling query doesn't release referenced resources
 Key: SLING-7281
 URL: https://issues.apache.org/jira/browse/SLING-7281
 Project: Sling
  Issue Type: Bug
Reporter: Bart Wulteputte
 Attachments: Screen Shot 2017-11-30 at 16.30.33.png, Screen Shot 
2017-11-30 at 18.19.07.png

We were using slingquery 3.0.0 and fsresource 2.1.8. I'm not sure if fsresource 
actually has anything to do with it, but I'm just adding the info to be 
complete.

The exact call done is : 
$(pageResource).searchStrategy(SearchStrategy.DFS).find("[expiryDate]");

The goal was to look for subresources under pageResource which contains a 
property which should be taken into account to do another action. However, what 
we see is that items are traversed and never released. Something that contains 
a <50 nodes starts eating up more and more of the heap without ever releasing 
any references. As you can see from the visualVM screen, we chew through 16GB 
of heap in less than half an hour

I'm unsure how to deliver a reproducible case without disclosing customer 
production data. My suspicion is that if you create a decent tree of nodes and 
keep invoke the query statement X times you'll be able to see something 
similar. In our case, we have a job which runs every minute and runs this query 
for X items each time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Sling Scripting JSP version 2.3.4

2017-11-30 Thread Karl Pauls 
+1

regards,

Karl

On Thu, Nov 30, 2017 at 3:54 PM, Carsten Ziegeler  wrote:
> +1
>
>
> Ian Boston wrote
>> Hi,
>>
>> We solved 2 issues in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12341395
>>
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1822/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
>>
>> Usage:
>> sh check_staged_release.sh 1822 /tmp/sling-staging
>>
>> Please vote to approve this release:
>>
>>   [ ] +1 Approve the release
>>   [ ]  0 Don't care
>>   [ ] -1 Don't release, because ...
>>
>> This majority vote is open for at least 72 hours.
>>
>> Best Regards
>> Ian
>>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Scripting JSP version 2.3.4

2017-11-30 Thread Carsten Ziegeler 
+1


Ian Boston wrote
> Hi,
> 
> We solved 2 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341395
> 
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1822/
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 1822 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
> This majority vote is open for at least 72 hours.
> 
> Best Regards
> Ian
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Engine 2.6.10, i18n 2.5.10,feature flags 1.2.2, and security 1.1.10

2017-11-30 Thread Stefan Egli 
+1

Cheers,
Stefan

On 28.11.17, 21:39, "Carsten Ziegeler"  wrote:

>Hi,
>
>We solved 1 issue for Engine 2.6.10
>https://issues.apache.org/jira/projects/SLING/versions/12340607
>
>We solved 4 issues for i18n 2.5.10
>https://issues.apache.org/jira/projects/SLING/versions/12339949
>
>We solved 1 issue for Feature Flags 1.2.2
>https://issues.apache.org/jira/projects/SLING/versions/12338140
>
>We solved 1 issue for Security 1.1.0
>https://issues.apache.org/jira/projects/SLING/versions/12342206
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1821
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1821 /tmp/sling-staging
>
>Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
>This majority vote is open for at least 72 hours.
>
>Regards
>Carsten
>-- 
>Carsten Ziegeler
>Adobe Research Switzerland
>cziege...@apache.org

[jira] [Commented] (SLING-7268) unable to create principals and use principals in ACLs on import

2017-11-30 Thread Bertrand Delacretaz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272631#comment-16272631
 ] 

Bertrand Delacretaz commented on SLING-7268:


Could you use repoinit instead to create those users and ACLs? That's the 
recommended way.

See 
https://sling.apache.org/documentation/bundles/repository-initialization.html 
for details

> unable to create principals and use principals in ACLs on import
> 
>
> Key: SLING-7268
> URL: https://issues.apache.org/jira/browse/SLING-7268
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR ContentLoader 2.2.6
>Reporter: Andres Bott
>Priority: Minor
>
> Not able to use principals and ACLS on the same bundle when defining initial 
> content
> ie:
> {
>   "jcr:primaryType" : "sling:Folder",
>   "security:principals": [
> { "name": "*user*", "password": "mypassword"}
>   ],
>   "security:acl": [
> { "principal": "*user*", "granted": ["jcr:read","jcr:write"] }
>   ]
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7280) Repo Init: Unable to create rep:glob restriction with empty string value

2017-11-30 Thread angela (JIRA) 
angela created SLING-7280:
-

 Summary: Repo Init: Unable to create rep:glob restriction with 
empty string value
 Key: SLING-7280
 URL: https://issues.apache.org/jira/browse/SLING-7280
 Project: Sling
  Issue Type: Bug
  Components: Repoinit
Reporter: angela


[~bdelacretaz], I was asked by a colleague at Adobe how to create a _rep:glob_ 
restriction with an empty string value as it is possible and documented with 
Jackrabbit API. I didn't find how to do that and suspect that it's simply a bug 
in the repo init.

I would appreciate if you could look into this and fix it.

cc: [~marett]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

2017-11-30 Thread angela (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272514#comment-16272514
 ] 

angela commented on SLING-7227:
---

[~bdelacretaz]. can you please take of that? The repo init you invented is 
incomplete, which prevents Adobe from using it despite the fact that it was 
announced as the preferred way of doing things. Thanks.

cc: [~marett]

> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7226) Repo Init: allow to pass intermediate path upon creating service user

2017-11-30 Thread angela (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272513#comment-16272513
 ] 

angela commented on SLING-7226:
---

[~bdelacretaz]. can you please take of that? The repo init you invented is 
incomplete, which prevents Adobe from using it despite the fact that it was 
announced as the preferred way of doing things. Thanks.

cc: [~marett]

> Repo Init: allow to pass intermediate path upon creating service user
> -
>
> Key: SLING-7226
> URL: https://issues.apache.org/jira/browse/SLING-7226
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>
> [~marett], [~bdelacretaz], if I am not mistaken it is currently not possible 
> to pass the second parameter 'intermediatePath' when creating a service user 
> using the repo-init.
> In the Jackrabbit {{UserManager}} API the call looks as follows:
> {code}
> UserManager.createSystemUser(String userID, String intermediatePath)
> {code}
> I would appreciate if both params would be respected by the repo-init and I 
> don't think it should be a big deal adding this.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7226) Repo Init: allow to pass intermediate path upon creating service user

2017-11-30 Thread Timothee Maret (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272497#comment-16272497
 ] 

Timothee Maret commented on SLING-7226:
---

Thanks [~anchela]! I was asking about the {{/}} in order to figure out if we 
_may_ use the existing syntax to carry the path information. With perspective, 
it may be best to modify the syntax to carry the path information.

I agree that we should not apply validations in the Sling code base.

Generally, I won't have the bandwidth to look at this issue in the coming 2 
months though.

cc [~bdelacretaz]

> Repo Init: allow to pass intermediate path upon creating service user
> -
>
> Key: SLING-7226
> URL: https://issues.apache.org/jira/browse/SLING-7226
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>
> [~marett], [~bdelacretaz], if I am not mistaken it is currently not possible 
> to pass the second parameter 'intermediatePath' when creating a service user 
> using the repo-init.
> In the Jackrabbit {{UserManager}} API the call looks as follows:
> {code}
> UserManager.createSystemUser(String userID, String intermediatePath)
> {code}
> I would appreciate if both params would be respected by the repo-init and I 
> don't think it should be a big deal adding this.
> Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7227) Repo Init: Add ability to register custom privileges

2017-11-30 Thread Timothee Maret (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16272491#comment-16272491
 ] 

Timothee Maret commented on SLING-7227:
---

[~anchela] thanks for this improvement, it seems to make sense. I won't have 
the bandwidth to look at it in the coming 2 months though.

cc [~bdelacretaz]

> Repo Init: Add ability to register custom privileges
> 
>
> Key: SLING-7227
> URL: https://issues.apache.org/jira/browse/SLING-7227
> Project: Sling
>  Issue Type: Improvement
>  Components: Repoinit
>Reporter: angela
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a 
> way to register a custom privilege during repo init. I am sure this is an 
> oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, 
> String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[VOTE] Release Apache Sling Scripting JSP version 2.3.4

2017-11-30 Thread Ian Boston 
Hi,

We solved 2 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12341395


Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1822/

You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1822 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

Best Regards
Ian

[jira] [Closed] (SLING-6943) Don't call into service registry from within a synchronized block

2017-11-30 Thread Karl Pauls (JIRA) 

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

Karl Pauls closed SLING-6943.
-

> Don't call into service registry from within a synchronized block
> -
>
> Key: SLING-6943
> URL: https://issues.apache.org/jira/browse/SLING-6943
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Resource Resolver 1.5.32
>
> Attachments: SLING-6943.patch
>
>
> ResourceProviderTracker activates and deactivates resource providers within a 
> synchronized block which then calls get/unget service on the service registry.
> I think we should avoid doing these calls within a sync'ed block



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7252) ResourceResolverImpl.map() does not invoke ResourceDecorator

2017-11-30 Thread Karl Pauls (JIRA) 

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

Karl Pauls closed SLING-7252.
-

> ResourceResolverImpl.map() does not invoke ResourceDecorator
> 
>
> Key: SLING-7252
> URL: https://issues.apache.org/jira/browse/SLING-7252
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.16, Resource Resolver 1.5.30
>Reporter: Francisco Chicharro
>Assignee: Karl Pauls
> Fix For: Resource Resolver 1.5.32
>
> Attachments: resourceresolverimpl.patch
>
>
> ResourceDecorators are invoked by ResourceResolverImpl for resource 
> resolution but not for mapping.
> I'm experiencing this issue with version 1.4.16, but the issue is also there 
> for latest version 1.5.30.
> I'm attaching a patch for 1.4.16 version.
> CC: [~cziegeler]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7009) NPE in ResourceChangeListenerInfo when resource.change.types is not String or String array

2017-11-30 Thread Karl Pauls (JIRA) 

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

Karl Pauls closed SLING-7009.
-

> NPE in ResourceChangeListenerInfo when resource.change.types is not String or 
> String array
> --
>
> Key: SLING-7009
> URL: https://issues.apache.org/jira/browse/SLING-7009
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.5.26
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Resource Resolver 1.5.32
>
>
> When registering a {{ResourceChangeListener}} with 
> {{ResourceChangeListener.CHANGES}} and e.g. {{ChangeType.ADDED}} (enum), 
> ResourceChangeListenerInfo fails with NPE:
> {noformat}
> 2017-07-13T23:55:46,811 | ERROR | RMI TCP Connection(3)-127.0.0.1 | Felix 
>|  -  -  | Bundle org.apache.sling.resourceresolver 
> [110] EventDispatcher: Error during dispatch. (java.lang.NullPointerException)
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.resourceresolver.impl.observation.ResourceChangeListenerInfo.(ResourceChangeListenerInfo.java:120)
>  ~[?:?]
>   at 
> org.apache.sling.resourceresolver.impl.observation.ResourceChangeListenerWhiteboard$1.addingService(ResourceChangeListenerWhiteboard.java:82)
>  ~[?:?]
>   at 
> org.apache.sling.resourceresolver.impl.observation.ResourceChangeListenerWhiteboard$1.addingService(ResourceChangeListenerWhiteboard.java:64)
>  ~[?:?]
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>  ~[?:?]
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
>  ~[?:?]
>   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:901)
>  ~[?:?]
>   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:4579) 
> ~[?:?]
>   at org.apache.felix.framework.Felix.registerService(Felix.java:3571) 
> ~[?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)
>  ~[?:?]
>   at 
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:355)
>  ~[?:?]
> {noformat}
> This should be more robust (try/catch including for-loop).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [RESULT][VOTE] Release Apache Sling Resource Resolver 1.5.32

2017-11-30 Thread Karl Pauls 
Time to call the vote on the Apache Sling Resource Resolver 1.5.32 release.

* +1 votes from Carsten Ziegeler, Antonio Sanso, and Karl Pauls.

* No other votes.

The vote is successful. I will make the artifacts available as soon as possible.

Re: [VOTE] Release Apache Sling Resource Resolver 1.5.32

2017-11-30 Thread Karl Pauls 
+1

regards,

Karl

On Fri, Nov 24, 2017 at 2:07 PM, Antonio Sanso  wrote:
> +1
> On Nov 24, 2017, at 1:24 PM, Karl Pauls  wrote:
>
>> I would like to call a vote on the following release,
>>
>> Apache Sling Resource Resolver 1.5.32
>>
>> We solved 3 issue in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12341241
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1819/
>>
>> You can use this UNIX script to download the release and verify the 
>> signatures:
>> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 1819 /tmp/sling-staging
>>
>> Please vote to approve these releases:
>>
>>  [ ] +1 Approve the releases
>>  [ ]  0 Don't care
>>  [ ] -1 Don't release, because ...
>



-- 
Karl Pauls
karlpa...@gmail.com

[jira] [Closed] (SLING-7264) Switch to OSGi annotation

2017-11-30 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler closed SLING-7264.
---

> Switch to OSGi annotation 
> --
>
> Key: SLING-7264
> URL: https://issues.apache.org/jira/browse/SLING-7264
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: JCR Registration 1.0.4
>
>
> Switch to official OSGi annotations



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SLING-7263) Make RMI package optional

2017-11-30 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler closed SLING-7263.
---

> Make RMI package optional 
> --
>
> Key: SLING-7263
> URL: https://issues.apache.org/jira/browse/SLING-7263
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: JCR Registration 1.0.4
>
>
> org.apache.sling.jcr.registration bundle currently imports following packages
> {noformat}
>   javax.jcr {version=[2.0,3)}
>   javax.naming  
>   javax.naming.spi  
>   javax.transaction.xa  {resolution:=optional}
>   org.apache.jackrabbit.rmi.remote  {version=[2.0,3)}
>   org.apache.jackrabbit.rmi.server  {version=[2.0,3)}
>   org.apache.sling.jcr.registration {version=[1.1,1.2)}
>   org.osgi.framework{version=[1.4,2)}
>   org.osgi.service.component{version=[1.0,2)}
>   org.osgi.service.log  {version=[1.3,2)}
> {noformat}
> Due to required import for "org.apache.jackrabbit.rmi" package this bundle 
> cannot be used on setups where "org.apache.jackrabbit.jackrabbit-jcr-rmi" is 
> not present. To enable usage (JNDI registration part) on such setups we 
> should mark these packages as optional



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[VOTE RESULT] Release Apache Sling JCR Registration 1.0.4

2017-11-30 Thread Carsten Ziegeler 
 The vote passed with three binding +1 votes

THanks

Carsten


> 
> Chetan Mehrotra wrote
>> Hi,
>>
>> We solved 2 issue in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12328687
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1817
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> https://raw.githubusercontent.com/apache/sling-ide-tooling/master/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 1817 /tmp/sling-staging
>>
>> Please vote to approve this release:
>>
>>   [ ] +1 Approve the release
>>   [ ]  0 Don't care
>>   [ ] -1 Don't release, because ...
>>
>> This majority vote is open for at least 72 hours.
>>
>> regards
>> Chetan
>>
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org