Community
Participate
Working Groups
Build Identifier: Virgo 2.1.1 Release When the Virgo server is hosting a repository and the other Virgo instance is using that repository as remote repository. When we add some artifacts in the Server repository those artifacts are not available to the remote repository until we restart the Server Instance. So every time we add artifact we have to restart the server. It should be like that whenever we add artifact in hosted repository it should be available to the remote sites who are using the hosted repository. Reproducible: Always Steps to Reproduce: 1. Start One Virgo instance (Server) and host a repository from this instance 2. Start another Virgo (Client) instance on other machine and add the hosted repository as remote repository in this instance. 3. Deploy some test artifact in the hosted repository 4. Make a plan file and mention that artifact in that file. 5. Deploy the plan file in the pickup directory of the Client Virgo Instance. 6. The artifact does not available in the Client OSGi environment. But it should be.
Did you use a watched repository in the repository host? You should also check the refresh interval of the repository client.
I tried with both external and watched repostiory with the refresh interval of 30 seconds in the host system and in the repository client the resfresh interval was 30 seconds.
Ok, then this is strange as the function has worked on other occasions. An external repository won't help as it is only refreshed on repository server startup, but a watched repository should give the desired behaviour. Have you tried allowing, say, 2 minutes between adding the bundle and deploying the plan to ensure that both intervals have had a chance to expire in sequence?
When I use the repostiory as external then the repository is available but when we try using watched repository then the repository is not available and when we try to access the hosted repository from URL "http://localhost:8080/org.eclipse.virgo.apps.repository/hosted-repo" it gives "HTTP Status 404"
Hmmm. It certainly seems likely you have a configuration error somewhere. Have you double/triple checked that you have correctly followed the instructions in the User Guide? To be clear, your repository server Virgo instance should use a watched repository to store the artifacts that need to be available remotely. If you still can't find the problem, please attach all the relevant configuration files to this bug so we can take a look.
Created attachment 199728 [details] Virgo server Hosted Repostiory configuration This is the configuration file available on the Virgo Server Instance.
Created attachment 199729 [details] Virgo client reomote repostiory configuration This file is available at the Virgo Client Instance for lookup in the remote repository.
Please see the attched configuration files and let me know if I am missing something or any thing else need to add. The server donot host the repository with this configuration.But when I use hosted-repo as external in the server reposotory configuration the hosted-repo becomes available.
The hosted repository configuration is incorrect: hosted-repo.type=watched hosted-repo.searchPattern=repository/hosted/* hosted-repo.watchedInterval=10 For a watched repository, you must specify repository-name.watchDirectory. searchPattern is only applicable for an external repository. This is described in Table 11.8 in the User Guide: http://www.eclipse.org/virgo/documentation/virgo-documentation-3.0.0.x/docs/virgo-user-guide/htmlsingle/virgo-user-guide.html#configuring-hosted-repo.
