Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor
Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745411] Mon, 10 October 2016 13:19 Go to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
Hello,

I'm finding https://github.com/vorburger/opendaylight-eclipse-setup is either completely broken or got REALLY SLOW - it seems to remain "stuck" at some point in the P2 Director task, and a jstack shows it spending A LOT of time around the org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor class - some snapshots shown below. (Should be reproducible by provisioning a workspace for any of the OpenDaylight projects in the catalogue.)

Tried it several times, attempted to run with Bundle Pool switched off at the first step of the wizard, repair (nothing) and clean up the bundle pool, finally wiping ~/.p2, but no good, currently can't install anymore ..

This is with Oomph 1.5.0 Build 2617, but the problem of course could be elsewhere - in p2 code, or even in one of the external p2 sites we pull... perhaps something wrong with a signature somewhere, but which?

Last line printed in Oomph wizard UI console view after, after a full wipe of ~/.p2 (although stuck at different places earlier), is:

Downloading org.bouncycastle.bcprov
Fetching org.bouncycastle.bcprov_1.52.0.v20160915-1535.jar from http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/

This stay stuck there for over 20 min, with very high (100%) x2 CPU usage - clearly something gone wrong, IMHO.

Have any of you other Oomph users seen something like this in your own projects? Any suggestions for how to resolve, or further debug (my understanding of the inner works of p2 is VERY limited .. which other Forum / Bugzilla product would even be appropriate for org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor related issues? Equinox/p2?), or work around this?

Thanks,
M.

"Worker-31" #73 prio=5 os_prio=0 tid=0x00007f379800a800 nid=0x3a91 sleeping[0x00007f375275d000]
java.lang.Thread.State: RUNNABLE
at java.lang.String.indexOf(String.java:1769)
at java.lang.String.indexOf(String.java:1735)
at java.lang.AbstractStringBuilder.indexOf(AbstractStringBuilder.java:1348)
at java.lang.StringBuffer.indexOf(StringBuffer.java:636)
- eliminated <owner is scalar replaced> (a java.lang.StringBuffer) at java.lang.AbstractStringBuilder.indexOf(AbstractStringBuilder.java:1329)
at java.lang.StringBuffer.indexOf(StringBuffer.java:628)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.removeAll(SignatureBlockProcessor.java:463)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.stripContinuations(SignatureBlockProcessor.java:458)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.populateMDResults(SignatureBlockProcessor.java:189)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:112)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:61)
at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.initializeSignedContent(SignedBundleFile.java:44)
at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:215)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verifyContent(SignatureVerifier.java:79)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verify(SignatureVerifier.java:61)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.close(SignatureVerifier.java:108)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.reportStatus(SimpleArtifactRepository.java:1183)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:592)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:319)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:288)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:223)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

"Worker-31" #73 prio=5 os_prio=0 tid=0x00007f379800a800 nid=0x3a91 sleeping[0x00007f375275d000]
java.lang.Thread.State: RUNNABLE
at java.lang.String.equalsIgnoreCase(String.java:1109)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.getDigestAlgorithmFromString(SignatureBlockProcessor.java:273)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.populateMDResults(SignatureBlockProcessor.java:201)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:112)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:61)
at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.initializeSignedContent(SignedBundleFile.java:44)
at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:215)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verifyContent(SignatureVerifier.java:79)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verify(SignatureVerifier.java:61)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.close(SignatureVerifier.java:108)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.reportStatus(SimpleArtifactRepository.java:1183)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:592)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:319)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:288)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:223)
at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:153)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

