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

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Sat Jun 11 07:18:24 EDT 2011 

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

Snjezana Peco commented on JBIDE-8854:
--------------------------------------

This is an upstream issue.
When updating/installing a plugin, Eclipse opens all jarred plugins and doesn't close them until shutdown. 
The steps to reproduce the issue are the following:

- set ulimit -f to > 20000
- install Eclipse IDE for Java Developers 3.7RC3, JBT Tools, m2eclipse, m2eclipse-wtp Maven Support
- start Eclipse without the -clean option
Eclipse will start normally.
- exit Eclipse
- set ulimit -f to 1024
- start Eclipse without the -clean option
Eclipse will start normally. JBoss Tools plugins are not the cause of the issue.

- exit Eclipse and start it with the -clean option
or
- install/update some plugin (QuickImage http://psnet.nu/eclipse/updates, for instance) and restart Eclipse

You will get the "too many open files" error.

- set ulimit -f to >20000
- start Eclipse with the -clean option and exit it
- set ulimit -f to 1024
- start Eclipse without the -clean option

Eclipse will start normally. 

The problem happens only when Eclipse reinitializes plugins (starting with the -clean option or restarting after install/update) and there are a lot of jarred plugins (my testing environment has 857 jarred plugins).  It doesn't matter if those plugins are JBT or not.

There are a lot of Eclipse jiras related to this issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=349073
https://bugs.eclipse.org/bugs/show_bug.cgi?id=302044
https://bugs.eclipse.org/bugs/show_bug.cgi?id=138182
...

The osgi.bundlefile.limit property mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=138182#c10 doesn't help. This property has an effect only if Eclipse starts without the -clean option.
The default value for osgi.bundlefile.limit is already 100 in Eclipse 3.7RC3 .

I suppose to add this info to the Release Notes. 

> JBT 3.3.0 nightly build installation errors (Eclipse 3.7)
> ---------------------------------------------------------
>
>                 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: Snjezana Peco
>            Priority: Critical
>             Fix For: 3.3.0.M2
>
>
> 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