Bugzilla – Full Text Bug Listing
| Summary: | Unrecoverable error while profiling application plug-ins that use Log4j | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Robert Enyedi <renyedi> | ||||
| Component: | TPTP | Assignee: | Stanislav Polevic <stanislav.v.polevic> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | analexee, jkubasta | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | closed460 | ||||||
| Attachments: |
|
||||||
I tried to reproduce it with 4.4.1-200709060100 build in clean workspace and failed. It is being profiled fine and it seems to be a misconfiguration problem... Could you create temp workspace and try to profile it there with the latest build? What does you lib directory contain? Did you change classpath for profiling? I tested this with the latest candidate build (TPTP-4.4.1-200709101254) and the problem is fixed. Thanks for checking on this. Keep up the good work! Please change the target to the 4.5 iteration when this Bugzilla was resolved. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |
Created attachment 77112 [details] The plugin of TptpTestApplication Build ID: I20070625-1500 Steps To Reproduce: I'm trying to profile an Eclipse command line application plug-in that uses Log4j for logging. I encountered the following issue first in a larger application but I narrowed it down to a small plug-in (see the attachment). The attached plug-in does the following: - extends the org.eclipse.core.runtime.applications extension point and provides an application implementation (tptptestplugin.TptpTestApplication class); - declares a dependency to the org.apache.log4j plug-in (the results are also the same if the log4j JAR is bundled inside the plug-in); - the application implementation instantiates a Log4j logger and tries to log a message. The application executes as expected. However, when trying to profile it from the IDE using the Profile Dialog (with the memory or processor collector from the JDK 1.5+ group), the following stack trace is dumped: log4j:ERROR Could not instantiate class [org.eclipse.hyades.logging.log4j.XmlLayout]. java.lang.ClassNotFoundException: org.eclipse.hyades.logging.log4j.XmlLayout at java.lang.ClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:429) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at org.apache.log4j.helpers.Loader.loadClass(Loader.java:178) at org.apache.log4j.helpers.OptionConverter.instantiateByClassName(OptionConverter.java:317) at org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConverter.java:120) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:641) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) at org.apache.log4j.LogManager.<clinit>(LogManager.java:122) at org.apache.log4j.Logger.getLogger(Logger.java:117) at tptptestplugin.TptpTestApplication.<clinit>(TptpTestApplication.java:17) Am I doing something wrong here or is this really a bug? More information: Execution environment: - Eclipse 3.3 - TPTP 4.4 (latest from the Europa discovery site) - both JDK 1.6.0_02 and JDK 1.5.0_12