Extremely poor performance with NIO...

So far, so good. I haven’t subjected it to heavy load, but it’s been handling website-tasks (HTTP) on the net for a week nonstop with no crashes. I’ve recently added some simple load and performance-measures which give figures representing “typical” and “recent” performance (e.g. using rolling-means/ranges and mean-with-feedback/hysteresis).

We’re going to external alpha test v.soon, so I’ll hopefully have some stats to verify things going OK. However, I wish SNMP was integrated into java in a much easier fashion (PS thanks to leknor for pointer to JMX). It appears right now that the best you can get is to use a J2EE server which supports JMX (it seems that only j2ee vendors currnetly have JMX solutions?), and even JMX is a bitch to get started with. And there’s no way I’m touching J2EE for this project - even if Sun bribed me hint, hint (nah, not even then :)).

1.4.2 - I waited until I could test it on the gold release before submitting bug etc.

The current downloads pump out (on the client side only, oops) the java version etc, so people could just cut and paste them along with figures.

If you only want to use jmx maybe you should give jboss a try?
They have a modular server which supposedly gives you the ability to strip out all services you don’t want (ejb, jndi, webserver, etc etc ) and only keep the jmx bit, this is done by editing a xml configuration file.

Not sure if this is what you want, but I thought I could as well let you know (if you didn’t already :wink:

Ah, yes, their move to a micro-kernel. I’m afraid I still haven’t got out of the habit of thinking “JBoss == opensource J2EE”. You’re correct that I ought to try a stripped-down version and see how good it is, although I still have nightmares about having tried to do that with things like linux before (where it is architecturally and theoretically easy, but in practice often just pain, pain, and more pain, depending on what you are trying to do).

The biggest question is going to be how easy it is to integrate with an existing server - whilst maintaining security policies and architectural constraints.