[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8854) JBT 3.7.0 nightly build installation errors

Isaac Rooskov (JIRA) jira-events at lists.jboss.org
Thu May 5 18:15:19 EDT 2011 

    [ https://issues.jboss.org/browse/JBIDE-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600204#comment-12600204 ] 

Isaac Rooskov commented on JBIDE-8854:
--------------------------------------

2. I decided to try downloading from the update site again (with a fresh Eclipse Indigo install) to test it since that's where the issue was (but your info is great, is that in one of our guides already, if not I should add it). 

Upon trying to download from the update site again, I was faced with the following issues:
 
 - First I tried download just the "All of JBoss Tools 3.3" package but I was faced with an erorr about a missing 'mozilla' plug-in.

 - I then tried selecting everything except "All of JBoss Tools 3.3" I got the following error:

An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,net.jcip.annotations,1.0.0.
MD5 hash is not as expected. Expected: 64d425b74aa6cfe0d6c221c3cd84ee28 and found 7fd51bd44b59c77794c242940b69cbe1.
Problems downloading artifact: osgi.bundle,net.sf.saxon,8.7.3.
MD5 hash is not as expected. Expected: c261cb3f34276d6c1ce76c9d139459d8 and found 6ef97d9f749b7f4f4cbc693d8f5d99cf.
Problems downloading artifact: osgi.bundle,org.apache.poi,2.5.1.
MD5 hash is not as expected. Expected: 35c8e3a44fc0434c10835052499601ea and found 104e274badbc266fdb0e7bb01f9e5691.
Problems downloading artifact: osgi.bundle,org.jaxen,1.0.7.
MD5 hash is not as expected. Expected: f2f6e27c67263599ac49524b35848752 and found 22a6345c6c5831d6270f94b9462c1670.
Problems downloading artifact: org.eclipse.update.feature,org.jboss.savara.tools.feature,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: 8ccf25bfc2aa84e37e9b47d23e7a5626 and found fccfeaa82b2779121759ad2995fc852f.
Problems downloading artifact: osgi.bundle,org.savara.tools.bpel,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: 340243167e6ea7cd56eac2f8f6d3f248 and found 3c23b6424506e43bb6548fd74bc45a2f.
Problems downloading artifact: osgi.bundle,org.savara.tools.common,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: e440490ac26db276a0c9b8b5609de999 and found 52dd695233d7c0b99094cda8714704f3.
Problems downloading artifact: org.eclipse.update.feature,org.savara.tools.feature,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: ba7edd9583e28c30e529c62f655ada6d and found eb1daba3cc3e94a39e3d01a911c0db15.
Problems downloading artifact: osgi.bundle,org.savara.tools.monitor,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: b1b633d592c07dbf0bffa8ba4bf6c10b and found 1198c4a57c039863254e320a0f1b3e92.
Problems downloading artifact: osgi.bundle,org.savara.tools.scenario,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: 25ead6ff954485b8eb024269e61b36fa and found d95cf28c2433a0bcef89096ad02d4e0b.
Problems downloading artifact: osgi.bundle,org.savara.tools.validator,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: 5de1101070a0d662aa3e831c90c5609f and found eec8f6596397c5931b14aa6336c8409f.
Problems downloading artifact: osgi.bundle,org.savara.tools.wsdl,2.0.0.20110505-M3.
MD5 hash is not as expected. Expected: 4505defd48b7e3cac491e225600ab03e and found b678996be69ae3fa14c43bc1d9271df5.
Problems downloading artifact: osgi.bundle,org.wsdl4j,1.4.0.
MD5 hash is not as expected. Expected: 430e7fcd389602cdb36f6dfde5c6ef97 and found 483de66de04c2f8a78aa43aa42c5f2fe.

 - Then I went back to trying only "All JBoss Tools 3.3" and it installed. 

3. Ah, ok, I see, thanks. I tried the workaround but it didn't change anything in my original install of Eclipse Indigo, but after trying a fresh install and putting the workaround in from the beginning (and performing the above tasks of trying to install JBT 3.3) it worked :S


Finally, after Eclipse restarted with JBoss Tools 3.3 installed it would not contact any update or install sites. Once closing Eclipse and re-launching it would then contact the sites.

It seems that this is quite volatile. I think most of this can possibly be associated with Eclipse Indigo still being in development, however this is not my area of expertise so I'm passing all this info along to you so you can make that judgement ;) 

> JBT 3.7.0 nightly build installation errors
> -------------------------------------------
>
>                 Key: JBIDE-8854
>                 URL: https://issues.jboss.org/browse/JBIDE-8854
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: updatesite
>    Affects Versions: 3.3.x
>         Environment: Fedora 14 64bit with Eclipse Indigo M6a
>            Reporter: Isaac Rooskov
>            Assignee: Isaac Rooskov
>
> Two issues present when installing from the 3.7.0 nightly build update site within Eclipse Indigo M6a:
> 1) Upon clicking everything in the list of install items (except the one that says "All JBoss Tools 3.2.0"), after everything is downloaded and the installation begins, this error appears:
> An error occurred while collecting items to be installed
> session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.esb.core,1.5.0.v20110504-0713-H212-M1
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.esb.feature,1.3.0.v20110504-0713-H212-M1
> No repository found containing: osgi.bundle,org.jboss.tools.esb.project.core,1.4.0.v20110504-0713-H212-M1
> No repository found containing: osgi.bundle,org.jboss.tools.esb.project.ui,1.4.0.v20110504-0713-H212-M1
> No repository found containing: osgi.bundle,org.jboss.tools.esb.ui,1.4.0.v20110504-0713-H212-M1
> No repository found containing: osgi.bundle,org.jboss.tools.esb.validator,1.4.0.v20110504-0713-H212-M1
> 2)Upon skipping components that the above files relate to, installation completes and Eclipse is restarted. Upon re-launching Eclipse the following error is displayed before a workspace location is asked for:
> An error has occurred. See the log file
> /home/irooskov/Work/JBT/eclipse/configuration/<random_long_number_string>.log.
> Within the generated log file, the following can be found:
> !ENTRY org.eclipse.equinox.registry 4 0 2011-05-05 08:27:17.902
> !MESSAGE Unable to create output stream for registry cache.
> !STACK 0
> java.io.FileNotFoundException: /home/irooskov/Work/JBT/eclipse/configuration/org.eclipse.core.runtime/.extraData3426067224546608204.new (Too many open files)
> 	at java.io.FileOutputStream.open(Native Method)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
> 	at org.eclipse.core.internal.registry.TableWriter.openFiles(TableWriter.java:96)
> 	at org.eclipse.core.internal.registry.TableWriter.saveCache(TableWriter.java:78)
> 	at org.eclipse.core.internal.registry.ExtensionRegistry.stop(ExtensionRegistry.java:802)
> 	at org.eclipse.core.internal.registry.osgi.Activator.stopRegistry(Activator.java:151)
> 	at org.eclipse.core.internal.registry.osgi.Activator.stop(Activator.java:66)
> 	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764)
> 	at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510)
> 	at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565)
> 	at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1160)
> 	at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595)
> 	at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257)
> 	at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215)
> 	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284)
> 	at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:690)
> 	at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:597)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> 	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbosstools-issues mailing list