| Summary: | Profiled application executed with redundant classpath | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Alexander N. Alexeev <analexee> | ||||
| Component: | TPTP | Assignee: | Eugene Chan <ewchan> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jkubasta, joerg.schaible, rjlorimer | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | housecleaned462 closed472 | ||||||
| Attachments: |
|
||||||
I just hit this on our application as well. My scenario is very similar to the newsgroup conversation that triggered this bug. I have a Java 1.4.2 application that uses log4j. When starting up as a Java Application to profile, the EMF libraries were being unintentionally loaded by the instance of Log4J in my classpath, at which point I received this error - capturing the error here for bots on the web: java.lang.UnsupportedClassVersionError: org/eclipse/emf/ecore/EObject (Unsupported major.minor version 49.0) I was unable to follow the workaround suggested here: http://dev.eclipse.org/newslists/news.eclipse.tptp/msg05286.html ...which involved duplicating the bootstrap classpath of TPTP in the bootstrap of my profile JVM (I may not have followed the instructions correctly), however I was able to get an XML trace via standalone profiling - which will provide a sufficient workaround for the short term. Hi Bing. I have transferred my bugs to you for triage. Thanks. If this Bugzilla is planed to be completed in 4.5, please add the plan keyword. Otherwise, please target to future. In addition, if this Bugzilla is committed to be completed in 4.5, please change the priority to P1. Hi Eugene, can you take a look at this. not containable in 4.5 As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. Since this defect is more than 2 years old, it may be no longer relevant. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this defect is resolved as WONTFIX. If this defect is still relevant and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. This defect had been resolved as WONTFIX for more than 1 month. Closing this on the reporter's behalf. Please re-open if you have further comment on this issue. Closed in TPTP 4.7.2. |
Created attachment 82416 [details] Test application prints recivied classpath Profile attached testcase application. It receives long classpath, most part of which isn't required (also for profiling). It can cause problems with incorrect class version loading which is hardly detectable.