Re: [virgo-dev] Configuring some of the ports opened by Virgo

[Glyn Normington <gnormington@xxxxxxxxxx>]

Thanks.

Regards,
Glyn

On 17 Feb 2011, at 08:36, Violeta Georgieva wrote:

Hi,

 

This is also useful when Virgo is behind a firewall.

I will create an enhancement.

 

Regards

Violeta

2011/2/10 Glyn Normington <gnormington@xxxxxxxxxx>

That function seems desirable to me. Users with very many ports in use who start Virgo relatively early may find that Virgo consumes a port that some other program started later is hard-coded to use, causing the later program to fail.

OTOH I am not aware of users actually hitting this problem, so I wouldn't put it ahead of more useful features (like Tomcat 7, for instance).

Regards,
Glyn

On 10 Feb 2011, at 15:10, Violeta Georgieva wrote:

Hi,

 

I want to start the discussion about configuring some of the ports opened by Virgo.

 

When I start/stop Virgo several times I observe the following:

 

N:\>netstat -a -o -n |findstr 4452

  TCP    0.0.0.0:4971           0.0.0.0:0              LISTENING       4452

  TCP    0.0.0.0:4972           0.0.0.0:0              LISTENING       4452

  TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING       4452

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING       4452

  TCP    0.0.0.0:8443           0.0.0.0:0              LISTENING       4452

  TCP    0.0.0.0:9875           0.0.0.0:0              LISTENING       4452

 

N:\>netstat -a -o -n |findstr 1092

  TCP    0.0.0.0:4992           0.0.0.0:0              LISTENING       1092

  TCP    0.0.0.0:4993           0.0.0.0:0              LISTENING       1092

  TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING       1092

  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING       1092

  TCP    0.0.0.0:8443           0.0.0.0:0              LISTENING       1092

  TCP    0.0.0.0:9875           0.0.0.0:0              LISTENING       1092

 

The 8009, 8080 and 8443 ports are Tomcat’s Connectors ports. They can be configured in the tomcat-server.xml.

 

The 9875 port is the JMX port and it can be configured through –jmxport.

 

What about the ports 4971&4972 (4992&4993 from the second run)?

What I found is that these are the RMI ports used for JMX Remote connections. And they are randomly chosen every time the JVM starts. There is Tomcat documentation for what have to be done in order to explicitly specify them to be one and the same every time. http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html (JMX Remote Lifecycle Listener).

 

What do you think about introducing this functionality in Virgo?

We need to bundlize the catalina-jmx-remote.jar and to add a listener in the tomcat-server.xml

 

Thanks

Regards

Violeta

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev

_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev