You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/12/13 19:59:45 UTC
[jira] Created: (GERONIMO-1349) Missing Ports in Startup Port List
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
Reporter: Aaron Mulder
Assigned to: Aaron Mulder
Priority: Blocker
Fix For: 1.0
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
[jira] Updated: (GERONIMO-1349) Missing Ports in Startup Port List
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=all ]
John Sisson updated GERONIMO-1349:
----------------------------------
Fix Version: 1.0.1
Version: 1.0
> 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
>
> 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
[jira] Updated: (GERONIMO-1349) Missing Ports in Startup Port List
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=all ]
Aaron Mulder updated GERONIMO-1349:
-----------------------------------
Component: CORBA
> Missing Ports in Startup Port List
> ----------------------------------
>
> Key: GERONIMO-1349
> URL: http://issues.apache.org/jira/browse/GERONIMO-1349
> Project: Geronimo
> Type: Bug
> Components: CORBA, 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
[jira] Commented: (GERONIMO-1349) Missing Ports in Startup Port
List
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=comments#action_12365990 ]
Aaron Mulder commented on GERONIMO-1349:
----------------------------------------
With the previous patch committed and an adjustment to OpenEJB to show the ORB TSS listen port, there is only one port left, which is the CORBA root POA. The last line of our code that executes is the OpenEJBPOA constructor -- it calls super and super listens on a random port. It would be nice to figure out a way to pass a port into that.
However, that would still leave the problem that one GBean (the CORBABean) effectively wraps both the ORB and POA, and our port list currently can't handle a single GBean listening on multiple ports. It would be nice if OpenEJBORB and OpenEJBPOA were GBeans such that they could each provide a manageable port number. Perhaps the TSS configuration should be a GBean, as it's what has the actual SSL listen port configured on it.
Also, if a secondary TSS is defined to listen on a different port and then associated with a live EJB, that probably would not be caught at present.
> Missing Ports in Startup Port List
> ----------------------------------
>
> Key: GERONIMO-1349
> URL: http://issues.apache.org/jira/browse/GERONIMO-1349
> Project: Geronimo
> Type: Bug
> Components: CORBA, 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
[jira] Updated: (GERONIMO-1349) Missing Ports in Startup Port List
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Commented: (GERONIMO-1349) Missing Ports in Startup Port
List
Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=comments#action_12362601 ]
John Sisson commented on GERONIMO-1349:
---------------------------------------
I think this is the code that is causing us to listen on another port..
Thread [main] (Suspended)
java.net.ServerSocket.bind(java.net.SocketAddress, int) line: 316
java.net.ServerSocket.<init>(int, int, java.net.InetAddress) line: 185
java.net.ServerSocket.<init>(int) line: 97
sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(int) line: 27
sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(int) line: 333
sun.rmi.transport.tcp.TCPEndpoint.newServerSocket() line: 615
sun.rmi.transport.tcp.TCPTransport.listen() line: 231
sun.rmi.transport.tcp.TCPTransport.exportObject(sun.rmi.transport.Target) line: 178
sun.rmi.transport.tcp.TCPEndpoint.exportObject(sun.rmi.transport.Target) line: 382
sun.rmi.transport.LiveRef.exportObject(sun.rmi.transport.Target) line: 116
sun.rmi.server.UnicastServerRef2(sun.rmi.server.UnicastServerRef).exportObject(java.rmi.Remote, java.lang.Object, boolean) line: 145
sun.rmi.server.UnicastServerRef2(sun.rmi.server.UnicastServerRef).exportObject(java.rmi.Remote, java.lang.Object) line: 129
java.rmi.server.UnicastRemoteObject.exportObject(java.rmi.Remote, java.lang.String, java.lang.Class[], java.lang.Object[]) line: 275
java.rmi.server.UnicastRemoteObject.exportObject(java.rmi.Remote, int, java.rmi.server.RMIClientSocketFactory, java.rmi.server.RMIServerSocketFactory) line: 206
javax.management.remote.rmi.RMIJRMPServerImpl.export() line: 39
javax.management.remote.rmi.RMIConnectorServer.start() line: 149
org.apache.geronimo.jmxremoting.JMXConnector.doStart() line: 122
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance() line: 936
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart() line: 325
> 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
>
> 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
[jira] Commented: (GERONIMO-1349) Missing Ports in Startup Port
List
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=comments#action_12362639 ]
Aaron Mulder commented on GERONIMO-1349:
----------------------------------------
Are we saying that the JMX connector is listening on an arbitrary port? That would be really bad, as it sounds like it would mean you can't configure a firewall to allow remote management!
> 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
>
> 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
[jira] Commented: (GERONIMO-1349) Missing Ports in Startup Port
List
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=comments#action_12365918 ]
Aaron Mulder commented on GERONIMO-1349:
----------------------------------------
A recent Geronimo/netstat run with at least one CORBA EJB enabled indicates that we don't show the CORBA TSS SSL listen port, and there were two unknown ports in the list. If one was JMX, I'm still not sure about the other.
> 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
[jira] Updated: (GERONIMO-1349) Missing Ports in Startup Port List
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1349?page=all ]
Aaron Mulder updated GERONIMO-1349:
-----------------------------------
Fix Version: 1.1
(was: 1.0)
Priority: Major (was: Blocker)
Fixed the directory port. Not sure where the other random port is coming from, but it's probably less critical.
> 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
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Fix For: 1.1
>
> 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