On 12-11-10 13:23, Dennis Reedy wrote:
Would using the the JSR 160 approach where a service adds
net.jini.look.entry.jmx.* attributes to its collection of attributes
it maintains with it's service registration also work? That way a JMX
connection can be established to the service's JVM, allowing jconsole
or visualvm to display (even profile) JVM details?

JMX would be nice.

Gr. Sim

--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397

Reply via email to