[GitHub] [felix-dev] bosschaert merged pull request #88: FELIX-6444 Contribute a compatible implementation of OSGi Features
bosschaert merged pull request #88: URL: https://github.com/apache/felix-dev/pull/88 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (FELIX-6320) Better logging for the case bundle org.apache.felix.rootcause is not available
[ https://issues.apache.org/jira/browse/FELIX-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6320. --- > Better logging for the case bundle org.apache.felix.rootcause is not > available > --- > > Key: FELIX-6320 > URL: https://issues.apache.org/jira/browse/FELIX-6320 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Affects Versions: healthcheck.generalchecks 2.0.6 >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Fix For: healthcheck.generalchecks 2.0.8 > > > For the case org.apache.felix.rootcause is not installed, currently the log > is missing the components/services that are actually missing (it just prints > a summary on how many components/services are missing). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6400) Reduce resource consumption during component checks
[ https://issues.apache.org/jira/browse/FELIX-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6400. --- > Reduce resource consumption during component checks > --- > > Key: FELIX-6400 > URL: https://issues.apache.org/jira/browse/FELIX-6400 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Affects Versions: healthcheck.generalchecks 2.0.6 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: healthcheck.generalchecks 2.0.8 > > > the components health check is each time (every 5 secs) iteration over all DS > components just to check for a few. The iteration includes access to the > service registry which (in Felix framework 6.x) has a lock > There are two optimizations: > - components check should only check for the configured ones instead of > iterating over all components just to find the ones interested in > - the resultcan be cached until an event occurs (service changed event of the > SCR runtime as the runtime has a change count property to exactly avoid > polling) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6344) HealthCheckExecutor can run into endless failures in case a health check throws a java Error
[ https://issues.apache.org/jira/browse/FELIX-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6344. --- > HealthCheckExecutor can run into endless failures in case a health check > throws a java Error > > > Key: FELIX-6344 > URL: https://issues.apache.org/jira/browse/FELIX-6344 > Project: Felix > Issue Type: Bug > Components: Health Checks >Affects Versions: healthcheck.core 2.0.8 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: healthcheck.core 2.0.10 > > > We had this exception happening on a system every few seconds: > [https://gist.github.com/cschneider/2840339f86faf5a46d2a8a94f0617e76] > The root cause was an error in class loading which resulted in the > DsComponentsCheck running into a java Error. > The problem then was that the finish method in the FutureTask was never > called and so the future always stayed in the list of futures to check and > always returned the Error again. > > I supected that we simply should catch Throwable in the code below: > https://github.com/apache/felix-dev/blob/master/healthcheck/core/src/main/java/org/apache/felix/hc/core/impl/executor/HealthCheckFuture.java#L75 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6447) Log every status change of a HC
[ https://issues.apache.org/jira/browse/FELIX-6447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6447. --- > Log every status change of a HC > --- > > Key: FELIX-6447 > URL: https://issues.apache.org/jira/browse/FELIX-6447 > Project: Felix > Issue Type: Improvement > Components: Health Checks >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: healthcheck.core 2.0.10 > > > The result of a HC is currently not logged, which makes it difficult to trace > the state of a HC over time. > We should log every change for each HC -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6240) NPE in StatusWriterJson if description is null
[ https://issues.apache.org/jira/browse/FELIX-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6240. --- > NPE in StatusWriterJson if description is null > -- > > Key: FELIX-6240 > URL: https://issues.apache.org/jira/browse/FELIX-6240 > Project: Felix > Issue Type: Bug > Components: System Ready >Affects Versions: systemready-0.4.2 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: systemready-0.5.0 > > > 26.02.2020 18:06:16.642 *ERROR* [FelixLogListener] > org.apache.felix.http.jetty Exception while processing request to > /systemready (java.lang.NullPointerException) java.lang.NullPointerException: > null at > org.apache.felix.systemready.impl.servlet.StatusWriterJson.getStatus(StatusWriterJson.java:52) > [org.apache.felix.systemready:0.4.2] > Systemready should handle this case gracefully by using "" instead of null > for description. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6401) Add deprecation annotations to systemready api
[ https://issues.apache.org/jira/browse/FELIX-6401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6401. --- > Add deprecation annotations to systemready api > -- > > Key: FELIX-6401 > URL: https://issues.apache.org/jira/browse/FELIX-6401 > Project: Felix > Issue Type: Improvement > Components: System Ready >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: systemready-0.5.0 > > > As the systemready api is superseeded by health checks, the api should be > marked as such -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6399) Reduce resource consumption during component checks
[ https://issues.apache.org/jira/browse/FELIX-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6399. --- > Reduce resource consumption during component checks > --- > > Key: FELIX-6399 > URL: https://issues.apache.org/jira/browse/FELIX-6399 > Project: Felix > Issue Type: Improvement > Components: System Ready >Affects Versions: systemready-0.4.2 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: systemready-0.5.0 > > > the components readycheck is each time (every 5 secs) iteration over all DS > components just to check for a few. The iteration includes access to the > service registry which (in Felix framework 6.x) has a lock > There are two optimizations: > - components check should only check for the configured ones instead of > iterating over all components just to find the ones interested in > - the resultcan be cached until an event occurs (service changed event of the > SCR runtime as the runtime has a change count property to exactly avoid > polling) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6445) Recursive reference detection throws excepteion
[ https://issues.apache.org/jira/browse/FELIX-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6445. --- > Recursive reference detection throws excepteion > --- > > Key: FELIX-6445 > URL: https://issues.apache.org/jira/browse/FELIX-6445 > Project: Felix > Issue Type: Bug > Components: rootcause >Affects Versions: rootcause-0.1.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: rootcause-0.2.0 > > > The recursive reference handling in DSRootCause is throwing an > IllegalStateException which is not expected when calling the api, especially > as circular references are a reality -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FELIX-6217) RootCauseCommand#rootcause causes a NoSuchElementException for OSGI comonents that do not exist
[ https://issues.apache.org/jira/browse/FELIX-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed FELIX-6217. --- > RootCauseCommand#rootcause causes a NoSuchElementException for OSGI comonents > that do not exist > --- > > Key: FELIX-6217 > URL: https://issues.apache.org/jira/browse/FELIX-6217 > Project: Felix > Issue Type: Bug > Components: rootcause >Affects Versions: rootcause-0.1.0 >Reporter: Ahmed Musallam >Assignee: Carsten Ziegeler >Priority: Major > Labels: bug > Fix For: rootcause-0.2.0 > > > calling RootCauseCommand#rootcause with a name that does not correspond to an > existing OSGI Component throws a NoSuchElementException. > I've made a simple PR fix on github: https://github.com/apache/felix/pull/221 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[VOTE RESULT] Release Apache Felix Rootcause 0.2.0, Systemready 0.5.0, HealthCheck Core 2.0.10, HealthCheck Generalchecks 2.0.8
The vote passed with 6 binding +1 votes Thanks everyone Regards Carsten -- Carsten Ziegeler Adobe cziege...@apache.org
[jira] [Resolved] (FELIX-6444) Contribute a compatible implementation of OSGi Features
[ https://issues.apache.org/jira/browse/FELIX-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. J. David Bosschaert resolved FELIX-6444. --- Resolution: Fixed > Contribute a compatible implementation of OSGi Features > --- > > Key: FELIX-6444 > URL: https://issues.apache.org/jira/browse/FELIX-6444 > Project: Felix > Issue Type: New Feature >Reporter: A. J. David Bosschaert >Assignee: A. J. David Bosschaert >Priority: Major > > As discussed on the Felix Dev mailing list > (https://www.mail-archive.com/dev%40felix.apache.org/msg52338.html) a > compatible implementation of the OSGi Feature Service should be added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [felix-dev] bosschaert merged pull request #88: FELIX-6444 Contribute a compatible implementation of OSGi Features
bosschaert merged pull request #88: URL: https://github.com/apache/felix-dev/pull/88 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FELIX-6448) Simplify result cache for components check
Carsten Ziegeler created FELIX-6448: --- Summary: Simplify result cache for components check Key: FELIX-6448 URL: https://issues.apache.org/jira/browse/FELIX-6448 Project: Felix Issue Type: Improvement Components: Health Checks, System Ready Affects Versions: systemready-0.5.0, healthcheck.generalchecks 2.0.8 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: systemready-0.6.0, healthcheck.generalchecks 2.0.10 The code to handle the recently introduced cache for ds component results could be improved; both systemready and the hc generalchecks use the same logic -- This message was sent by Atlassian Jira (v8.3.4#803005)
