sanity
Blaine Simpson <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
I've finally remembered how I used to do remote JMX without any lookup facility. I used the JMXMP connector, which works perfectly fine without any lookups nor runny any extra service, just by using URLs like "service:jmx:jmxmp://balder:2004". (Not to mention support for TLS encryption). Too bad that mx4j doesn't implement the Generic Connector, because most applications don't need dynamic discovery. DNS manages to provide the needed indirection for every http server on the www, and it works just as well for Jmx. If I have outside JMX clients for my mx4j jmx service, in addition to not having portable encryption support, I have to protect an otherwise unnecessary JNDI service and open it up through the firewalls. Any plans for implementing the Generic Connector in the future? I could do the TLS part at least (having done same for the hsqldb project). -- Don't pray in my school, and I won't think in your church. ICF: 703-934-3692 Cell: 703-944-9317 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click