| Remote Repository Downloads on Port 8080 Regardless of Config [message #661491] |
Thu, 24 March 2011 18:29  |
Eclipse User |
|
|
|
I am running a Virgo hosted repository and it is listening on port 8080, the Virgo default configuration. I'm using a firewall on that server to redirect port 80 traffic to port 8080; Port 8080 traffic is generally disabled on our network, so this allows other Virgo instances on the network to have remote repositories connecting on port 80 to my hosted repository server.
Here is an example org.eclipse.virgo.repository.properties config file of a Virgo instance pointed at the remote repository:
ext.type=external
ext.searchPattern=repository/ext/{artifact}
usr.type=watched
usr.watchDirectory=repository/usr
iris-test.type=remote
iris-test.uri=http://stormlog.wrh.noaa.gov:80/org.eclipse.virgo.apps.repository/iris-test
iris-test.indexRefreshInterval=30
chain=ext,usr,iris-test
Note that it is using port 80 (I have also omitted the port specification as well assuming it would default to port 80).
When a Virgo instance out on the network polls the remote repository every 30 seconds, the polling happens over port 80 and seems to work as expected.
When a Virgo instance actually attempts to download artifacts from the remote repository, it does that over port 8080 despite my port 80 configuration. This causes the artifact download to fail because 8080 traffic is not allowed on my network.
I have verified this behavior using tpcdump.
Maybe a bug? Port 8080 hard coded somewhere in Virgo?
Thanks,
Aaron
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04378 seconds
Home