My Oracle Support Banner

GlassFish Server Instance Running an Embedded Message Queue Broker Opens an Extra Port at (Broker Port + 100) (Doc ID 1582247.1)

Last updated on NOVEMBER 02, 2020

Applies to:

Oracle GlassFish Server - Version 3.1.2 to 3.1.2 [Release 3.1]
Information in this document applies to any platform.

Symptoms

NOTE: The attribute values used represent fictitious sample names that made up as examples. Ports are used as example to clarify the issue.
Any similarity to actual code, is purely coincidental and not intended in any other manner.

=========

It is noticed than when a GlassFish Server instance is started, which is using an embedded Message Queue (MQ) broker, that there is a port opened whose value is 100 greater than the broker's principle portmapper port.  For example, if the MQ broker is using the default port of 7676, then the GlassFish instance's process also has port 7776 open.  In the following example the broker portmapper port is 31206:

The broker's portmapper port can be seen as the last port in the URL, with the RMI port listed before it, as highlighted in the output above.

Please note that there is also an ephemeral port being used, as there is No port listed following the first appearance of the hostname in the url, "<host>".

Therefore there are three ports that this article discusses:

  1. JMX RMI Port
  2. RMI Port
  3. Broker Port Mapper Port

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.