JMX integration

• Key: DIRMINA-29
• Type: New Feature
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Julien Vermillard
• Reporter: Trustin Lee
• Affects Version/s: 0.7.0, 0.8.0, 0.9.0, 1.0.0
• Fix Version/s: 1.0.0

Comments

[Trustin Lee]

* The current/maximum number of connections
* Traffic information provided by IoSession for all connections; admins should have fine-grained view.
* The ratio of the actual running time of MINA and total uptime for the application.
* Thread pool information
* ByteBuffer pool information; memory usage, the number of pooled buffers for each different buffer size
* The list of ports and transport types held by MINA
* Spying a specific connection using JMX notification

We appreciate any idea!

[Julien Vermillard]

* modifing the filter chain

[Julien Vermillard]

* closing a connection
* closing all the conections

[Julien Vermillard]

simple session MBean, a starting idea for implementation

[Julien Vermillard]

proxying to IoSession implementation

[Julien Vermillard]

i'm working on a first implmentation for now it permit to know the number of bytes written and read and to close the connection.


I simply add it to my MBeanServer in the IoHandler session created :

public void sessionCreated(IoSession session) throws Exception {
((SocketSession)session).setTcpNoDelay(true);

// add the codec in the filter chain
ProtocolCodecFactory codec;
codec = new NettyCodecFactory(new PAMessageRecognizer(PAMessageRecognizer.SERVER_MODE));
        session.getFilterChain().addFirst("protocolFilter", new ProtocolCodecFilter( codec ) );
        
        // JMX instrumentation
try {
SessionManager sessMgr=new SessionManager(session);
MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();
ObjectName name = new ObjectName("archean.util.mina:type=SessionManger,cnx="+session.getRemoteAddress().toString().replace(':','/'));
mbs.registerMBean(sessMgr, name);
} catch (JMException e) {
log.error("JMX Exception : ",e);
}
}

[Julien Vermillard]

I'm actively working on the SessionManager toy :)

I added support for :
- operations for adding and removing LoggingFilter at First or End of the chain for dumping decodec message and ByteBuffer
- display list of filters (nameas and class)
- avg byte/sec sent and recieved since the begin of the connection (a profiler filter would be usefull)
- display of local and remote SocketAddress

for now it work well for my debuging needs : kill buggy connections, activate dumping, watch if it's alive (rcv/sent byte counters)

[Trustin Lee]

Keep up the great work!!!

[Julien Vermillard]

managing ByteBuffer, displaying infos about memory usage

[Julien Vermillard]

MBean interface for manage ByteBuffer pool

[Julien Vermillard]

ByteBuffer modified for getting memory usage information

[Julien Vermillard]

mistake I attached the files without any javadoc comments

[Trustin Lee]

Thanks for continuing contribution! :D

I feel like we'll have JMX support earlier than we expected thanks to your work.

[Julien Vermillard]

mistake : I used the hardcoded value 1 in place of MINIMUM_CAPACITY

[Julien Vermillard]

* bundled everything (except ByteBuffer patch)
* added ServiceRegistry manager (can list service and unbind specified ones per port or name)

[Federico Bonelli]

You have done a great work!
I really like this stuff!
Is this JMX integration already in some 0.9.x version?

[Julien Vermillard]

nop it's not integrated, it's still work-in-progress but you can add the files to your MINA it works well (I use it everyday now).
I'm gonig to finsih ThreadPool and Service monitoring next month (normaly).

[peter royal]

ThreadPoolFilterMBean committed to svn.

[Trustin Lee]

I didn't know that this issue is being watched by this many people. Why don't we include Julien's patch now? I'll apply the patches.

[Julien Vermillard]

Added simple throughput analize : a thread, calculate the thoughput on the X millis seconds.
removed the stupids tabular datas

[Julien Vermillard]

how it's looking in JConsole

[Trustin Lee]

Now we've got a basic integration with JMX. We will continue improving this feature at the next unstable branch.