将服务器移动到新虚拟机后，VisualVM 远程连接看不到“监视器”选项卡或应用程序 mbean
我已经在 VMWare VM 中的 Solaris (5.10) 上运行了 Spring 3.x 应用程序一段时间了。我的应用程序注册了一些 mbean。我已经能够从 VisualVM 远程连接到 VM 并在“监视器”选项卡中查看数据，并且我已经能够在 MBeans 选项卡中查看和操作我的应用程序 mbean。
我的服务器最近移动到另一个 VMWare 虚拟机，但主机名和 IP 地址没有更改。我想，我们已经一切正常了，直到当我尝试从桌面上的 VisualVM 连接到虚拟机时，我注意到一些奇怪的行为。当我第一次尝试时，我认为它工作正常，但是当我仔细观察时，我注意到没有“Monitor”选项卡，当我查看 MBeans 选项卡时，它没有任何我的应用程序 mbean。
我可以运行本地 WebLogic 实例，并且当我在本地使用 VisualVM 连接时没有看到这些问题。
看来这不是防火墙问题。连接成功。在“概述”选项卡中，我可以看到所有基本属性设置。
为什么我的远程连接功能会“降级”？
I've had a Spring 3.x application running on Solaris (5.10) in a VMWare VM for quite a while. My application registers some mbeans. I've been able to connect remotely to the VM from VisualVM and view data in the "Monitor" tab, and I've been able to see and manipulate my application mbeans in the MBeans tab.
My server was recently moved to another VMWare VM, although the host name and IP address didn't change. We got it all working, I thought, until I noticed some odd behavior when I tried to connect to the VM from VisualVM on my desktop. When I first tried it, I thought it was working fine, but when I looked closer I noticed that there was no "Monitor" tab, and when I looked at the MBeans tab, it didn't have any of my application mbeans.
I can run a local WebLogic instance, and I don't see these issues when I connect locally with VisualVM.
It doesn't seem like it would be a firewall problem. The connection succeeded. In the "Overview" tab I can see all the basic property settings.
Why would my remote connection have "degraded" functionality?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
看起来您的远程连接到了错误的 MBeanServer，也就是说，没有连接到 WebLogic Domain Runtime Server，您正在连接到 JVM 的平台 MBeanServer。我不确定，但我认为您应该能够连接到 WebLogic 实例中运行的三个 MBeanServer 中的任何一个，如所述 此处。
还有一个选项可以在平台MBeanServer。
It looks like your remote is connected to the wrong MBeanServer, which is to say, rather than connecting to the WebLogic Domain Runtime Server, you are connecting to the JVM's platform MBeanServer. I'm not certain, but I think you should be able to connect to any of the three MBeanServers running in the WebLogic instance, as outlined here.
There is also an option to register your Weblogic Domain MBeans in the platform MBeanServer.