incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Spicar (JIRA)" <>
Subject [jira] [Updated] (CLEREZZA-606) A tool for monitoring file descriptors held open by CRIS
Date Fri, 15 Jul 2011 20:21:59 GMT


Daniel Spicar updated CLEREZZA-606:

    Attachment: ZZ-606-rdf.cris.monitoring-issue-20110715.diff

Initial Version.

The patch is to applied to the issues repository folder. It creates a new issue 'CLEREZZA-606'
with a new project 'rdf.cris.monitoring'.

This version is offering basic monitoring functionality.
- It can be configured trough Felix Config Admin/Web Console.
- Currently only supporting Linux Operating System.
- Only tested with patch from issue CLEREZZA-564 applied.
- A web resource displaying the statistics can be found at http://localhost:8080/admin/monitoring/cris/
- A threshold can be configured and a threshold url. When the Platform uses more than threshold
file descriptors, then a GET request on the threshold url is performed (allows to call optimize
via a jaxrs resource for example).
- Because GraphIndexer is not a service, you need to configure the bundle id (the number next
to the bundle that uses an instance of GraphIndexer that is displayed when you enter 'ps'
on the clerezza console.
- You also need to supply the path to the folder where the index lies. This path is relative
to the configured bundle's data folder.

> A tool for monitoring file descriptors held open by CRIS
> --------------------------------------------------------
>                 Key: CLEREZZA-606
>                 URL:
>             Project: Clerezza
>          Issue Type: New Feature
>            Reporter: Daniel Spicar
>         Attachments: ZZ-606-rdf.cris.monitoring-issue-20110715.diff
> On UNIX systems CRIS can open many file descriptors which can lead to CRIS stopping to
work. A tool that monitors the file descriptors held by CRIS will help administrators and
developers to optimize and configure CRIS for their environment and use cases.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message