geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Sisson (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1349) Missing Ports in Startup Port List
Date Mon, 16 Jan 2006 12:07:20 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1349?page=all ]

John Sisson updated GERONIMO-1349:
----------------------------------

    Attachment: GERONIMO-1349_JMXConnector.patch

The attached patch for the 1.0 branch displays the JMX host and port number in the summary
of listening ports that was specified in the JMXService url.

The following are some example JMXService urls and their associated startup messages (with
this patch applied):

Example 1) service:jmx:rmi://0.0.0.0:9999/jndi/rmi://0.0.0.0:1099/JMXConnector 

  Listening on Ports:
    9999 0.0.0.0 JMX Remoting Server Connector

In the above example, the RMI Connector Server will be bound to the RMIRegistry running on
port 1099 and the RMIConnection and RMIServer remote objects will be bound to port 9999, listening
on any IP addresses (0.0.0.0).

Example 2) service:jmx:rmi:///jndi/rmi://0.0.0.0:1099/JMXConnector

  Listening on Ports:
       0 192.168.0.21 JMX Remoting Server Connector

In the above example, the RMI Connector Server will be bound to the RMIRegistry running on
port 1099 and the RMIConnection and RMIServer remote objects will be bound to a random port,
on the localhost.  Since the port is random it isn't firewall friendly.

Example 3) service:jmx:rmi://0.0.0.0/jndi/rmi://0.0.0.0:1099/JMXConnector
  Listening on Ports:
       0 0.0.0.0 JMX Remoting Server Connector

In the above example, the RMI Connector Server will be bound to the RMIRegistry running on
port 1099 and the RMIConnection and RMIServer remote objects will be bound to a random port,
listening on any IP addresses (0.0.0.0).  Since the port is random it isn't firewall friendly.

AFAIK, it is not possible for Geronimo's JMXConnector code to determine what random port was
chosen if you just pass the JMXService url specified in th plan to the JMXConnectorServerFactory.
 The only way we could display the random port that was assigned by the operating system,
rather than displaying '0' is to call getLocalPort() on a ServerSocket and then close the
ServerSocket then call the JMXServiceURL(..) constructor with that port in it.

Could you please comment on whether you think we should display 0 or the port obtained by
the OS (by jumping through hoops).  Also we need to decide whether we want the port (e.g.
9999) specified in the JMXService urls.  We also need to get patch the installer and installer
assembly.

> Missing Ports in Startup Port List
> ----------------------------------
>
>          Key: GERONIMO-1349
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1349
>      Project: Geronimo
>         Type: Bug
>   Components: startup/shutdown
>     Versions: 1.0-M5, 1.0
>     Reporter: Aaron Mulder
>     Assignee: Aaron Mulder
>      Fix For: 1.1, 1.0.1
>  Attachments: GERONIMO-1349_JMXConnector.patch
>
> The port list for Geronimo is:
>   Listening on Ports:
>     1099 0.0.0.0   RMI Naming
>     1527 0.0.0.0   Derby Connector
>     4201 0.0.0.0   ActiveIO Connector EJB
>     4242 0.0.0.0   Remote Login Listener
>     8019 127.0.0.1 Jetty Connector AJP13
>     8080 0.0.0.0   Jetty Connector HTTP
>     8443 0.0.0.0   Jetty Connector HTTPS
>    61616 0.0.0.0   ActiveMQ Message Broker Connector
> The port list from netstat is:
> tcp        0      0 :::1099                 :::*                    LISTEN      8447/java
> tcp        0      0 :::1389                 :::*                    LISTEN      8447/java
> tcp        0      0 :::1527                 :::*                    LISTEN      8447/java
> tcp        0      0 :::4201                 :::*                    LISTEN      8447/java
> tcp        0      0 :::4242                 :::*                    LISTEN      8447/java
> tcp        0      0 127.0.0.1:8019          :::*                    LISTEN      8447/java
> tcp        0      0 :::8080                 :::*                    LISTEN      8447/java
> tcp        0      0 :::8443                 :::*                    LISTEN      8447/java
> tcp        0      0 :::16321                :::*                    LISTEN      8447/java
> tcp        0      0 :::61616                :::*                    LISTEN      8447/java
> The differences are:
> 1389 -- Directory
> variable -- 16321 (16333 on next run) -- what is this??

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message