Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-2733

Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException when trying to connect to ssh container

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.2
    • jboss-fuse-6.2
    • Fabric8 v1
    • None
    • % %
    • Hide

      1. start ssh server
      2. Start Fuse and create fabric, and wait for provision.
      3. Run commands:

      mq-create --no-ssl --parent-profile=mq-replicated --group a broker-nossl-b

profile-edit --system org.apache.activemq.leveldb.test=true mq-broker-a.broker-nossl-b

fabric:container-create-ssh --user USER --host 127.0.0.1  --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c0

fabric:container-create-ssh --user USER --host 127.0.0.1  --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c1

fabric:container-create-ssh --user USER --host 127.0.0.1  --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c2

      4. Wait for all containers to start successfully (check with 'container-list') command

      5. For each ssh containers run command 

      container-info broker-nossl-b-c0
container-info broker-nossl-b-c1
container-info broker-nossl-b-c2

      and try to connect to jmx using JMX url provided. It connects successfully.

      6. stop fuse
      7. kill all container processes

      pkill -f karaf

      and check that there are no more karaf processes

      ps aux| grep karaf

      8. Delete fuse/data and fuse/instances folders
      9. Delete HOME/containers folder
      10. In the same Linux terminal repeat steps 2-5.
      The connection to the last container karaf-broker-nossl-b-c2 fails. It seems to work the same way if instead amq containers use containers with other profiles.

      Show
      1. start ssh server 2. Start Fuse and create fabric, and wait for provision. 3. Run commands: mq-create --no-ssl --parent-profile=mq-replicated --group a broker-nossl-b profile-edit --system org.apache.activemq.leveldb.test= true mq-broker-a.broker-nossl-b fabric:container-create-ssh --user USER --host 127.0.0.1 --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c0 fabric:container-create-ssh --user USER --host 127.0.0.1 --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c1 fabric:container-create-ssh --user USER --host 127.0.0.1 --profile mq-broker-a.broker-nossl-b --password PASSWORD broker-nossl-b-c2 4. Wait for all containers to start successfully (check with 'container-list') command 5. For each ssh containers run command container-info broker-nossl-b-c0 container-info broker-nossl-b-c1 container-info broker-nossl-b-c2 and try to connect to jmx using JMX url provided. It connects successfully. 6. stop fuse 7. kill all container processes pkill -f karaf and check that there are no more karaf processes ps aux| grep karaf 8. Delete fuse/data and fuse/instances folders 9. Delete HOME/containers folder 10. In the same Linux terminal repeat steps 2-5. The connection to the last container karaf-broker-nossl-b-c2 fails. It seems to work the same way if instead amq containers use containers with other profiles.

    Description

      After restarting fabric (in the same Linux terminal window), the JMX connection to the 3rd ssh container fails(all containers run on the same host where fabric is started).
      The JMX url is aquired using container-info command.
      JMX connection fails both via jconsole and java client. (The java client from https://issues.jboss.org/browse/ENTESB-1611 can be used).
      The java client throws exception:

      java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: karaf-broker-nossl-b-c2
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369)
	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268)
	at SimpleJMX.main(SimpleJMX.java:42)
Caused by: javax.naming.NameNotFoundException: karaf-broker-nossl-b-c2
	at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:116)
	at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:203)
	at javax.naming.InitialContext.lookup(InitialContext.java:411)
	at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1936)
	at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1903)
	at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286)
	... 2 more

      JMX url for karaf-broker-nossl-b-c2:

      service:jmx:rmi://vpn1-51-195.bne.redhat.com:44447/jndi/rmi://vpn1-51-195.bne.redhat.com:1102/karaf-broker-nossl-b-c2

      Among open ports for process corresponding to karaf-broker-nossl-b-c2 there is no port 44447.

      [emedvede@dhcp-4-224 jboss-fuse-6.2.0.redhat-066]$ ss -lntp| grep 15568
LISTEN     0      50                       :::8104                    :::*      users:(("java",15568,296))
LISTEN     0      50                       :::1102                    :::*      users:(("java",15568,293))
LISTEN     0      1          ::ffff:127.0.0.1:42542                   :::*      users:(("java",15568,274))
LISTEN     0      50                       :::52759                   :::*      users:(("java",15568,92))
LISTEN     0      1          ::ffff:127.0.0.1:38039                   :::*      users:(("java",15568,43))
LISTEN     0      50                       :::8184                    :::*      users:(("java",15568,127))

      For another container, for which jmx works, the corresponding port 44446 was opened.

      Attachments

        1. bundle6_missing.png
          bundle6_missing.png
          26 kB
        2. container-log-101.zip
          166 kB
        3. container-logs.zip
          98 kB
        4. fuse-101.log
          814 kB
        5. karaf_mamanment_c0.png
          karaf_mamanment_c0.png
          110 kB
        6. karaf.management_pic.png
          karaf.management_pic.png
          88 kB
        7. org.apache.karaf.management.cfg
          2 kB
        8. root-fuse.log
          363 kB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-2190 io.fabric8.common.util.MultiException when deploying more broker instances in fabric

          • 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.
          • Closed

          Activity

            People

              ggrzybek Grzegorz Grzybek
              emedvede Elena Medvedeva (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: