解决：eclipse 非正常关闭，导致无法正常启动

eclipse 无法正常启动：

!ENTRY org.eclipse.ui.navigator 4 2 2016-09-07 11:23:54.181
!MESSAGE 从插件调用代码时出现问题：“org.eclipse.ui.navigator”。
!STACK 0
java.lang.NullPointerException
    at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.getChildren(ItemTreeStateProviderManager.java:74)
    at org.eclipse.jpt.common.ui.internal.navigator.NavigatorContentProvider.getChildren(NavigatorContentProvider.java:109)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94)
    at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
    at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125)
    at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1365)
    at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
    at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:905)
    at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
    at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2647)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1918)
    at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:684)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1893)
    at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1850)
    at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561)
    at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1528)
    at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1436)
    at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
    at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1397)
    at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1525)
    at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:533)
    at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:350)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$3.run(PackageExplorerContentProvider.java:957)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runUpdates(PackageExplorerContentProvider.java:195)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.runPendingUpdates(PackageExplorerContentProvider.java:187)
    at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$1.runInUIThread(PackageExplorerContentProvider.java:165)
    at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

!ENTRY org.eclipse.ui.navigator 4 0 2016-09-07 11:23:54.184
!MESSAGE 调用扩展时发生了异常：对象 P/* 的 org.eclipse.jpt.jpa.ui.jpaNavigatorContent
!STACK 0
java.lang.NullPointerException
    at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.getChildren(ItemTreeStateProviderManager.java:74)
    at org.eclipse.jpt.common.ui.internal.navigator.NavigatorContentProvider.getChildren(NavigatorContentProvider.java:109)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275)
    at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94)
    at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)

打开eclipse的工作空间目录workspace，然后一层一层进入下面的目录 workspace\.metadata\.plugins\org.eclipse.core.resources删掉.snap 文件。

时间： 2025-01-07 13:48:36

解决：eclipse 非正常关闭，导致无法正常启动的相关文章

FlashBuilder 4.7 非正常关闭导致的不能启动的解决的方法

停电.或者卡死.FB就不能正常启动了. 以下是老外给出的方法,好用: 进入.metadata/.plugins/org.eclipse.core.resources 文件夹 删除.snap文件 假设是苹果系统,则文件夹有可能是: .metadata\org.eclipse.core.resources\ 以下两个方法都不行: 1.网上说的加 -clean 參数又一次启动的方法,不靠谱,可能跟版本号不一样有关系,反正在4.7版本号没成功过. 2.整个删除.metadata 文件夹,也不好使,要又一

FlashBuilder 4.7 非正常关闭导致的不能启动的解决办法

停电.或者卡死,FB就不能正常启动了. 下面是老外给出的方法,好用: 进入.metadata/.plugins/org.eclipse.core.resources 目录 删除.snap文件 如果是苹果系统,则目录有可能是: .metadata\org.eclipse.core.resources\ 下面两个方法都不行: 1.网上说的加 -clean 参数重新启动的方法,不靠谱,可能跟版本不一样有关系,反正在4.7版本没成功过. 2.整个删除.metadata 目录,也不好使,要重新设置很多东西

解决Eclipse异常关闭后重启报 org.eclipse.swt.SWTException: Invalid thread access 的问题

. . . . . 很久没有写博客了,最近实在是太忙,一直想写点干货,但是一直没静下心来学习. 今天又在加班忙碌之中,结果谁知道越忙碌越出问题.先是 weblogic 没有正常启动,凭经验第一反应就是7001端口被其它程序占用了,然后通过命令查看之后,发现果然是被占用了,占用端口的竟然是Eclipse,查找占用端口的方式请移步至博主的另一篇文章<[windows]查询占用端口的程序——记一次解决webloigc启动失败的过程>. Eclipse之前是不占用7011端口的,这次占用估计可能是启动

04_Weblogic之受管服务器：配置受管服务器，启动受管服务器，解决因为强制关闭Weblogic之后导致启动有问题的问题，配置boot.properties

 配置受管服务器, 先启动WebLogic服务器,启动方式如下: 在WebLogic控制台中的"开发模式"---"锁定并编辑"模式下,点击"Server(服务器)"然后进行配置.(进入控制台的方式是在浏览器地址中输入:http://192.168.6.25:7001/console/login/LoginForm.jsp). 点击登录,然后进入登录页面. 3 开始配置,暂开"环境"----"服务器",进

eclipse异常关闭，无法启动tomcat解决办法

如果eclipse异常关闭,会出现以下 此时需要关闭javaw.exe即可,重新启动tomcat了. 关闭javaw.exe需要打开任务关闭器,选择详细信息,然后结束javaw.exe即可

mongoDB非正常关闭后无法启动问题

mongoDB非正常关闭后无法启动问题: http://my.oschina.net/GivingOnenessDestiny/blog/53804 http://codingstandards.iteye.com/blog/1214093 前段时间不小心非正常关闭了mongoDB,准备重启却发现不行,错误信息如下: ? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Tue Apr 17 11:13:30

myeclipse非正常关闭引起的异常解决办法

myeclipse非正常关闭,控制台server出现异常“Could not create the view: An unexpected exception was thrown.”. 解决办法: --  删除文件 “workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/ com.genuitec.eclipse.ast.deploy.core.prefs” --  重新启动myeclipse即可

解决eclipse启动插件时PermGen space问题

解决eclipse启动插件时PermGen space问题 修改启动参数增加如下: -Xms256m  -Xmx512m  -XX:PermSize=256m -XX:MaxPermSize=512m 示例解释如下: -Xms128m 表示JVM Heap(堆内存)最小尺寸128MB,初始分配 -Xmx512m 表示JVM Heap(堆内存)最大允许的尺寸256MB,按需分配.说明:如果-Xmx不指定或者指定偏小,应用可能会导致java.lang.OutOfMemory错误,此错误来自JVM不是

解决Myeclipse中端口占用，导致tomcat无法启动的问题。（Linux）

本文出自:http://blog.csdn.net/svitter 引文:http://www.2cto.com/os/201305/209285.html { ubuntu查看占用某端口的程序 查看端口使用情况,使用netstat命令. 查看已经连接的服务端口(ESTABLISHED netstat -a 查看所有的服务端口(LISTEN,ESTABLISHED) netstat -ap 查看8080端口,则可以结合grep命令:netstat -ap | grep 8080 如查看8888端