glassfish
  1. glassfish
  2. GLASSFISH-20714

GlassFish Broker's Use Of An RMI Registry Port Must Be Configurable And Documented

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2.2
    • Fix Version/s: None
    • Component/s: jms
    • Labels:
      None
    • Environment:

      Generic

      Description

      This issue is related to GLASSFISH-20707 and GLASSFISH-20708.

      The MQ broker's use of an RMI Registry port, in both embedded and local mode, needs to be something that can be controlled and configured by the end user, rather than having the resource adapter pick an arbitrary port of its own choosing - even if the value used can be predicted (mq broker port + 100).

      The use of the RMI port also needs to be documented and explained and absolutely MUST be included in the list of known ports.

      See: http://docs.oracle.com/cd/E26576_01/doc.312/e24939/release-notes.htm#ggpoq

      which lists the MQ port mapper, admin and jms ports, and how the admin and jms ports can be configured. The same level of detail will be needed with the RMI Registry port.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              David Zhao
              Reporter:
              tecknobabble
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: