Use JMX joloesb to monitor Mule esb

Jolow.1.0.6: http://www.jolokia.org/agent/mule.html

Mule esb 3.3.0: http://www.mulesoft.org

Now more and more integrated platforms use the Mule Enterprise Service Bus middleware. The monitoring program of the Mule Enterprise Edition is charged. However, the Mule daxie is still somewhat conscientious and implements many MBEAN interfaces, JMX interfaces are provided to implement the custom monitoring interface.

The structure of the preparation is as follows:

Add a JMX proxy to the Mule and create a new flow. The Code is as follows:

<? Xml version = "1.0" encoding = "UTF-8"?>

<Mule xmlns = "http://www.mulesoft.org/schema/mule/core"
Xmlns: xsi = "http://www.w3.org/2001/XMLSchema-instance"
Xmlns: management = "http://www.mulesoft.org/schema/mule/management"
Xmlns: spring = "http://www.springframework.org/schema/beans"
Xsi: schemaLocation ="
Http://www.mulesoft.org/schema/mule/core
Http://www.mulesoft.org/schema/mule/core/3.1/mule.xsd
Http://www.springframework.org/schema/beans
Http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
Http://www.mulesoft.org/schema/mule/management
Http://www.mulesoft.org/schema/mule/management/3.1/mule-management.xsd>

<! -- Jmx configuration -->
<Custom-agent name = "jolow.agent" class = "org. jolow.mule. JolokiaMuleAgent">
<Spring: property name = "port" value = "8099"/>
</Custom-agent>
<Management: jmx-server>
<Management: connector-server url = "service: jmx: rmi: // jndi/rmi: // localhost: 7099/mule" rebind = "true"/>
</Management: jmx-server>
</Mule>

Attachment: package of Mule-Agent: jolokia-mule-1.0.6-agent.jar needs to be added to class directory

Reference: http://www.jolokia.org/agent/mule.html

Running result:

The following information is printed, indicating that JMX is successfully added.

Open http: // casking-soa-PC: 8099/jolokia to view the version.

Memory condition and recovery operations:

Http: // 127.0.0.1: 8099/jolokia/read/java. lang: type = Memory

Http: // 127.0.0.1: 8099/jolokia/exec/java. lang: type = Memory/gc

Operating System Information

Http: // 127.0.0.1: 8099/jolow./ read/java. lang: type = OperatingSystem

Running Environment

Http: // 127.0.0.1: 8099/jolokia/read/java. lang: type = Runtime

Overall thread status

Http: // 127.0.0.1: 8099/jolokia/read/java. lang: type = Threading

Class Loading

Http: // 127.0.0.1: 8099/jolokia/read/java. lang: type = ClassLoading

For more methods, see: http://www.jolokia.org/reference/html/protocol.html

With the API, you can write your own custom interface.

Let's take a look at our structure. The Green Section provides standard JMX APIs. Let's test the JConsole.

JDK

Double-click to open and enter the RIM address

1 2 Next Page