Jolokia

Jolokia should support JMX notifications, too. Two modes are possible: * Pull: A client periodically polls the agents for new notifications. The agent will queue notifications, which has been registered before. * Push: Either a cometd...

Add a python library, similar in spirit as the jmx4perl Perl binding.

Add a Groovy client library.

Assuming, that a Jolokia Javascript client binding is already there, it would be nice to have some Javascript widget (YUI or jQuery UI or whatever) for graphing or showing JMX values. These widgets should use the JolokiaJS library.

In addition to package the policy file within a the war-agent, it should be possible to proided the policy by more dynamic means. E.g. lookup in LDAP or via an upload over an MBean (with local storage on the agent side and passwort protected after...

Add scala as a client library

Please add integrations tests based on Citrus.

I'd like to secure (via https) the JSR-160 communication which is used for going from the JMX proxy to the target server. Proxy code should handle client certificates. Requests forwarded with username/password in clear-text to the target server is...

It would be nice, if there is an (optional) way for autodetecting the Agent. The idea is to allow the agent for listening on a UDP broadcast port and answering with iths agent URL. The broadcast mechanism should be configurable. Still open: Can...

It would be great to extend the allow deny policy for MBeans Currently it seems that access to all MBeans is allowed if you have read access and don't specify the others explicitly. Therefore a more strict Approach would be good without having...

Add a Ruby client library (or JRuby)

The current proxy mode can be enhanced in various ways. * JSR-160 connection pooling. * Policy where the proxy is allowed to connect to.

An specialized agent could store historically values in a persistence instead of keeping them in Memory only. Also, it would be cool, if the agent itself could periodically query attributes/operations and stores them in the backend (timer based).

In addition to the JSR-160 proxy it would be nice to have a dispatcher for Jolokia requests. This is useful for a forthcoming JavaScript binding to overcome the 'same location' JS policy. Technically it should work the same as the JSR-160 proxy...

Eclipse Virgo (http://www.eclipse.org/virgo) is the continuation of the dm Server project and provides an OSGi container as part of the Virgo Web Server or, possibly more relevantly, as part of the Virgo Kernel. Please consider testing the OSGi...

The WAR Agent was tested on dm Server 2.0. Eclipse Virgo (http://www.eclipse.org/virgo) is the continuation of the dm Server project. Please consider testing the WAR Agent against Virgo Web Server 2.1.0.

Configuration is currently done via servlet init parameters, which need to be set in the war agent application's web.xml Configuration could be externalized if other Servlet specification compatible means could be used. Using ServletContext...