Eclipse Community Forums: Virgo » Hosted repository with virgo tomcat server 3.0.2

Re: Hosted repository with virgo tomcat server 3.0.2 [message #780350 is a reply to message #780328]

Tue, 17 January 2012 16:47

Messages: 1222
Registered: July 2009

Senior Member

Adding a repository to the chain of the Virgo instance which is acting as a repository server does not make that repository externally visible as a URL. The contents of the added repository will be available via the normal remote repository URL.

So I'd be very surprised if you ever saw the 2.1.1 behaviour you describe. Perhaps it is worth checking the rest of your 2.1.1 configuration to make sure somebody didn't sneak in some extra configuration that you are not aware of.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #780418 is a reply to message #780350]

Tue, 17 January 2012 19:45

jc perron

Messages: 4
Registered: January 2012

Junior Member

Maybe that's the case, I will start with a fresh virgo 2.1.1 just to be sure.

With virgo 2.1.1 accessing the adress start the download of an xml file. With virgo 3.0.2 I get a 404 error with the browser and there is the same 404 error in the log file of the remote repository, so I guess the problem is with my hosted repository.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #780821 is a reply to message #780418]

Thu, 19 January 2012 14:09

jc perron

Messages: 4
Registered: January 2012

Junior Member

I made some tests starting with fresh download of virgo 2.1.1. and virgo 3.0.2. With virgo 2.1.1, no problem the hosted repository work fine and is accessible just by adding some bundles in the folder repository/hosted. With virgo 3.0.2 I am still getting a 404 error... For now I will go in production with virgo 2.1.1 as the hosted repo and will investigate further my problem with virgo 3.0.2 in the next month.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #780828 is a reply to message #780821]

Thu, 19 January 2012 14:30

Messages: 1222
Registered: July 2009

Senior Member

Ok. Meanwhile, please could you confirm that the URL

myserver:8080/org.eclipse.virgo.apps.repository/hosted-maven

is not giving a 404 with Virgo 2.1.1 as that would be most surprising unless you have configured hosted-maven to be a remote repository?

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782793 is a reply to message #780828]

Tue, 24 January 2012 13:15

Messages: 14
Registered: January 2012

Junior Member

I confirm that hosted repository does not work with Virgo 3.0.2. It sends 404 error.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782809 is a reply to message #782793]

Tue, 24 January 2012 13:55

Messages: 1222
Registered: July 2009

Senior Member

Please could you say what URL is giving the 404?

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782813 is a reply to message #782809]

Tue, 24 January 2012 14:05

Messages: 14
Registered: January 2012

Junior Member

Glyn Normington wrote on Tue, 24 January 2012 08:55

Please could you say what URL is giving the 404?

Please find the URL in the next message.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782814 is a reply to message #782813]

Tue, 24 January 2012 14:06

Messages: 14
Registered: January 2012

Junior Member

Anton Kolmakov wrote on Tue, 24 January 2012 09:05

Glyn Normington wrote on Tue, 24 January 2012 08:55
Please could you say what URL is giving the 404?

Please find the URL in the next message.

URL http://${server}:${port}/org.eclipse.virgo.apps.repository/${name of any repository defined in org.eclipse.virgo.apps.repository.properties} gives the 404 error.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782823 is a reply to message #782814]

Tue, 24 January 2012 14:22

Messages: 1222
Registered: July 2009

Senior Member

Thanks Anton. That behaviour is consistent with the behaviour reported by jc perron above. But I'm not convinced that this should ever have worked as adding a repository to the chain of the Virgo instance which is acting as a repository server does not make that repository externally visible as a URL. I asked jc perron whether this used to work on 2.1.1, which would be most surprising, but I am still waiting for a response. Do you have an answer to that?

Anyway, a 404 of that URL is no indication of a problem. You should still be able to configure another Virgo instance to use a remote repository by following the information in the User Guide.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #782879 is a reply to message #782823]

Tue, 24 January 2012 16:30

Messages: 14
Registered: January 2012

Junior Member

I had downloaded Virgo 2.1.1 and added new hosted repository to org.eclipse.virgo.apps.repository.properties file:

hosted.type=watched
hosted.watchDirectory=repository/hosted

After that I have started the server and performed a simple test that sends HTTP GET request with URI "http://localhost:9080/org.eclipse.virgo.apps.repository/hosted":

0:0:0:0:0:0:0:1 - - [24/Jan/2012:18:08:48 +0200] "GET /org.eclipse.virgo.apps.repository/hosted HTTP/1.1" 200 101

The server successfully processed the request and returned some XML response.

Virgo 3.0.2 does not pass the test:

0:0:0:0:0:0:0:1 - - [24/Jan/2012:18:09:36 +0200] "GET /org.eclipse.virgo.apps.repository/hosted HTTP/1.1" 404 952

And when another server tries to access a remote repository hosted on Virgo 3.0.2, it fails because of the 404 error. With 2.1.1 version of Virgo everything works.

[Updated on: Tue, 24 January 2012 16:32]

Re: Hosted repository with virgo tomcat server 3.0.2 [message #816684 is a reply to message #782879]

Fri, 09 March 2012 06:18

Will Yao

Messages: 11
Registered: July 2010

Junior Member

hi:

You should put the org.eclipse.virgo.apps.repository.properties into the org.eclipse.virgo.apps.repository_3.0.2.par file, and it should work.

Re: Hosted repository with virgo tomcat server 3.0.2 [message #816773 is a reply to message #816684]

Fri, 09 March 2012 08:42

Messages: 1222
Registered: July 2009

Senior Member

I think the bottom line here is that if hosted repositories are not working properly, a bug should be raised with details of how to reproduce the problem so a fix can be investigated. I'm afraid the invalid URLs posted early in the thread have been a bit of a distraction from the real issue.