Bug 356724 - Error while editing java Files
Summary: Error while editing java Files
Status: VERIFIED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6.2   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: 3.8 M2   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-05 07:36 EDT by Manfred Schwarz CLA
Modified: 2015-04-25 07:20 EDT (History)
4 users (show)

See Also:


Attachments
Log file for the "Compute launch button tooltip MALFORMED" problem (61.97 KB, application/octet-stream)
2015-04-25 06:29 EDT, Donghua Liu CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Manfred Schwarz CLA 2011-09-05 07:36:35 EDT
after an OS Upgrade and a switch to Java SDK 7 i get the following stacktrace:
i tried to install sdk 6 update 27, but wiht no success.
There are several errors with different Message:
- "An internal error occurred during: "Compute launch button tooltip"."
- "Designer [8.1.0.r36x201010220706]: MALFORMED"
- "Error in JDT Core during AST creation"

The stacktrace looks always like this
java.lang.IllegalArgumentException: MALFORMED
	at java.util.zip.ZipCoder.toString(Unknown Source)
	at java.util.zip.ZipFile.getZipEntry(Unknown Source)
	at java.util.zip.ZipFile.access$900(Unknown Source)
	at java.util.zip.ZipFile$1.nextElement(Unknown Source)
	at java.util.zip.ZipFile$1.nextElement(Unknown Source)
	at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(JarPackageFragmentRoot.java:84)
	at org.eclipse.jdt.internal.core.JavaProjectElementInfo.initializePackageNames(JavaProjectElementInfo.java:252)
	at org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(JavaProjectElementInfo.java:225)
	at org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(JavaProjectElementInfo.java:290)
	at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2282)
	at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2292)
	at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1321)
	at org.eclipse.jdt.internal.core.JavaProject.findType(JavaProject.java:1228)
	at org.eclipse.jdt.internal.core.manipulation.JavaElementPropertyTester.test(JavaElementPropertyTester.java:155)
	at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
	at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99)
	at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
	at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:91)
	at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
	at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:150)
	at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
	at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72)
	at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
	at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53)
	at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.evalEnablementExpression(LaunchShortcutExtension.java:287)
	at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.getShortcutsForSelection(LaunchingResourceManager.java:452)
	at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager.computeLabels(LaunchingResourceManager.java:237)
	at org.eclipse.debug.internal.ui.contextlaunching.LaunchingResourceManager$2.run(LaunchingResourceManager.java:138)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)



-- Configuration Details --
Product: Eclipse 1.3.2.20110218-0812 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.jdt 3.6.2.r362_v20101117-0800-7z8XFW6FLFlmjJcvz03jyeFBLS_F
Comment 1 Walter Harley CLA 2011-09-06 12:39:58 EDT
Sounds like a bogus entry in the classpath?
Comment 2 Olivier Thomann CLA 2011-09-06 14:03:09 EDT
Could you please provide the whole .log file (compressed if too big)?
Thanks.
Comment 3 Manfred Schwarz CLA 2011-09-06 15:39:05 EDT
Hi,
As Walter assumed - it was a misconfiguration. I unchecked a system in the Java Configuration Panel and thought it would have effect on my classpath ;) But it had not. When i call my Helios Eclipse Relesae with the -vm c:\javasdk\bin library the error disappears. So it is a user error but Walter helped me finding the error. Sorry for taking your time - and thanks again.
Can i close the bug ?
Regards Manfred
Comment 4 Olivier Thomann CLA 2011-09-06 15:40:38 EDT
Closing as INVALID.
Comment 5 Ayushman Jain CLA 2011-09-12 16:28:33 EDT
Verified for 3.8M2
Comment 6 Steffen Feige CLA 2013-05-29 08:11:11 EDT
I have also this Problem under XP with Eclipse 4.2.2

java.lang.IllegalArgumentException: MALFORMED
	at java.util.zip.ZipCoder.toString(Unknown Source)
	at java.util.zip.ZipFile.getZipEntry(Unknown Source)
	at java.util.zip.ZipFile.access$900(Unknown Source)
	at java.util.zip.ZipFile$1.nextElement(Unknown Source)
	at java.util.zip.ZipFile$1.nextElement(Unknown Source)
	at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(JarPackageFragmentRoot.java:86)
	at org.eclipse.jdt.internal.core.JavaProjectElementInfo.initializePackageNames(JavaProjectElementInfo.java:252)...


it comes from an jar file in the classpath which has been recompressesed 7zip.
Comment 7 Donghua Liu CLA 2015-04-25 06:29:22 EDT
Created attachment 252761 [details]
Log file for the "Compute launch button tooltip MALFORMED" problem
Comment 8 Donghua Liu CLA 2015-04-25 06:30:47 EDT
Comment on attachment 252761 [details]
Log file for the "Compute launch button tooltip MALFORMED" problem

I have the similar problem, It popped up a dialog which said "Compute launch button tooltip MALFORMED"
Comment 9 Donghua Liu CLA 2015-04-25 07:20:03 EDT
Finally, I found the problem, one of my project dependency, a jar file was broken.