[jbosstools-issues] [JBoss JIRA] (JBIDE-17297) JBoss Central crashes and brings down JBDS 8 Beta 1

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-17297:
---------------------------------------

I can't reproduce the issue either with OracleJDK (1.7.0_55) or with OpenJDK (included into F20).
I have used JBDS Beta1-20140323-1410-B78 and Fedora 20 Live (without any updates).
According to your log, you have faced the issue described in JBIDE-17237, but it can't be the cause of the crash.
Could you check if jar files located in the <YOUR_WORKSPACE>/.metadata/.plugins/org.jboss.tools.central/proxyWizards/*/*.jar are valid?
Are there any crash log files (hs_err_pidXXX.log) in your working directory?

> JBoss Central crashes and brings down JBDS 8 Beta 1
> ---------------------------------------------------
>
>                 Key: JBIDE-17297
>                 URL: https://issues.jboss.org/browse/JBIDE-17297
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 4.2.0.Beta1
>         Environment: JBDS 8 Beta1, Fedora 20, multiple JVMs - Oracle JDK 8 (1.8.0_05), Oracle JDK 7 (1.7.0_55)
>            Reporter: Vineet Reynolds
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 4.2.0.Beta2
>
>
> I encounter crashes in JBDS 8 Beta 1, when JBDS Central is loaded.
> The following stack trace was recorded:
> {noformat}
> !MESSAGE Cannot load bundle com.jboss.jbds.central.discovery_8.0.0.Beta1_v20140408_2329_B102.jar_115481158031680986.jar from url /home/vreynolds/workspaces/JBDS8Workspaces/WFK/.metadata/.plugins/org.jboss.tools.central/proxyWizards/1400494422919/com.jboss.jbds.central.discovery_8.0.0.Beta1_v20140408_2329_B102.jar_115481158031680986.jar: zip file is empty
> !STACK 0
> java.util.zip.ZipException: zip file is empty
> 	at java.util.zip.ZipFile.open(Native Method)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:220)
> 	at java.util.zip.ZipFile.<init>(ZipFile.java:150)
> 	at java.util.jar.JarFile.<init>(JarFile.java:166)
> 	at java.util.jar.JarFile.<init>(JarFile.java:130)
> 	at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundle(DiscoveryRegistryStrategy.java:137)
> 	at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundles(DiscoveryRegistryStrategy.java:126)
> 	at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.onStart(DiscoveryRegistryStrategy.java:78)
> 	at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725)
> 	at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:125)
> 	at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> 	at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> 	at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:101)
> 	at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.getProxyWizards(ProxyWizardManager.java:121)
> 	at org.jboss.tools.central.editors.GettingStartedPage.getProxyWizards(GettingStartedPage.java:555)
> 	at org.jboss.tools.central.editors.GettingStartedPage.access$11(GettingStartedPage.java:553)
> 	at org.jboss.tools.central.editors.GettingStartedPage$5.run(GettingStartedPage.java:511)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> !SESSION 2014-05-19 15:45:30.045 -----------------------------------------------
> {noformat}
> To recover from this, I needed to be quick enough to uncheck the "load on startup" checkbox to disable JBoss Central. Re-opening JBoss Central at any other point in time causes the crash to be reproducible.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)