Bug 97091 - Code Completion stops working totally after using Eclipse for a while
Summary: Code Completion stops working totally after using Eclipse for a while
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-05-27 18:20 EDT by Morten Moeller CLA
Modified: 2009-08-30 02:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Morten Moeller CLA 2005-05-27 18:20:42 EDT
Since M7, I've had problems with code completion stoping to work from time to time. 

I get a lot of these errors however before it happens (the stack trace is the
same, but the package changes.. it will say Java Model Status [foobar [in
/lib/weblogic.jar where foobar can be com, javax.transaction,net etc..

This never happened in M6.. A restart fixes the issue.. There are no other
exceptions in my logs and no popups happen.



!ENTRY org.eclipse.jdt.ui 4 10001 2005-05-27 16:56:34.597
!MESSAGE Internal Error
!STACK 1
Java Model Exception: Java Model Status [com [in /lib/weblogic.jar [in
process-server]] does not exist]
        at
org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:468)
        at
org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:499)
        at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:232)
        at
org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:218)
        at
org.eclipse.jdt.internal.core.JarPackageFragment.containsJavaResources(JarPackageFragment.java:92)
        at
org.eclipse.jdt.internal.ui.packageview.PackageFragmentProvider.isEmpty(PackageFragmentProvider.java:172)
        at
org.eclipse.jdt.internal.ui.packageview.PackageFragmentProvider.getBottomPackage(PackageFragmentProvider.java:152)
        at
org.eclipse.jdt.internal.ui.packageview.PackageFragmentProvider.filter(PackageFragmentProvider.java:143)
        at
org.eclipse.jdt.internal.ui.packageview.PackageFragmentProvider.getChildren(PackageFragmentProvider.java:88)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.getChildren(PackageExplorerContentProvider.java:155)
        at
org.eclipse.jdt.internal.ui.packageview.WorkingSetAwareContentProvider.getChildren(WorkingSetAwareContentProvider.java:81)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.isExpandable(PackageExplorerPart.java:299)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus(AbstractTreeViewer.java:1831)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:536)
        at
org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:514)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:494)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1076)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1073)
        at
org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:1604)
        at
org.eclipse.jface.viewers.StructuredViewer.setSelectionToWidget(StructuredViewer.java:1494)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.setSelectionToWidget(PackageExplorerPart.java:600)
        at
org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1450)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.showInput(PackageExplorerPart.java:1447)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.editorActivated(PackageExplorerPart.java:1412)
        at
org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$1.partActivated(PackageExplorerPart.java:211)
        at org.eclipse.ui.internal.PartListenerList$1.run(PartListenerList.java:72)
        at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1029)
        at org.eclipse.core.runtime.Platform.run(Platform.java:775)
        at
org.eclipse.ui.internal.PartListenerList.fireEvent(PartListenerList.java:58)
        at
org.eclipse.ui.internal.PartListenerList.firePartActivated(PartListenerList.java:70)
        at
org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:73)
        at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:166)
        at
org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:54)
        at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:112)
        at
org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:2754)
        at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:531)
        at org.eclipse.ui.internal.WorkbenchPage.makeActive(WorkbenchPage.java:1058)
        at org.eclipse.ui.internal.WorkbenchPage.bringToTop(WorkbenchPage.java:739)
        at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2267)
        at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2185)
        at org.eclipse.ui.internal.WorkbenchPage.access$8(WorkbenchPage.java:2177)
        at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2163)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
        at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2158)
        at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2140)
        at
org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$1.run(SourceLookupFacility.java:353)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
        at
org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:362)
        at
org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:278)
        at
org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(SourceLookupFacility.java:209)
        at org.eclipse.debug.ui.DebugUITools.displaySource(DebugUITools.java:673)
        at
org.eclipse.debug.internal.ui.views.launch.LaunchView$SourceDisplayJob.runInUIThread(LaunchView.java:209)
        at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:93)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
        at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:118)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2747)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2478)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1601)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1565)
        at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:315)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
        at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:230)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:371)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:160)
        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:324)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:330)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:274)
        at org.eclipse.core.launcher.Main.run(Main.java:977)
        at org.eclipse.core.launcher.Main.main(Main.java:952)
!SUBENTRY 1 org.eclipse.jdt.core 4 969 2005-05-27 16:56:34.598
!MESSAGE com [in /lib/weblogic.jar [in process-server]] does not exist
Comment 1 Frederic Fusier CLA 2005-06-08 12:19:31 EDT
Do you still experience this error with RC1?
Comment 2 Morten Moeller CLA 2005-06-08 16:03:02 EDT
I haven't been able to upgrade yet. Its simpler for me to keep the same 
version on my eclipse ide as the one we use for our product, and we're having 
blocking issues with RC1 so I cannot upgrade yet. I've also tried to take the 
massive weblogic.jar out of my build classpath, and so far that might have 
helped. 
 
I've noticed a couple of other things that happen when this happens. My import 
list has various randing errors on imports that should be valid (like 
org.eclipse.ui.view will be marked red as Eclipse cannot find it). It is like 
the jobs that keep the models (I forget what their called) behind the scene 
just dies and doesn't wake up again.. But I see no errors or exceptions 
besides the ones pasted in here. 
 
Hopefully I can upgrade to RC2 and see if that fixes it. It is annoying, but a 
restart of the IDE fixes it (at least temporary). 
Comment 3 Morten Moeller CLA 2005-06-27 16:20:04 EDT
This just happened again on RC3 after not happening for a long time. 
 
It seems to be happening as soon as the "weblogic.jar" is in the build path of 
any project. I just added a new project and happened to add weblogic.jar as a 
library to it, and 10-15 minutes later this happened again.  
 
But as long as I keep this one out, it works fine. It is either something 
inside the weblogic.jar causing this or its size is just too big alltogether 
(30mb). I'm taking it out again, but this might be an issue if people are using 
Eclipse for weblogic specific development. 
Comment 4 David Audel CLA 2006-03-29 03:48:27 EST
I don't find a test case to reproduce the bug.

I close as REMIND this bug. If you can reproduce the bug with a recent build, please reopen this bug.
Comment 5 Denis Roy CLA 2009-08-30 02:05:54 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.