2011-02-02 91 views
3

我正在尝试遵循Java API文档中的一个示例(http://download.oracle.com/javase/1.5.0/docs/api/java/lang/management/ MemoryPoolMXBean.html#Notification)与Memory Pool Beans和通知的UsageThreshold属性相关。每当游泳池超过门槛时,我的意图就是做一些事情。这是示例代码:远程JMX连接和通知问题

MemoryPoolMXBean remoteOldGenMemoryPool = 
    ManagementFactory.newPlatformMXBeanProxy(
     jmxServer, 
     "java.lang:type=MemoryPool,name=PS Old Gen", 
     MemoryPoolMXBean.class); 


class MyListener implements javax.management.NotificationListener { 
    public void handleNotification(Notification notification, Object handback) { 
     String notifType = notification.getType(); 
     if (notifType.equals(MemoryNotificationInfo.MEMORY_THRESHOLD_EXCEEDED)) { 
     // Do Something 
     println "Threshold passed"; 
     } 
    } 
    } 

// Register MyListener with MemoryMXBean 
MemoryMXBean remoteMemory = 
     ManagementFactory.newPlatformMXBeanProxy(
      jmxServer, 
      ManagementFactory.MEMORY_MXBEAN_NAME, 
      MemoryMXBean.class); 

NotificationEmitter emitter = remoteMemory as NotificationEmitter; 
MyListener listener = new MyListener(); 
emitter.addNotificationListener(listener, null, null); 

remoteOldGenMemoryPool.setUsageThreshold 500000000; 

当我执行的代码,并连接到我的JVM,我可以看到以下内容:

Threshold passed 
02-Feb-2011 16:30:00 ClientCommunicatorAdmin restart 
WARNING: Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
    java.net.SocketException: Connection reset] 
02-Feb-2011 16:30:03 RMIConnector RMIClientCommunicatorAdmin-doStop 
WARNING: Failed to call the method close():java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
    java.net.SocketException: Connection reset 
02-Feb-2011 16:30:03 ClientCommunicatorAdmin Checker-run 
WARNING: Failed to check connection: java.net.SocketException: Connection reset 
02-Feb-2011 16:30:03 ClientCommunicatorAdmin Checker-run 
WARNING: stopping 

出于某种原因(我不明白还)代码正在尝试重新启动与JVM的连接。任何想法为什么会发生这种情况,或者如何预防这种情况?我在做错吗?

感谢

+2

看来这实际上是一个让JMX连接保持活着的问题。 ClientCommunicatorAdmin内有一个守护线程(Checher),每分钟检查一次连接。 – Gotxi 2011-02-03 11:45:50

回答

0

可能是你可以添加一个变量JMX的环境,这样的: m.put( “jmx.remote.x.client.connection.check.period”,0L);

但是,我遇到的是与此有点不同。 你可以看到:http://chainhou.iteye.com/blog/1906688