Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Unable to read repository
Unable to read repository [message #1816722] Tue, 05 November 2019 15:36 Go to next message
Tom Edwards is currently offline Tom EdwardsFriend
Messages: 5
Registered: November 2019
Junior Member
Fresh install of Eclipse IDE Version: Photon Release (4.8.0)
Build id: 20180619-1200

Unable to read repository error encountered while trying to download plugin or check for updates from the following repositories

www.flowable.org/designer/update
dowload.eclipse.org/releases/latest
download.eclipse.org/releases/photon
download.eclipse.org/eclipse/updates/4.8

Windows 7 running Java version 8 update 191
Re: Unable to read repository [message #1816735 is a reply to message #1816722] Wed, 06 November 2019 05:48 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 30635
Registered: July 2009
Senior Member
Does it tell you which specific one doesn't load? Sometimes networks and servers have transient problems...
Re: Unable to read repository [message #1816812 is a reply to message #1816735] Thu, 07 November 2019 14:04 Go to previous messageGo to next message
Tom Edwards is currently offline Tom EdwardsFriend
Messages: 5
Registered: November 2019
Junior Member
It returns the unable to read repository error for all of them.

I have tried several times on different networks and its always the same
Re: Unable to read repository [message #1816842 is a reply to message #1816812] Fri, 08 November 2019 06:36 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 30635
Registered: July 2009
Senior Member
Perhaps your firewall has blocked the Eclipse application from accessing the internet?
Re: Unable to read repository [message #1816843 is a reply to message #1816842] Fri, 08 November 2019 08:35 Go to previous messageGo to next message
Tom Edwards is currently offline Tom EdwardsFriend
Messages: 5
Registered: November 2019
Junior Member
I have been told this is not the case and the internal browser in eclipse can access them.

Could it be the version of Java?

Re: Unable to read repository [message #1816847 is a reply to message #1816843] Fri, 08 November 2019 09:18 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 30635
Registered: July 2009
Senior Member
No, it seems unlikely to be the Java version. But it is possible that if you use https URs that the Java version might not have the root certificates needed to validate the secure connection.

There's nothing in the Error Log view that might provide clues? (Or in <workspace>/.metadata/.log).
Re: Unable to read repository [message #1816973 is a reply to message #1816847] Wed, 13 November 2019 08:42 Go to previous messageGo to next message
Tom Edwards is currently offline Tom EdwardsFriend
Messages: 5
Registered: November 2019
Junior Member
This is the log entry

!ENTRY org.eclipse.equinox.p2.core 4 0 2019-11-13 08:39:47.425
!MESSAGE Provisioning exception
!STACK 1
org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://www.flowable.org/designer/update.
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:127)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:77)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryLoad(ArtifactRepositoryManager.java:78)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:767)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:409)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:201)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Artifact.loadRepository(CachingRepositoryManager.java:543)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.basicRefreshRepository(AbstractRepositoryManager.java:203)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.refreshRepository(ArtifactRepositoryManager.java:121)
at org.eclipse.equinox.p2.ui.RepositoryManipulationPage.lambda$16(RepositoryManipulationPage.java:584)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Caused by: java.io.IOException: Invalid repository location: http://www.flowable.org/designer/update.
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:103)
... 14 more
!SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 1002 2019-11-13 08:39:47.425
!MESSAGE Unable to read repository at http://www.flowable.org/designer/update.
!STACK 0
java.io.IOException: Invalid repository location: http://www.flowable.org/designer/update.
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:103)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.load(SimpleArtifactRepositoryFactory.java:77)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryLoad(ArtifactRepositoryManager.java:78)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:767)
at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:117)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:409)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:201)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Artifact.loadRepository(CachingRepositoryManager.java:543)
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.basicRefreshRepository(AbstractRepositoryManager.java:203)
at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.refreshRepository(ArtifactRepositoryManager.java:121)
at org.eclipse.equinox.p2.ui.RepositoryManipulationPage.lambda$16(RepositoryManipulationPage.java:584)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Re: Unable to read repository [message #1816974 is a reply to message #1816973] Wed, 13 November 2019 08:49 Go to previous messageGo to next message
Tom Edwards is currently offline Tom EdwardsFriend
Messages: 5
Registered: November 2019
Junior Member
Also logs say that System property http.proxyPort is not set as well as http.proxyHost, but i have completed the Proxy settings in the Network connections window in preferences
Re: Unable to read repository [message #1816993 is a reply to message #1816974] Wed, 13 November 2019 13:51 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30635
Registered: July 2009
Senior Member
I see such warnings from low-level libraries, but still everything works.

The particular stack suggests the problem at line 103 is currently at this line:

https://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclipse.equinox.p2.artifact.repository/src/org/eclipse/equinox/internal/p2/artifact/repository/simple/SimpleArtifactRepositoryFactory.java#n106

That suggests that the content.jar was downloaded but the contents could not be processed. This all works for me and the specific file https://www.flowable.org/designer/update/content.jar does exist and looks correct to me.

It all smells to me like something a virus scanner or firewall jar scanner would cause.

You could also have a look in your <home>/.eclipse/org.eclipse.oomph.p2/cache to see what if anything has made from the internet to your machine. You can delete this cache folder to see just is freshly and recently used files. The file names in the cache folder are mangled versions of the URL from which the file came. Are empty jars showing up here? Do _p2.index files appear? Do any files beyond just those appear?
Previous Topic:how to merge two rown in BIRT
Next Topic:Tycho build fails
Goto Forum:
  


Current Time: Fri Nov 15 15:15:33 GMT 2019

Powered by FUDForum. Page generated in 0.03263 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top