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

Fabric container not properly updating JMX ports

XMLWordPrintable

    • % %
    • Hide

      Create a Fabric and update the RMI Server and RMI Registry ports using a profile similar to the following:

      JBossFuse:karaf@root> profile-display management 
Profile id: management
Version   : 1.0
Attributes: 
	parents: default
Containers: root

Container settings
----------------------------

Configuration details
----------------------------
PID: org.apache.karaf.management
  rmiServerPort 44445
  rmiRegistryPort 1199



Other resources
----------------------------
Resource: ReadMe.md
JBossFuse:karaf@root>

      After this is applied to the container confirm the JMX Service URL is properly updated.

      Then attempt to make a JMX connection to this container.

      Show
      Create a Fabric and update the RMI Server and RMI Registry ports using a profile similar to the following: JBossFuse:karaf@root> profile-display management Profile id: management Version : 1.0 Attributes: parents: default Containers: root Container settings ---------------------------- Configuration details ---------------------------- PID: org.apache.karaf.management rmiServerPort 44445 rmiRegistryPort 1199 Other resources ---------------------------- Resource: ReadMe.md JBossFuse:karaf@root> After this is applied to the container confirm the JMX Service URL is properly updated. Then attempt to make a JMX connection to this container.
    • 6.3 Sprint 4 (Mar 28 - Apr 29)

      After updating the RMI server and RMI registry ports fabric still attempts to make connections to the default 44444 and 1099 ports. Also, even though the JMX Service URL reflects the updated ports it doesn't appear the RMI server gets started as nothing can be found listening on the RMI server port.

            janstey@redhat.com Jonathan Anstey
            rhn-support-jsherman Jason Sherman
            Roman Jakubco Roman Jakubco (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: