Using ws-jmx-connector for cross platform agent to interoperate with JMX Agent

Now a connecter named ws-jmx-connector has realesed to use for calling JMX agent. This connector uses soap call to connect with JMX agent.
See the project link for more information.
I have download the realease and install. Tried samples delivered with artifact and wondered. it's simple implements of JSR 262.

If you have all ready wiseman worked - this connector will help you to make your development easy.
I have used jax-ws library delivered with wiseman and wise library to compile and run the samples.

Some additional information will be very usefull to run samples under 64bit version of java. I tried java 1.5_014 64 bit version on fedora and got following class not found exception:
java.lang.NoClassDefFoundError: com/sun/xml/ws/developer/MemberSubmissionAddressing$Validation
Download and install JAX-WS RI 2.1.5 which contains the right library jaxws-rt.jar to run all the samples under 64 bit version of JVM.

In the holyday i will make a try to use this connector in our projects.

See also following links:
http://marxsoftware.blogspot.com/2008/05/first-look-at-jmx-web-services.html
http://marxsoftware.blogspot.com/2008/06/second-look-at-jmx-web-services.html

Comments

Book review: High Performance in-memory computing with Apache Ignite by Sadruddin Md

A new title The Apache Ignite book has been released including Ignite 2.6 and above. Read the full book review by Sadruddin Md .

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...

Quick start with In memory Data Grid, Apache Ignite

UP1: For complete quick start guide, see also the sample chapter of the book "High performance in-memory computing with Apache Ignite" here . Even you can find the sample examples from the GitHub repository . IMDG or In memory data grid is not an in-memory relational database, an NoSQL database or a relational database. It is a different breed of software datastore. The data model is distributed across many servers in a single location or across multiple locations. This distribution is known as a data fabric. This distributed model is known as a ‘shared nothing’ architecture. IMDG has following characteristics: All servers can be active in each site. All data is stored in the RAM of the servers. Servers can be added or removed non-disruptively, to increase the amount of RAM available. The data model is non-relational and is object-based. Distributed applications written on the platform independent language. The data fabric is resilient, allowing non-disruptive au...

My workspace

Search This Blog