Community
Participate
Working Groups
Getting org.eclipse.jdt.internal.ui.browsing.JavaBrowsingPart 1.64 fails with attached error. Other revisions work fine. Test Case: 1. Connect to dev.eclipse.org. 2. Add org.eclipse.jdt.ui to your workspace 3. Open the history for org.eclipse.jdt.internal.ui.browsing.JavaBrowsingPart 4. Double-click on revision 1.64
Created attachment 789 [details] The error reported by CVS
This works for me. It appears that the problem was a server lock that has since been released. Does it work for you now?
No it does not. same result (you have to use exactly 1.64). I'm using build 20020508
What revision of the file do you have loaded?
revision 1.65 - and it is still not working ;-)
Can others in your Team access the file?
There do not appear to be any locks on the server. The only odd thing is that the permissions on the server file JavaBrowsingPerspectiveFactory.java,v are -r- -rw-r-x instead of -r--r--r--. This is odd since CVS wouldn't do this. If you still have this problem, could you try setting the permission to -r--r--r--. Also, could you check if others who have write access can access the file revision.
I tested it again and it still did not work. Then I tried to see if the CVS log contains info -> no. Then I set compression to 0 and voilà it works! Then I set compression back to 6 (default) and it still works. NOTE: When I exit and then restart (compression is 6) it again doesn't work.
Are you using J9? J9 has a bug with compression. It was fixed but I don't think the latest J9 drops ae Eclipse friendly.
java version "1.3.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20020403 (JIT ena bled: jitc))
I have reproduced this now. It only happens for a compression level of 6 (didn't happen for 5 anyway). It appears to be a problem with the server and the contents of the file in question. The command line client doesn't have this problem as it uses the Gzip-Stream request instead of gzip-file-contents.
Solution will be to mention in release notes
Marking post 2.0, keyword readme for 2.0 notes
Reopening to leave around as info
Can't follow your comment. Do you leave the bug as info because it is a bug in the IBM JDK and not in Eclipse? If it's not a JDK but then we should either fix it or not allow compression levels higher than 5.
*** Bug 35693 has been marked as a duplicate of this bug. ***
*** Bug 36295 has been marked as a duplicate of this bug. ***
Given that the bug is a CVS server bug, we should consider Dani's suggestion for 2.1.1.
Post 3.0
*** Bug 38664 has been marked as a duplicate of this bug. ***
*** Bug 76871 has been marked as a duplicate of this bug. ***
Compression levels 6 through 9 are now disabled