You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/24 18:35:50 UTC
[jira] [Commented] (JENA-614) Remove JMX support from ARQ
[ https://issues.apache.org/jira/browse/JENA-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856407#comment-13856407 ]
ASF subversion and git services commented on JENA-614:
------------------------------------------------------
Commit 1553307 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1553307 ]
JENA-614 (Remove JMX support) : step 1 : all JMX specific code pulled into ARQMgt
> Remove JMX support from ARQ
> ---------------------------
>
> Key: JENA-614
> URL: https://issues.apache.org/jira/browse/JENA-614
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> ARQ has some JMX support but JMX is unavailable in verions environments (some OSGi (glassfish), Google App engine, systems using classloader restrictions (ant).
> If JMX can't be started, ARQ operates as normal, but without the static information (e.g. versions) and live query counts.
> The proposal is to remove JMX from ARQ on the assumption that, as a library, such information is better obtained by the using application.
> One such system might be Fuseki which already has a management information framework (it exposes statistics over HTTP).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)