"Worker-31" #73 prio=5 os_prio=0 tid=0x00007f379800a800 nid=0x3a91 sleeping[0x00007f375275d000]
java.lang.Thread.State: RUNNABLE
at java.lang.String.indexOf(String.java:1769)
at java.lang.String.indexOf(String.java:1735)
at java.lang.AbstractStringBuilder.indexOf(AbstractStringBuilder.java:1348)
at java.lang.StringBuffer.indexOf(StringBuffer.java:636)
- eliminated <owner is scalar replaced> (a java.lang.StringBuffer) at java.lang.AbstractStringBuilder.indexOf(AbstractStringBuilder.java:1329)
at java.lang.StringBuffer.indexOf(StringBuffer.java:628)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.removeAll(SignatureBlockProcessor.java:463)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.stripContinuations(SignatureBlockProcessor.java:458)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.populateMDResults(SignatureBlockProcessor.java:189)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.processSigner(SignatureBlockProcessor.java:112)
at org.eclipse.osgi.internal.signedcontent.SignatureBlockProcessor.process(SignatureBlockProcessor.java:61)
at org.eclipse.osgi.internal.signedcontent.SignedBundleFile.initializeSignedContent(SignedBundleFile.java:44)
at org.eclipse.osgi.internal.signedcontent.SignedBundleHook.getSignedContent(SignedBundleHook.java:215)
at org.eclipse.equinox.internal.p2.artifact.repository.SignatureVerifier.verifyContent(SignatureVerifier.java:79)

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745422 is a reply to message #1745411] Mon, 10 October 2016 14:29 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
No, I've not seen such a problem, but if you tell me exact steps to try to reproduce it, then I could perhaps find time to find out what's going on. If p2 has a problem processing some artifact, it will often download it again, and try again, and do that 200 times before failing. That clearly can take very very long.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745427 is a reply to message #1745422] Mon, 10 October 2016 14:53 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
> if you tell me exact steps to try to reproduce it
> then I could perhaps find time to find out what's going on

You are very kind!! If you do have the time, here is what you would have to do:

Similarly to the steps described on https://github.com/vorburger/opendaylight-eclipse-setup, basically:

1. Eclipse Installer
2. Advanced mode
3. Product: Eclipse IDE for Java Developers
4. Projects page, collapse the Eclipse Projects & GitHub Projects to scroll down to the OpenDaylight.org Projects (or use the "Select Catalogs" icon in the upper right hand corner for permanent filtering)
5. Click any of the many ODL projects listed, for example "netvirt" (it shouldn't matter, because this problem here happens long before projects get cloned etc. anyway)
6. Variables, the usual
7. Finish

I just hope that it "doesn't go away by itself" by when you try - I suspect this could have something to do with one of the (many) p2 sites from which this set up model pulls.. any their content changes frequently.

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745548 is a reply to message #1745427] Wed, 12 October 2016 11:31 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
Sorry, I've not found time yet to investigate. Too many good intentions and not enough time. One thing I want to double check first is to be sure you're not running with Java 1.7 as your JRE and perhaps are installing things that were pack200'd with Java 1.8. I know that causes this kind of looping. In any case, I'll try to find time...

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745582 is a reply to message #1745548] Wed, 12 October 2016 17:14 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
> One thing I want to double check first is to be sure you're not running with Java 1.7 as your JRE and perhaps are installing things that were pack200'd with Java 1.8. I know that causes this kind of looping

Confirming this - I'm running on Java 8 only.

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745604 is a reply to message #1745411] Thu, 13 October 2016 07:37 Go to previous messageGo to next message
Missing name Mising name is currently offline Missing name Mising nameFriend
Messages: 3
Registered: October 2016
Junior Member
Hi guys,

Me and my colleague are also stuck at the same installation step in Oomph:

Downloading org.bouncycastle.bcprov
Fetching org.bouncycastle.bcprov_1.52.0.v20160915-1535.jar from http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/

Is there any work around ???

Thanks,
Aziz

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745637 is a reply to message #1745548] Thu, 13 October 2016 16:40 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
> Me and my colleague are also stuck at the same installation step in Oomph:

Aziz, are you stuck with this in https://github.com/vorburger/opendaylight-eclipse-setup, or with another completely different Oomph model which happens to also use http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/ ?

If it's the former, then I can help you and could try, as a temporary workaround, to just disable (or make it an option during the installation) the particular Eclipse plugin which pulls this apparently troublesome bundle from the opendaylight.setup. It's actually isn't critical at all and totally just nice to have one, in this setup.

If it's the latter, then you being the 2nd person hitting this independently with this particular JAR makes me think that this is perhaps something for you to pick up with the linuxtools project - perhaps they simple have some sort.. bug, which makes p2 choke, where they publish this particular bundle?

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745699 is a reply to message #1745637] Fri, 14 October 2016 17:05 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
I get a failure much sooner from using https://otto.takari.io/content/sites/m2e.extras/m2eclipse-buildhelper/0.15.0/N/0.15.0.201405280027/ so I'm not able to test this scenario.

ERROR: org.eclipse.equinox.p2.transport.ecf code=1002 Unable to read repository at https://otto.takari.io/content/sites/m2e.extras/m2eclipse-buildhelper/0.15.0/N/0.15.0.201405280027/content.xml.
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
  at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
  at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
  at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
  at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
  at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
  at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
  at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
  at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
  at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.SNIAwareHttpClient$1.connectSocket(SNIAwareHttpClient.java:63)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
  at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
  at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
  at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
  at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
  at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
  at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
  at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
  at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
  at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:249)
  at sun.security.validator.Validator.validate(Validator.java:260)
  at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
  at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
  at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
  at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
  at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
  at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
  at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
  at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.SNIAwareHttpClient$1.connectSocket(SNIAwareHttpClient.java:63)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
  at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
  at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
  at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
  at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
  at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
  at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
  at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
  ... 1 more
