Bug 408338 - JarIndexLocation.getInputStream failed
Summary: JarIndexLocation.getInputStream failed
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.3   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 4.6 M3   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2013-05-17 08:47 EDT by Dani Megert CLA
Modified: 2015-10-28 09:01 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2013-05-17 08:47:57 EDT
http://download.eclipse.org/eclipse/downloads/drops4/I20130516-2200/testresults/html/org.eclipse.jdt.core.tests.model_win32.win32.x86_7.0.html


zip file closed

java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.ensureOpen(ZipFile.java:632)
at java.util.zip.ZipFile.getInputStream(ZipFile.java:345)
at java.util.jar.JarFile.getInputStream(JarFile.java:403)
at org.eclipse.jdt.internal.core.index.JarIndexLocation.getInputStream(JarIndexLocation.java:89)
at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java:623)
at org.eclipse.jdt.internal.core.index.DiskIndex.addQueryResults(DiskIndex.java:199)
at org.eclipse.jdt.internal.core.index.Index.query(Index.java:143)
at org.eclipse.jdt.internal.core.search.matching.TypeDeclarationPattern.queryIn(TypeDeclarationPattern.java:310)
at org.eclipse.jdt.core.search.SearchPattern.findIndexMatches(SearchPattern.java:2297)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.findIndexMatches(MatchLocator.java:269)
at org.eclipse.jdt.internal.core.search.PatternSearchJob.search(PatternSearchJob.java:109)
at org.eclipse.jdt.internal.core.search.PatternSearchJob.execute(PatternSearchJob.java:65)
at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:277)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.searchAllTypeNames(BasicSearchEngine.java:1135)
at org.eclipse.jdt.core.search.SearchEngine.searchAllTypeNames(SearchEngine.java:746)
at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.waitUntilIndexesReady(AbstractJavaModelTests.java:2999)
at org.eclipse.jdt.core.tests.model.JavaIndexTests.testIndexInJar(JavaIndexTests.java:793)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.runTest(SuiteOfTestCases.java:104)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.superRun(SuiteOfTestCases.java:88)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$1.protect(SuiteOfTestCases.java:76)
at org.eclipse.jdt.core.tests.model.SuiteOfTestCases$Suite.run(SuiteOfTestCases.java:85)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:655)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:310)
at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
at org.eclipse.core.launcher.Main.main(Main.java:34)
Comment 1 Jay Arthanareeswaran CLA 2013-05-17 11:52:45 EDT
I can't say whether this is a file system issue (perhaps transient) or a concurrency. Will try running the automated test suite and see if it reveals anything.
Comment 2 Jay Arthanareeswaran CLA 2015-10-26 23:58:19 EDT
We haven't seen this error since. Looks like one off case some external factor triggering this. Closing the bug.
Comment 3 Manoj N Palat CLA 2015-10-28 09:01:55 EDT
(In reply to Jay Arthanareeswaran from comment #2)
> We haven't seen this error since. Looks like one off case some external
> factor triggering this. Closing the bug.

Verified for Neon 4.6 M3 Build id: I20151026-2000