`

MyEclipse error log

    博客分类:
  • tool
阅读更多
!SESSION 2009-10-23 09:11:57.625 -----------------------------------------------
eclipse.buildId=I20070625-1500
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CN
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2009-10-23 09:11:58.250
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1018)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:611)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:497)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:250)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:153)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:588)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:289)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
Caused by: java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setLazyLoaded(BundleDescriptionImpl.java:287)
at org.eclipse.osgi.internal.resolver.StateImpl.resolveBundle(StateImpl.java:249)
at org.eclipse.osgi.internal.resolver.StateImpl.removeBundle(StateImpl.java:139)
at org.eclipse.osgi.internal.resolver.SystemState.removeBundle(SystemState.java:23)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.checkSystemState(BaseStorage.java:654)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.getStateManager(BaseStorage.java:643)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:385)
at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook.frameworkStart(EclipseAdaptorHook.java:78)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStart(BaseAdaptor.java:260)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:55)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
... 18 more
Root exception:
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setLazyLoaded(BundleDescriptionImpl.java:287)
at org.eclipse.osgi.internal.resolver.StateImpl.resolveBundle(StateImpl.java:249)
at org.eclipse.osgi.internal.resolver.StateImpl.removeBundle(StateImpl.java:139)
at org.eclipse.osgi.internal.resolver.SystemState.removeBundle(SystemState.java:23)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.checkSystemState(BaseStorage.java:654)
at org.eclipse.osgi.internal.baseadaptor.BaseStorage.getStateManager(BaseStorage.java:643)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.getPlatformAdmin(BaseAdaptor.java:385)
at org.eclipse.core.runtime.internal.adaptor.EclipseAdaptorHook.frameworkStart(EclipseAdaptorHook.java:78)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.frameworkStart(BaseAdaptor.java:260)
at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:55)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:611)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:497)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:250)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:153)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:588)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:289)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)

!ENTRY org.eclipse.osgi 4 0 2009-10-23 09:11:58.265
!MESSAGE Startup error
!STACK 1
java.lang.RuntimeException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:619)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:497)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:250)
at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:153)
at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:588)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:289)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
!SESSION Fri Oct 23 09:11:58 CST 2009 ------------------------------------------
!ENTRY org.eclipse.equinox.launcher 4 0 2009-10-23 09:11:58.265
!MESSAGE Exception launching the Eclipse Platform:
!STACK
java.lang.NullPointerException
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.setExportPackages(BundleDescriptionImpl.java:208)
at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:255)
at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:608)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:456)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:117)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getExportedPackageMap(StateHelperImpl.java:74)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getUnsatisfiedLeaves(StateHelperImpl.java:109)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.getUnsatisfiedLeaves(StateHelperImpl.java:145)
at org.eclipse.core.runtime.adaptor.EclipseStarter.logUnresolvedBundles(EclipseStarter.java:438)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:186)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)


用jdk中的jre 覆盖掉MyEclipse中的jre
分享到:
评论

相关推荐

    myeclipse10log4e插件

    【标题】"myeclipse10log4e插件"涉及的是在MyEclipse集成开发环境中安装和使用Log4e插件的相关知识点。Log4e是一款适用于Java项目的日志管理工具,它为MyEclipse提供了方便的日志查看和调试功能。 【描述】提到的...

    log4e插件,集成在myeclipse里面

    Log4e插件是专为Eclipse IDE设计的一款日志查看工具,尤其适用于MyEclipse集成环境。Log4e不仅提供了方便的日志查看功能,还能与应用程序无缝集成,提升开发效率。 **一、Log4e插件概述** Log4e,全称为Log for ...

    解决MyEclipse10安装VSS插件版本为1.6.2报错

    See error log for more details. (本人64win7 安装:10.7版本 64 位 32位 均可以使用) 原因:版本旧,原来做vss插件的后来就没有更新,现找到国外高手更新了,但是知道的人不多,我有这个文件 需要的 可以下载 ...

    Myeclipse开发项目时导入日志包

    日志级别包括DEBUG、INFO、WARN、ERROR和FATAL,可以根据需要调整log4j.properties文件中的配置,以控制不同级别的日志输出。此外,Log4j还支持自定义日志输出格式、异步日志处理等功能,可以根据具体需求进一步定制...

    MyEclipse10安装Log4E插件

    《MyEclipse10安装与使用Log4E插件指南》 在软件开发过程中,日志记录是一项必不可少的任务,它能帮助开发者追踪程序运行状态,定位错误和异常。Log4j是一款广泛使用的Java日志框架,而Log4E是一款专为MyEclipse...

    myeclipse10.7.1导出war问题解决办法

    9. **日志排查**:如果以上方法都无法解决问题,查看MyEclipse的错误日志,通常在"Window" > "Show View" > "Error Log"中可以找到,这有助于定位具体错误。 10. **更新或重装**:如果问题仍然存在,考虑更新...

    myeclipse导出war错误解决

    通常,这些日志可以在myEclipse安装目录的`log`文件夹下找到。 7. **社区求助**:如果问题依然无法解决,不要忘记利用互联网资源,比如Stack Overflow或myEclipse官方论坛,寻找其他开发者遇到相同问题的解决方案。...

    MyEclipse安装VSS插件步骤及错误解决

    MyEclipse安装VSS插件会一直报错an error has occurred see error log for more details:org/eclipse/ui/internal/activeeditoraction;一番麻烦后总算解决,看到有不少人也有类似问题,就共享到这里,希望有所帮助

    de.jayefem.log4e_1.3.2

    在代码中引入Log4j的Logger类,创建对应的logger实例,然后通过不同的方法(如debug(), info(), warn(), error()等)输出不同级别的日志。例如: ```java import org.apache.log4j.Logger; public class MyClass { ...

    Log4jToWriterAppender.zip

    在"Log4jToWriterAppender.zip"项目中,开发者可能深入研究了如何结合MyEclipse开发环境,有效地利用WriterAppender进行日志管理和分析,从而提高代码质量和维护性。通过实际操作和不断实践,我们可以更熟练地驾驭这...

    myeclipse10导出war包时出错解决办法

    6. **查看错误日志**:MyEclipse在出错时会生成错误日志,通过“Window > Show View > Error Log”查看,可以帮助定位问题的具体原因。 7. **社区求助**:如果以上步骤无法解决问题,可以在MyEclipse的官方论坛或...

    Java_Log4j

    在这个“Java_Log4j”的主题中,我们将深入探讨Log4j的核心概念、配置方法、使用场景以及与MyEclipse集成的相关知识。 1. **Log4j核心组件** - **Logger**: 日志记录器,是日志信息的来源,可以根据不同的等级(如...

    de.jayefem.log4e_pro_2.0.0.zip

    "log4e_pro_2.0.0.zip" 提供的正是这样一个工具,专为Java开发环境设计,特别是集成于MyEclipse中的日志管理系统——Log4E。这个版本是2.0.0,相较于之前的版本,它可能包含了更多的改进和新特性。 Log4E这个名字...

    Log4j_1.2.15 源码

    Logger负责生成日志事件,Appender决定这些事件如何被输出(如控制台、文件、数据库等),Layout则定义了日志信息的显示格式,Level用于设置不同的日志级别,如DEBUG、INFO、WARN、ERROR和FATAL。 3. **配置文件** ...

    log4jToFileAppender.zip

    在MyEclipse这样的开发环境中,我们可以直接导入"log4jToFileAppender"项目,配置好log4j配置文件后,编写测试代码,观察日志是否按预期写入到指定的文件中。例如,创建一个简单的Java类,使用`logger.info()`或`...

    jsp网上投票系统myeclipse开发

    // Just puts "destroy" string in log // Put your code here } /** * The doPost method of the servlet. * * This method is called when a form has its tag value method equals to post. *...

    log4j日志文件的小资料(小小参考)

    Log4j是一款广泛使用的Java日志记录框架,它允许开发者在程序中方便地记录各种级别的日志信息,如ERROR、WARN、INFO、DEBUG等。在Web开发中,尤其是在使用MyEclipse这样的集成开发环境中,Log4j对于调试和追踪代码中...

    MyEclipse快捷键

    - `Alt+Shift+Q,L`:显示“Error Log”视图。 通过以上介绍的快捷键,开发者可以更加高效地利用MyEclipse进行软件开发。熟练掌握这些快捷键不仅可以提高编码速度,还能提升代码质量和维护性。希望这些内容能够帮助...

    tomcat控制台详细错误日志设置

    如果你的应用使用了log4j作为日志框架,那么你可以在`WEB-INF/classes`或者`lib`目录下放置`log4j.properties`或`log4j.xml`配置文件,来定制你的日志输出级别和格式。例如,你可以设置如下: ```xml <!...

    struts2+hibernate+spring+mysql+tomcat+log4j

    **Log4j**:Log4j是Java日志框架之一,它提供了灵活的日志记录功能,可以配置不同的日志级别,如DEBUG、INFO、WARN、ERROR等,帮助开发者调试和监控应用程序。通过配置文件,可以轻松改变日志输出的位置和格式。 **...

Global site tag (gtag.js) - Google Analytics