Uploaded image for project: 'Fuse Tooling'
  1. Fuse Tooling
  2. FUSETOOLS-1939

Several seconds/minutes of UI freeze when accessing JMX nodes of Camel MBean of a lost connection

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 8.0.0
    • None
    • None
    • Hide
      • Deploy a camel route as local process
      • expand some nodes in JMX view under Camel (but not all)
      • kill the process (from terminate button in Console view for instance)
      • try to expand other nodes

      OR

      • Deploy a camel route as local process
      • expand some nodes in JMX view under Camel (but not all)
      • kill the process (from terminate button in Console view for instance)
      • redeploy a the camel route
      • try to expand some nodes in JMX views
      Show
      Deploy a camel route as local process expand some nodes in JMX view under Camel (but not all) kill the process (from terminate button in Console view for instance) try to expand other nodes OR Deploy a camel route as local process expand some nodes in JMX view under Camel (but not all) kill the process (from terminate button in Console view for instance) redeploy a the camel route try to expand some nodes in JMX views

    Description

      seems t be due to a new JMX connection everytime we access hashcode of a *Node: org.fusesource.ide.jmx.camel.navigator.RoutesNode.hashCode() for isntance

         java.lang.Thread.State: RUNNABLE
	at java.net.DualStackPlainSocketImpl.connect0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	- locked <0x00000000eb5bc4c0> (a java.net.DualStackPlainSocketImpl)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at java.net.Socket.<init>(Socket.java:434)
	at java.net.Socket.<init>(Socket.java:211)
	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130)
	at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
	at javax.management.remote.rmi.RMIConnectionImpl_Stub.getAttribute(Unknown Source)
	at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:906)
	at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
	at com.sun.proxy.$Proxy56.getManagementName(Unknown Source)
	at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.fusesource.ide.camel.model.service.core.jmx.camel.CamelFacadeSupport$1.invoke(CamelFacadeSupport.java:57)
	at com.sun.proxy.$Proxy57.getManagementName(Unknown Source)
	at org.fusesource.ide.jmx.camel.navigator.CamelContextNode.getManagementName(CamelContextNode.java:140)
	at org.fusesource.ide.jmx.camel.navigator.RoutesNode.hashCode(RoutesNode.java:186)
	at org.fusesource.ide.jmx.camel.navigator.RoutesNode.equals(RoutesNode.java:177)
	at java.util.HashMap.getNode(HashMap.java:571)
	at java.util.HashMap.get(HashMap.java:556)
	at org.eclipse.ui.internal.navigator.extensions.StructuredViewerManager.getData(StructuredViewerManager.java:122)

      Attachments

        Issue Links

          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) FUSETOOLS-1975 Properly detect lost connection from JMX view

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              apupier@redhat.com Aurélien Pupier
              apupier@redhat.com Aurélien Pupier
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: