今天在启动eclipse时,我选了炫目所在的文件夹,然后确定,就出现问题了,进度条走了一部分弹出一个错误,我打开错误发现里面报的是空指针异常,后面我重新启动时之后又报了一个下面这样的异常
!SESSION 2013-12-27 11:08:13.953 ----------------------------------------------- eclipse.buildId=M20120208-0800 java.version=1.6.0_32 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.osgi 4 0 2013-12-27 11:08:23.015 !MESSAGE Application error !STACK 1 java.lang.ClassFormatError: Illegal UTF8 string in constant pool in class file org/eclipse/ui/internal/NavigationHistory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:626) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:608) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:562) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:486) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:459) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.eclipse.ui.internal.WorkbenchPage.<init>(WorkbenchPage.java:162) at org.eclipse.ui.internal.tweaklets.Workbench3xImplementation.createWorkbenchPage(Workbench3xImplementation.java:39) at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:796) at org.eclipse.ui.internal.Workbench$23.runWithException(Workbench.java:1229) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.core.jobs 2 2 2013-12-27 11:08:23.578 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.ide.IDEWorkbenchActivityHelper$4 !SESSION 2013-12-27 11:25:48.500 ----------------------------------------------- eclipse.buildId=M20120208-0800 java.version=1.6.0_32 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.osgi 4 0 2013-12-27 11:25:56.781 !MESSAGE Application error !STACK 1 java.lang.ClassFormatError: Illegal UTF8 string in constant pool in class file org/eclipse/ui/internal/NavigationHistory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:626) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:608) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:562) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:486) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:459) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216) at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:400) at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:476) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.eclipse.ui.internal.WorkbenchPage.<init>(WorkbenchPage.java:162) at org.eclipse.ui.internal.tweaklets.Workbench3xImplementation.createWorkbenchPage(Workbench3xImplementation.java:39) at org.eclipse.ui.internal.WorkbenchWindow.busyOpenPage(WorkbenchWindow.java:796) at org.eclipse.ui.internal.Workbench$23.runWithException(Workbench.java:1229) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1600) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2609) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !ENTRY org.eclipse.core.jobs 2 2 2013-12-27 11:25:57.343 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.ide.IDEWorkbenchActivityHelper$4 !SESSION 2013-12-27 11:44:12.921 ----------------------------------------------- eclipse.buildId=M20120208-0800 java.version=1.6.0_32 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=zh_CN Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.ui 4 4 2013-12-27 11:44:52.265 !MESSAGE Referenced part does not exist yet: org.eclipse.jdt.ui.PackageExplorer. !ENTRY org.zeroturnaround.eclipse 2 0 2013-12-27 11:45:18.312 !MESSAGE Cannot convert rebel.notification.port to integer !ENTRY org.eclipse.jst.jsp.core 4 4 2013-12-27 11:45:39.531 !MESSAGE A workspace crash was detected. The previous session did not exit normally. Not using saved taglib indexes.
我重新启动了计算机就OK了,但是我没有找到原因。
相关推荐
Eclipse是一款广泛使用的开源...总的来说,“eclipse启动时间插件”是针对Eclipse启动慢问题的一种解决策略,通过优化启动流程来提升效率。不过,用户还需要结合自身情况,综合运用多种方法来最大化Eclipse的启动速度。
4. **代码编辑器**:具有语法高亮、代码补全、代码提示、错误检测等功能。 5. **调试工具**:内置了强大的调试工具,支持断点、逐步执行、变量查看等调试功能。 6. **版本控制集成**:支持与 Git、SVN 等版本控制...
此错误表明Eclipse启动时检测到当前安装的JVM(Java虚拟机)版本过低,不满足Eclipse运行的要求。 #### 二、问题分析 1. **JVM版本不匹配**:Eclipse需要特定版本的JVM支持才能正常运行,通常情况下,Eclipse至少...
1. **JVM版本不兼容**:如果系统中安装的Java虚拟机版本与Eclipse所需版本不一致,可能会导致Eclipse启动失败。 2. **插件冲突**:Eclipse支持丰富的插件扩展功能,但过多或不兼容的插件可能会导致启动问题。 3. **...
请注意,在编辑此文件之前最好备份原始文件,以免造成不可逆的错误。 - 在 `eclipse.ini` 文件中,您可以看到以下关键配置项: - `-vm`: 该指令用于指定 Eclipse 应该使用的 Java 虚拟机路径。例如: ``` -vm D:...
3. **JRE或JDK版本不兼容**:Eclipse可能因为与Java运行环境版本不匹配而无法启动。确保你的系统安装了与Eclipse版本兼容的JRE或JDK,并在Eclipse的配置中正确设置。 4. **Eclipse插件冲突**:过多或者冲突的插件也...
Eclipse中启动Tomcat服务器产生错误的原因及解决方案
如果使用的Tomcat版本与Eclipse不兼容,可能会导致启动时出现各种错误。 #### 1.2 JDK环境变量设置错误 JDK(Java Development Kit)是运行Tomcat的基本环境之一。如果JDK环境变量设置不当,如JAVA_HOME未正确设置...
- 如果遇到问题,如启动失败或无法访问,检查日志文件(位于Tomcat的logs目录下)以获取错误信息。 通过上述步骤,你可以在Eclipse中便捷地部署和启动Web项目,利用Eclipse的强大功能和Tomcat的稳定性能,实现高效...
在实际开发环境中,特别是在开发阶段,很少出现因字节码错误而导致的问题,因此关闭验证可以在不影响正常开发的情况下提高启动速度。 ##### 2. `-Xms24m` 和 `-Xmx96m` 设定初始堆大小和最大堆大小可以有效避免JVM...
确保服务器成功启动且无错误。 5. **测试连接**:使用XMPP客户端(如 Psi, Gajim 等)连接到运行中的Tigase服务器,验证其正常工作。 通过这个压缩包,开发者不仅能学习到Tigase服务器的内部工作原理,还可以快速...
这可能是由于Eclipse启动时分配给它的内存太小,或者系统本身可用的物理内存不足。 ##### 2. 解决步骤 解决该问题的关键在于修改Eclipse的启动配置文件`eclipse.config`或`eclipse.ini`。具体步骤如下: - 打开...
启动eclipse 时出现错误警告
8. **启动模式**:如果Eclipse依然无法启动,可以尝试使用干净启动模式(`-clean`参数)或者无插件启动模式(`-no-plugins`参数),以排除特定插件的问题。 9. **检查错误日志**:在`workspace/.log`文件中查看...
Eclipse启动Tomcat后无法访问项目解决办法 前言: Eclipse中的Tomcat可以正常启动,不过发布项目之后,无法访问,包括http://localhost:8080/的小猫页面也无法访问到,报404错误。这是因为Eclipse所指定的Server ...
### Eclipse启动Tomcat内存泄漏解决方案 #### 一、问题背景 在使用Eclipse集成开发环境(IDE)启动Tomcat服务器时,可能会遇到内存泄漏的问题。这种情况不仅会导致应用程序运行缓慢,严重时甚至会使得Tomcat服务器...
关于 eclipse启动卡死的问题(eclipse上一次没有正确关闭,导致启动的时候卡死错误解决方法),自己常用的解决方法: 方案一(推荐使用,如果没有这个文件,就使用方案二): 到\.metadata\.plugins\org.eclipse....
- 当Eclipse启动失败时,它通常会在工作区的`.log`文件中记录错误信息。查看这些日志可以帮助定位问题的具体原因。 以上是针对“initializing java tooling (1%)”问题的一些常见解决方案。请按照步骤逐一排查,找...
当出现"The connection to adb is down"的错误时,意味着电脑与手机之间的ADB连接中断或不稳定。 以下是一些解决Eclipse连接不上手机问题的方法: 1. **检查USB连接**:确保手机通过USB线正确连接到电脑,并尝试...