Virgo Tomcat Server 3.5.0 repository host returns 404 [message #930770] |
Tue, 02 October 2012 16:23 |
Kevin Beasley Messages: 4 Registered: October 2012 |
Junior Member |
|
|
Right off, let me say that I _know_ that this is supposed to work. I have gone through the user documentation many times trying to see where the issue is. I have searched this forum and read every post about repositories that I can find.
There is obviously something that I am missing, but I just cannot see it. Please help!
Steps to recreate:
1. Fresh install VTS 3.5.0 on linux machine.
2. edit configuration/org.eclipse.virgo.apps.repository.properties to contain the following 2 lines:
hosted-repository.type=external
hosted-repository.searchPattern=/home/devtools/hosted-virgo-repository/*
3. Create directory /home/devtools/hosted-virgo-repository
4. Copy a bundle to /home/devtools/hosted-virgo-repository. This bundle, if found by a VTS client, will fulfill a dependency requirement for a bundle that will be deployed on the client.
5. Start the VTS server on the linux machine. No errors in the logs, everything looks green from here.
6. Fresh install of VTS 3.5.0 on Windows 7 machine. This is the repository client.
7. edit configuration/org.eclipse.virgo.repository.properties. Add a remote repository pointing to the VTS repo server, and up date the chain to reference it. The actual hostname of the repo server resolves via DNS.
hosted-repo.type=remote
hosted-repo.uri=http://repohost:8080/org.eclipse.virgo.apps.repository/hosted-repository
chain=ext,usr,hosted-repo
8. Start the VTS on the Windows 7 machine.
9. The client sends a request to the repo server, gets a 404 back.
10. Fail.
If there is any information I can provide, please let me know.
Regards,
Kevin
|
|
|
Re: Virgo Tomcat Server 3.5.0 repository host returns 404 [message #931523 is a reply to message #930770] |
Wed, 03 October 2012 09:33 |
Glyn Normington Messages: 1222 Registered: July 2009 |
Senior Member |
|
|
Hi Kevin
Because you've clearly done your best to get this working, I was intrigued and tried to set it up myself. It's a while since I tested remote repository function and, unfortunately, it's one of the areas where we don't have an automated regression test of the end to end function.
So far, I have similarly failed to get it working on VTS 3.5.0 or VTS 3.0.3. Unless I'm making a stupid mistake, I think you've found a bug - feel free to raise a bugzilla if I haven't already done so (and posted to this thread) by the time you read this.
Meanwhile, I'm going back to VTS 2.1.x to see when it last worked the way I expect it to.
Regards,
Glyn
[Updated on: Wed, 03 October 2012 10:10] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: Virgo Tomcat Server 3.5.0 repository host returns 404 [message #931839 is a reply to message #931729] |
Wed, 03 October 2012 15:19 |
Kevin Beasley Messages: 4 Registered: October 2012 |
Junior Member |
|
|
Glyn,
Thanks so much for looking into this and tracking down the issue so quickly! Your solution works as advertised. The VTS repository host now responds correctly when the client connects and requests the repository information.
However, there seems to be another problem.
The VTS repository host has a bundle, "Bundle2", in the location that it is serving from. When the client makes the request to get the index from the VTS host, the index lists Bundle2 correctly. I have a second bundle, "Bundle1", which has a dependency on Bundle2. When I deploy Bundle1 into the pickup directory on the VTS client, the installation of Bundle1 fails with an o.e.v.k.o.framework.UnableToSatisfyBundleDependenciesException. The exception indicates "Unsatisfied leaf constraint on Bundle2".
The thing that I don't see when I try to deploy Bundle1 is a request from the VTS client for the contents of Bundle2 from the VTS host. In fact, I never see that request happen. I am watching the connection with tcpdump, fwiw.
What I do see is an UnknownHostException being thrown when the client attempts to download Bundle2 from the repository host. The hostname that it attempts to contact is localhost.localdomain, which is clearly wrong since the VTS host is running on a machine with a FQDN. This exception does not show up on the console, but it does get written to serviceability/logs/log.log
The only reference I can find to localhost.localdomain is in a file in work/ that looks like the contents of the repository server response when the client polls for the index.
Looking at the work/cache directory on the VTS client, I can see that the folder structure for Bundle2 has been created, but none of the bundle contents are there. The folder structure gets created when I attempt to deploy Bundle1 on the client.
Sorry for the over long and rambling post. I try to be as thorough as I can. Please let me know if there is any other information I can gather for you.
Regards,
Kevin
|
|
|
|
Powered by
FUDForum. Page generated in 0.05313 seconds