Caused by: java.security.cert.CertPathValidatorException: timestamp check failed
  at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
  at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
  at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
  at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
  at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
  at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
  at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:249)
  at sun.security.validator.Validator.validate(Validator.java:260)
  at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
  at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
  at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
  at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
  at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
  at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
  at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
  at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.SNIAwareHttpClient$1.connectSocket(SNIAwareHttpClient.java:63)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
  at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
  at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
  at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
  at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
  at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
  at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:263)
  ... 2 more
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Fri Oct 14 01:59:59 CEST 2016
  at sun.security.x509.CertificateValidity.valid(CertificateValidity.java:274)
  at sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:629)
  at sun.security.provider.certpath.BasicChecker.verifyTimestamp(BasicChecker.java:190)
  at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144)
  at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
  at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
  at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
  at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
  at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
  at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
  at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:249)
  at sun.security.validator.Validator.validate(Validator.java:260)
  at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
  at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
  at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
  at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
  at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
  at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
  at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
  at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
  at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
  at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:535)
  at org.eclipse.ecf.provider.filetransfer.httpclient4.SNIAwareHttpClient$1.connectSocket(SNIAwareHttpClient.java:63)
  at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
  at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
  at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
  at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
  at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
  at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
  at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
  ... 3 more


Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745774 is a reply to message #1745699] Mon, 17 October 2016 12:27 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
Ed, thanks again for your willingness to investigate this further! FYI the SSL problem above from https://otto.takari.io was another issue, completely unrelated to the main p2 one, and seems to have gotten fixed; I just rechecked, and we find that the expired cert on otto.takari.io has just been replaced by a new one which now "Begins on: Saturday 15 October 2016 & Expires on: Wednesday 16 October 2019" - so the problem above won't happen anymore (thanks... Jason van Zyl, I suppose).

If you're willing to retry now re. the original issue, that could be valuable (I suspect you would find either some general problem in p2, or something particular wrong on http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/.

FYI I've just done a simple standalone test - I've wiped (backed up) ~/.p2, installed a completely fresh new Eclipse IDE for Java Developers (Neon), and "manually" (without Oomph, just good ol' Help > Install New Software..) added both that Docker and Vagrant Tooling from Linux Tools on http://download.eclipse.org/linuxtools/updates-docker-nightly/ - and that WORKS, I can't replicate it that way. However if I retry an opendaylight-eclipse-setup now, then I still see the same problem initially reported above - same jstack thread dump stack trace, and console mentions "Downloading org.bouncycastle.bcprov" & "Downloading org.bouncycastle.bcpkix" which I have a "hunch" this could be related to. Don't know if that is because in opendaylight-eclipse-setup there are other p2 sites in the picture, or because there is another version of "p2" (?) that runs from Oomph than Eclipse Neon IDE?

BTW: This signature verification security stuff MAY BE related to more than just Java 8 vs Java 7 (above) - I'm seeing this problem on OpenJDK on Fedora - I could theoretically imagine that this kind of (security) stuff behaves differently on other platforms...

As a short term work around this problem, which other users have now raised via email, I'm going to attempt making installation of additional Eclipse plugins optional in this particular setup model.

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745788 is a reply to message #1745774] Mon, 17 October 2016 14:36 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
It worked on Windows, so likely is problem specific to Linux. I'll have to find time to test there too then, but I do know that Linux is more fussy about certificates and refuses to accept some that are find on other platforms.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745794 is a reply to message #1745774] Mon, 17 October 2016 14:51 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
> because there is another version of "p2" (?) that runs from Oomph than Eclipse Neon IDE?

I'm now reasonably certain that this is the root cause! Here's why:

> going to attempt making installation of additional Eclipse plugins optional

Exploring this, see parallel forum thread Project with only P2 Director but no Git Clone nor Stream, led to a partially working situation where I more by coincidence managed to get the stuff from http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/ not initially installed by Oomph, but then later by the Eclipse IDE (by "accident"; see the other thread for more about that). Curiously, that worked just fine, without that looping around (not deadlock) in SignatureBlockProcessor - as already found in the standalone non-Oomph installation attempt documented above.

So I had a closer look at version, and found that indeed Oomph Eclipser Installer version: 1.5.0 Build 2617, which appears to be the latest currently publicly released auto-updated one, has e.g. org.eclipse.equinox.p2.core v2.4.0.v20150527-1706 - but an Eclipse IDE for Java Developers Version: Neon:1a Release (4.6.1) has an org.eclipse.equinox.p2.core 2.4.100.v20160419-0834 ... NB: I am NOT certain that the "stuck" problem which is is about is in equinox.p2.core, but as other bundles are likely about a full year off, perhaps it would be sensible to upgrade the versions of all p2 components used in Oomph to the latest released ones available at this point?

FTR: In the mean time, to unblock end-users of https://github.com/vorburger/opendaylight-eclipse-setup, I just have, for now, simply completely removed http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/ from it, and confirmed that this "fixes" this problem in the short term. Note to anyone reading this: You have to wipe your ~/.p2 directory, because otherwise if you've used it before, Oomph will still choke on "bad" (incompatible) content already in it.

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745874 is a reply to message #1745637] Tue, 18 October 2016 16:19 Go to previous messageGo to next message
Missing name Mising name is currently offline Missing name Mising nameFriend
Messages: 3
Registered: October 2016
Junior Member
Hi Michael,

Yes, that's https://github.com/vorburger/opendaylight-eclipse-setup.

Could you please explain how to disable or make it an optional during the installation ?

Thanks,
Aziz

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745879 is a reply to message #1745874] Tue, 18 October 2016 18:20 Go to previous messageGo to next message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
Aziz, I have yesterday simply completely removed http://download.eclipse.org/linuxtools/updates-docker-nightly/plugins/ from https://github.com/vorburger/opendaylight-eclipse-setup, so you this problem should be solved for now. You'll have to wipe your ~/.p2 directory, because otherwise if you've used it before, Oomph will still choke on "bad" (incompatible) content already in it. -- BTW: Could I suggest that you raise future issues specific to opendaylight-eclipse-setup support on the general OpenDaylight development list (dev@lists.opendaylight.org) with email subject topic prefix "[eclipse]" instead of on this eclipse.org forum? This place is typically more for development of Oomph setup models.

Ed, glad it works on windows BUT I just hope we didn't simply "cross" - FYI judging from our overlapping posts here, I was removing the problematic p2 site just about when you tried this out... Wink Based on my findings here, as detailed above, I believe it would be sensible to upgrade the versions of all p2 related components used in Oomph to the latest released ones available at this point. Would you like me to raise a bugzilla about that?

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745880 is a reply to message #1745879] Tue, 18 October 2016 18:34 Go to previous messageGo to next message
Eike Stepper is currently offline Eike StepperFriend
Messages: 6693
Registered: July 2009
Senior Member
Please never just wipe important shared folders such as the ~/.p2 folder unless you really know what you're doing!!! This can destroy all your other installations if you appear have some. If you really can't fix the problem in that folder you should rename it and only delete it when you're absolutely sure that you don't need it anymore, i.e., that all your IDEs still work.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745894 is a reply to message #1745880] Wed, 19 October 2016 05:46 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33264
Registered: July 2009
Senior Member
Sorry, but this thread is so long and so wandering... Never having been able to reproduce as problem anywhere I can't conclude that something in some newer version of something fixed something. From what you describe, the problem should be reproducible with a simple p2 task that installs some specific IU from a specific update site that serves up problematic content. Please give me something focused that I can use to reproduce the problem on some platform.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1745993 is a reply to message #1745879] Thu, 20 October 2016 09:51 Go to previous messageGo to next message
Missing name Mising name is currently offline Missing name Mising nameFriend
Messages: 3
Registered: October 2016
Junior Member
Hi Michael,

That's great. It is working now. The installation is working now.

Thanks,
Aziz

Report message to a moderator

Re: Stuck doing something/looping around (not deadlock) in SignatureBlockProcessor [message #1747533 is a reply to message #1745894] Tue, 15 November 2016 16:58 Go to previous message
Michael Vorburger is currently offline Michael VorburgerFriend
Messages: 103
Registered: July 2009
Senior Member
Ed, as promised during EclipseCon, follow-up in https://bugs.eclipse.org/bugs/show_bug.cgi?id=507559 ...

Report message to a moderator

Previous Topic:Project with only P2 Director but no Git Clone nor Stream
Next Topic:Error at installation
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Dec 26 21:12:25 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly