Home » Archived » Test and Performance Tools Platform (TPTP) » TPTP crashes eclipse help
| TPTP crashes eclipse help [message #56923] |
Thu, 09 March 2006 08:04  |
Eclipse User |
|
|
|
I verified this twice now (by adding/removing a link to the TPTP install
directory in eclipse's links subdirectory):
enabling TPTP causes eclipse's built-in help to fail.
To reproduce: just click Help => Help Contents.
The error message is:
Help can not be displayed. The embedded application server could not run
help web application. Check the log for details. [OK]
The corresponding entry in the log reads:
-----------------------------------
....
!ENTRY org.eclipse.tomcat 4 0 2006-03-09 14:03:20.436
!MESSAGE Exception occurred starting the embedded application server.
!STACK 0
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:532)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(L ogFactoryImpl.java:272)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java :414)
at org.apache.commons.digester.Digester.<init>(Digester.java:346)
at
org.apache.catalina.realm.MemoryRealm.getDigester(MemoryReal m.java:278)
at org.apache.catalina.realm.MemoryRealm.start(MemoryRealm.java :348)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.j ava:1173)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine .java:363)
at org.apache.catalina.startup.Embedded.addEngine(Embedded.java :464)
at
org.eclipse.tomcat.internal.TomcatAppServer.start(TomcatAppS erver.java:146)
at
org.eclipse.help.internal.appserver.AppserverPlugin.startWeb appServer(AppserverPlugin.java:143)
at
org.eclipse.help.internal.appserver.AppserverPlugin.getAppSe rver(AppserverPlugin.java:41)
at
org.eclipse.help.internal.appserver.WebappManager.start(Weba ppManager.java:58)
at
org.eclipse.help.internal.base.BaseHelpSystem.ensureWebappRu nning(BaseHelpSystem.java:246)
at
org.eclipse.help.internal.base.HelpDisplay.displayHelpURL(He lpDisplay.java:164)
at
org.eclipse.help.internal.base.HelpDisplay.displayHelp(HelpD isplay.java:54)
at
org.eclipse.help.ui.internal.DefaultHelpUI.displayHelp(Defau ltHelpUI.java:122)
at
org.eclipse.ui.internal.help.WorkbenchHelpSystem.displayHelp (WorkbenchHelpSystem.java:822)
at
org.eclipse.ui.internal.actions.HelpContentsAction$1.run(Hel pContentsAction.java:83)
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.ui.internal.actions.HelpContentsAction.run(HelpC ontentsAction.java:81)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:492 )
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:530)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:480)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:392)
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java (Compiled
Code))
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3287)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2907)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1899)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1863)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:417)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:106)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:99)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:374)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:416)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:525)
... 47 more
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:412)
... 48 more
-----------------------------------
Hints / ideas / work-arounds?
Michael
|
|
| | |
| Re: TPTP crashes eclipse help [message #57486 is a reply to message #57335] |
Fri, 10 March 2006 17:46  |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_0024_01C6449C.E7F18570
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Nope, I can't confirm this. It does NOT seem to depend on the JRE =
(alone).
I tried with 3 different JRE's (IBM 1.4.2, Sun 1.4.2, Sun 1.5.0) and it =
did not work with any of those.=20
I then re-installed an older eclipse (3.1.2) and with that it worked =
with ALL three JREs listed above.
From these few experiments I would rather conclude it's some eclipse =
version thing. To probe further I am right now re-installing a plain =
3.2.0M5a again and will try again from scratch and with ONLY TPTP and =
its prereqs installed and then adding misc. other plugins I am using and =
thereby hopefully being able to pinpoint the culprit. I'll keep you =
posted...
Michael
<Navid_Mehregani_nmehrega@ca.ibm.com> wrote in message =
news:dus8r3$b5h$1@utils.eclipse.org...
Hi Michael,=20
This is not a TPTP problem. I was actually having this problem as =
well. According to the Eclipse Project Release Notes this problem is =
caused by a conflict between libraries in org.eclipse.tomcat and JARS =
that are optionally installed in JRE, specifically in the jre/lib/ext =
directory. To fix the problem, either start Eclipse with a clean JDK =
install or make sure that the JRE used for running Eclipse doesn't =
contain any J2EE or Apache jars in the jre/lib/ext directory.=20
I experience this problem when I use the IBM JDK , but it's fine with =
Sun's JDK.=20
Navid Mehregani
------=_NextPart_000_0024_01C6449C.E7F18570
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Nope, I can't confirm this. It does NOT =
seem to=20
depend on the JRE (alone).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I tried with 3 different JRE's (IBM =
1.4.2, Sun=20
1.4.2, Sun 1.5.0) and it did not work with any of those. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I then re-installed an older =
eclipse (3.1.2)=20
and with that it worked with ALL three JREs listed above.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>From these few experiments I would =
rather=20
conclude it's some eclipse version thing. To probe further I am =
right=20
now re-installing a plain 3.2.0M5a again and will try again from =
scratch=20
and with ONLY TPTP and its prereqs installed and then adding misc. other =
plugins=20
I am using and thereby hopefully being able to pinpoint the =
culprit.=20
</FONT><FONT face=3DArial size=3D2>I'll keep you posted...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><<A=20
href=3D"mailto:Navid_Mehregani_nmehrega@ca.ibm.com">Navid_Mehregani_nmehr=
ega@ca.ibm.com</A>>=20
wrote in message <A=20
href=3D"news:dus8r3$b5h$1@utils.eclipse.org">news:dus8r3$b5h$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Hi Michael,</FONT> <BR><BR><FONT =
face=3Dsans-serif=20
size=3D2>This is not a TPTP problem. I was actually having =
this=20
problem as well. According to the </FONT><FONT =
size=3D3><TT>Eclipse Project=20
Release Notes</TT></FONT><FONT face=3Dsans-serif size=3D2> this problem =
is caused by=20
a conflict between libraries in org.eclipse.tomcat and JARS that are =
optionally=20
installed in JRE, specifically in the jre/lib/ext directory. To =
fix the=20
problem, either start Eclipse with a clean JDK install or make sure that =
the JRE=20
used for running Eclipse doesn't contain any J2EE or Apache jars in the=20
jre/lib/ext directory.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>I =
experience=20
this problem when I use the IBM JDK , but it's fine with Sun's =
JDK.</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>Navid =
Mehregani</FONT></BODY></HTML>
------=_NextPart_000_0024_01C6449C.E7F18570--
|
|
|
| Re: TPTP crashes eclipse help [message #57511 is a reply to message #57486] |
Fri, 10 March 2006 18:17 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
------=_NextPart_000_003A_01C644A1.2EC25930
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
As I already wrote: it's NOT the JRE!
I just installed another plain copy of eclipse 3.2.0M5 plus TPTP =
(tptp.runtime-TPTP-4.2.0-200602281515) and its prereqs =
(emf-sdo-SDK-2.1.0, xsd-SDK-2.1.0) onl and already that does not work. =
And that's with Sun JDK's...
On first search I would say the version conflict is between=20
eclipse's own =
....\eclipse\plugins\org.apache.ant_1.6.5\lib\ant-apache-log 4j.jar=20
and TPTP's =
....\eclipse\plugins\org.apache.jakarta_log4j_logging_1.2.8. v200602281515.=
jar
Michael
"Michael Moser" <mmo@zurich.ibm.com> wrote in message =
news:dusvm7$g5i$1@utils.eclipse.org...
Nope, I can't confirm this. It does NOT seem to depend on the JRE =
(alone).
I tried with 3 different JRE's (IBM 1.4.2, Sun 1.4.2, Sun 1.5.0) and it =
did not work with any of those.=20
I then re-installed an older eclipse (3.1.2) and with that it worked =
with ALL three JREs listed above.
From these few experiments I would rather conclude it's some eclipse =
version thing. To probe further I am right now re-installing a plain =
3.2.0M5a again and will try again from scratch and with ONLY TPTP and =
its prereqs installed and then adding misc. other plugins I am using and =
thereby hopefully being able to pinpoint the culprit. I'll keep you =
posted...
Michael
<Navid_Mehregani_nmehrega@ca.ibm.com> wrote in message =
news:dus8r3$b5h$1@utils.eclipse.org...
Hi Michael,=20
This is not a TPTP problem. I was actually having this problem as =
well. According to the Eclipse Project Release Notes this problem is =
caused by a conflict between libraries in org.eclipse.tomcat and JARS =
that are optionally installed in JRE, specifically in the jre/lib/ext =
directory. To fix the problem, either start Eclipse with a clean JDK =
install or make sure that the JRE used for running Eclipse doesn't =
contain any J2EE or Apache jars in the jre/lib/ext directory.=20
I experience this problem when I use the IBM JDK , but it's fine with =
Sun's JDK.=20
Navid Mehregani
------=_NextPart_000_003A_01C644A1.2EC25930
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>As I already wrote: </FONT><FONT =
face=3DArial=20
size=3D2>it's NOT the JRE!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I just installed another plain copy of =
eclipse=20
3.2.0M5 plus TPTP (tptp.runtime-TPTP-4.2.0-200602281515) and its prereqs =
(emf-sdo-SDK-2.1.0, xsd-SDK-2.1.0) onl and already that does not =
work.=20
</FONT><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>And=20
that's with Sun JDK's...</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV></FONT>
<DIV><FONT face=3DArial size=3D2>On first search I would say =
the version=20
conflict is between </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>eclipse's own </FONT><FONT =
face=3DArial=20
size=3D2> ...\eclipse\plugins\org.apache.ant_1.6.5\lib\ant-apache-log4 j.ja=
r=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>and </FONT><FONT face=3DArial =
size=3D2>TPTP's=20
....\eclipse\plugins\org.apache.jakarta_log4j_logging_1.2.8. v200602281515.=
jar</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>"Michael Moser" <<A=20
href=3D"mailto:mmo@zurich.ibm.com">mmo@zurich.ibm.com</A>> wrote in =
message <A=20
href=3D"news:dusvm7$g5i$1@utils.eclipse.org">news:dusvm7$g5i$1@utils.ecli=
pse.org</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>Nope, I can't confirm this. It does NOT =
seem to=20
depend on the JRE (alone).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I tried with 3 different JRE's (IBM =
1.4.2, Sun=20
1.4.2, Sun 1.5.0) and it did not work with any of those. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I then re-installed an older =
eclipse (3.1.2)=20
and with that it worked with ALL three JREs listed above.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>From these few experiments I would =
rather=20
conclude it's some eclipse version thing. To probe further I am =
right=20
now re-installing a plain 3.2.0M5a again and will try again from =
scratch=20
and with ONLY TPTP and its prereqs installed and then adding misc. other =
plugins=20
I am using and thereby hopefully being able to pinpoint the =
culprit.=20
</FONT><FONT face=3DArial size=3D2>I'll keep you posted...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><<A=20
href=3D"mailto:Navid_Mehregani_nmehrega@ca.ibm.com">Navid_Mehregani_nmehr=
ega@ca.ibm.com</A>>=20
wrote in message <A=20
href=3D"news:dus8r3$b5h$1@utils.eclipse.org">news:dus8r3$b5h$1@utils.ecli=
pse.org</A>...</DIV><BR><FONT=20
face=3Dsans-serif size=3D2>Hi Michael,</FONT> <BR><BR><FONT =
face=3Dsans-serif=20
size=3D2>This is not a TPTP problem. I was actually having =
this=20
problem as well. According to the </FONT><FONT =
size=3D3><TT>Eclipse Project=20
Release Notes</TT></FONT><FONT face=3Dsans-serif size=3D2> this problem =
is caused by=20
a conflict between libraries in org.eclipse.tomcat and JARS that are =
optionally=20
installed in JRE, specifically in the jre/lib/ext directory. To =
fix the=20
problem, either start Eclipse with a clean JDK install or make sure that =
the JRE=20
used for running Eclipse doesn't contain any J2EE or Apache jars in the=20
jre/lib/ext directory.</FONT> <BR><BR><FONT face=3Dsans-serif size=3D2>I =
experience=20
this problem when I use the IBM JDK , but it's fine with Sun's =
JDK.</FONT>=20
<BR><BR><FONT face=3Dsans-serif size=3D2>Navid Mehregani</FONT> =
</BODY></HTML>
------=_NextPart_000_003A_01C644A1.2EC25930--
|
|
|
| Re: TPTP crashes eclipse help [message #57690 is a reply to message #57511] |
Sun, 12 March 2006 19:06 |
| Eclipse User |
|
|
|
After responding to another message where the person was running Eclipse
3.2M5a with EMF/XSD/SDO 2.1, thinking those were the pre-reqs for TPTP
of 200602281515 (TPTP 4.2M5), I'm confused... where is this info coming
from? The info from the 200602281515 download page for TPTP says:
# Java runtime (JRE) or Java development kit (JDK) 1.4
# Eclipse SDK 3.2.0 M5a
# Eclipse Modeling Framework (EMF and XSD) SDK 2.2.0 M5
That's cut-and-pasted, with the newsreader changing the bullet to #.
Note that it is EMF/XSD 2.2.0 M5 ...
How come people keep saying they're running with 2.1.0 EMF/XSD? As I
said, I'm confused... and others appear to be as well!
--
RDS
Michael Moser wrote:
> As I already wrote: it's NOT the JRE!
>
> I just installed another plain copy of eclipse 3.2.0M5 plus TPTP
> (tptp.runtime-TPTP-4.2.0-200602281515) and its prereqs
> (emf-sdo-SDK-2.1.0, xsd-SDK-2.1.0) onl and already that does not work.
> And that's with Sun JDK's...
>
> On first search I would say the version conflict is between
> eclipse's own
> ...\eclipse\plugins\org.apache.ant_1.6.5\lib\ant-apache-log4 j.jar
> and TPTP's
> ...\eclipse\plugins\org.apache.jakarta_log4j_logging_1.2.8.v 200602281515.jar
>
> Michael
>
>
>
> "Michael Moser" <mmo@zurich.ibm.com <mailto:mmo@zurich.ibm.com>> wrote
> in message news:dusvm7$g5i$1@utils.eclipse.org...
> Nope, I can't confirm this. It does NOT seem to depend on the JRE (alone).
>
> I tried with 3 different JRE's (IBM 1.4.2, Sun 1.4.2, Sun 1.5.0) and it
> did not work with any of those.
> I then re-installed an older eclipse (3.1.2) and with that it worked
> with ALL three JREs listed above.
>
> From these few experiments I would rather conclude it's some eclipse
> version thing. To probe further I am right now re-installing a plain
> 3.2.0M5a again and will try again from scratch and with ONLY TPTP and
> its prereqs installed and then adding misc. other plugins I am using
> and thereby hopefully being able to pinpoint the culprit. I'll keep you
> posted...
>
> Michael
>
>
> <Navid_Mehregani_nmehrega@ca.ibm.com
> <mailto:Navid_Mehregani_nmehrega@ca.ibm.com>> wrote in message
> news:dus8r3$b5h$1@utils.eclipse.org...
>
> Hi Michael,
>
> This is not a TPTP problem. I was actually having this problem as
> well. According to the Eclipse Project Release Notes this problem is
> caused by a conflict between libraries in org.eclipse.tomcat and JARS
> that are optionally installed in JRE, specifically in the jre/lib/ext
> directory. To fix the problem, either start Eclipse with a clean JDK
> install or make sure that the JRE used for running Eclipse doesn't
> contain any J2EE or Apache jars in the jre/lib/ext directory.
>
> I experience this problem when I use the IBM JDK , but it's fine with
> Sun's JDK.
>
> Navid Mehregani
|
|
|
| Re: TPTP crashes eclipse help [message #57739 is a reply to message #57690] |
Mon, 13 March 2006 03:01 |
| Eclipse User |
|
|
|
Just a guess trying to recap how I came up with this mix:
Probably by working through this article
http://www.eclipse.org/articles/Article-TPTP-Profiling-Tool/ tptpProfilingArticle.html
but already having 3.2.0M5 installed and noting that there is also a
newer 4.2 available for that eclipse version, but not scrolling down far
enough on the download page to also read the prereq's section for that
TPTP version.
But also downloading the newer EMF/XSD/SDO 2.2.0M5 version doesn't fix
the problem...
Michael
"Randy D. Smith" <randy.d.smith@intel.com> wrote in message
news:dv2d5f$9c7$1@utils.eclipse.org...
> After responding to another message where the person was running
> Eclipse 3.2M5a with EMF/XSD/SDO 2.1, thinking those were the pre-reqs
> for TPTP of 200602281515 (TPTP 4.2M5), I'm confused... where is this
> info coming from? The info from the 200602281515 download page for
> TPTP says:
>
> # Java runtime (JRE) or Java development kit (JDK) 1.4
> # Eclipse SDK 3.2.0 M5a
> # Eclipse Modeling Framework (EMF and XSD) SDK 2.2.0 M5
>
> That's cut-and-pasted, with the newsreader changing the bullet to #.
> Note that it is EMF/XSD 2.2.0 M5 ...
>
> How come people keep saying they're running with 2.1.0 EMF/XSD? As I
> said, I'm confused... and others appear to be as well!
> --
> RDS
>
>
> Michael Moser wrote:
>> As I already wrote: it's NOT the JRE!
>> I just installed another plain copy of eclipse 3.2.0M5 plus TPTP
>> (tptp.runtime-TPTP-4.2.0-200602281515) and its prereqs
>> (emf-sdo-SDK-2.1.0, xsd-SDK-2.1.0) onl and already that does not
>> work. And that's with Sun JDK's...
>> On first search I would say the version conflict is between
>> eclipse's own
>> ...\eclipse\plugins\org.apache.ant_1.6.5\lib\ant-apache-log4 j.jar
>> and TPTP's
>> ...\eclipse\plugins\org.apache.jakarta_log4j_logging_1.2.8.v 200602281515.jar
>> Michael
>> "Michael Moser" <mmo@zurich.ibm.com <mailto:mmo@zurich.ibm.com>>
>> wrote in message news:dusvm7$g5i$1@utils.eclipse.org...
>> Nope, I can't confirm this. It does NOT seem to depend on the JRE
>> (alone).
>> I tried with 3 different JRE's (IBM 1.4.2, Sun 1.4.2, Sun 1.5.0) and
>> it did not work with any of those.
>> I then re-installed an older eclipse (3.1.2) and with that it worked
>> with ALL three JREs listed above.
>> From these few experiments I would rather conclude it's some eclipse
>> version thing. To probe further I am right now re-installing a plain
>> 3.2.0M5a again and will try again from scratch and with ONLY TPTP and
>> its prereqs installed and then adding misc. other plugins I am using
>> and thereby hopefully being able to pinpoint the culprit. I'll keep
>> you posted...
>> Michael
>> <Navid_Mehregani_nmehrega@ca.ibm.com
>> <mailto:Navid_Mehregani_nmehrega@ca.ibm.com>> wrote in message
>> news:dus8r3$b5h$1@utils.eclipse.org...
>>
>> Hi Michael,
>>
>> This is not a TPTP problem. I was actually having this problem as
>> well. According to the Eclipse Project Release Notes this problem is
>> caused by a conflict between libraries in org.eclipse.tomcat and JARS
>> that are optionally installed in JRE, specifically in the jre/lib/ext
>> directory. To fix the problem, either start Eclipse with a clean JDK
>> install or make sure that the JRE used for running Eclipse doesn't
>> contain any J2EE or Apache jars in the jre/lib/ext directory.
>>
>> I experience this problem when I use the IBM JDK , but it's fine with
>> Sun's JDK.
>>
>> Navid Mehregani
|
|
| | | | | | | | |
| Re: TPTP crashes eclipse help [message #66722 is a reply to message #56923] |
Fri, 14 April 2006 13:42 |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------030507050101000303010505
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
I have just spent the last few hours beating my head against the
proverbial wall, sure do will I had read this thread sooner :'( My
circumstances, however, are slightly different and may help to figure
out what the real underlying problem is.
The plugin we are developing depends on common-logging.jar. All works
fine in Eclipse 3.1.x, but in 3.2.M5a with TPTP 4..2.0 we experience the
reported exception. At first I figured it was a versioning problem with
the commons-logging shipped in org.apache.jakarta_commons_logging_1.0.3
so I replaced ours with the one shipped by TPTP. Guess what? It still
caused the exception. If I remove my plugin help works fine, if I
remove only commons-logging.jar from my plugin help works fine, but of
course my plugin is broken. Of point of interest we do *not* export this
jars packages in the Manifest, which I thought was supposed to give us
the control over exactly this type of problem
Has a bug report been opened on this yet? If so a pointer to it would be
appreciated.
Cheers,
Joel
Michael Moser wrote:
> I verified this twice now (by adding/removing a link to the TPTP
> install directory in eclipse's links subdirectory):
> enabling TPTP causes eclipse's built-in help to fail.
>
> To reproduce: just click Help => Help Contents.
>
> The error message is:
> Help can not be displayed. The embedded application server could not run
> help web application. Check the log for details. [OK]
>
> The corresponding entry in the log reads:
> -----------------------------------
> ...
> !ENTRY org.eclipse.tomcat 4 0 2006-03-09 14:03:20.436
> !MESSAGE Exception occurred starting the embedded application server.
> !STACK 0
> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JLogger does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:532)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(L ogFactoryImpl.java:272)
>
> at org.apache.commons.logging.LogFactory.getLog(LogFactory.java :414)
> at org.apache.commons.digester.Digester.<init>(Digester.java:346)
> at
> org.apache.catalina.realm.MemoryRealm.getDigester(MemoryReal m.java:278)
> at org.apache.catalina.realm.MemoryRealm.start(MemoryRealm.java :348)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.j ava:1173)
> at org.apache.catalina.core.StandardEngine.start(StandardEngine .java:363)
> at org.apache.catalina.startup.Embedded.addEngine(Embedded.java :464)
> at
> org.eclipse.tomcat.internal.TomcatAppServer.start(TomcatAppS erver.java:146)
>
> at
> org.eclipse.help.internal.appserver.AppserverPlugin.startWeb appServer(AppserverPlugin.java:143)
>
> at
> org.eclipse.help.internal.appserver.AppserverPlugin.getAppSe rver(AppserverPlugin.java:41)
>
> at
> org.eclipse.help.internal.appserver.WebappManager.start(Weba ppManager.java:58)
>
> at
> org.eclipse.help.internal.base.BaseHelpSystem.ensureWebappRu nning(BaseHelpSystem.java:246)
>
> at
> org.eclipse.help.internal.base.HelpDisplay.displayHelpURL(He lpDisplay.java:164)
>
> at
> org.eclipse.help.internal.base.HelpDisplay.displayHelp(HelpD isplay.java:54)
>
> at
> org.eclipse.help.ui.internal.DefaultHelpUI.displayHelp(Defau ltHelpUI.java:122)
>
> at
> org.eclipse.ui.internal.help.WorkbenchHelpSystem.displayHelp (WorkbenchHelpSystem.java:822)
>
> at
> org.eclipse.ui.internal.actions.HelpContentsAction$1.run(Hel pContentsAction.java:83)
>
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
> org.eclipse.ui.internal.actions.HelpContentsAction.run(HelpC ontentsAction.java:81)
>
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:492 )
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:530)
>
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:480)
>
> at
> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:392)
>
> at
> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java (Compiled
> Code))
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3287)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2907)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1899)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1863)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:417)
>
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:106)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:99)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:374)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:169)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:85)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:58)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:60)
>
> at java.lang.reflect.Method.invoke(Method.java:391)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
> Caused by: org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JLogger does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:416)
>
> at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:525)
>
> ... 47 more
> Caused by: org.apache.commons.logging.LogConfigurationException: Class
> org.apache.commons.logging.impl.Log4JLogger does not implement Log
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:412)
>
> ... 48 more
> -----------------------------------
>
> Hints / ideas / work-arounds?
>
> Michael
>
--------------030507050101000303010505
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi,<br>
<br>
I have just spent the last few hours beating my head against the
proverbial wall, sure do will I had read this thread sooner <span
class="moz-smiley-s15"><span> :'( </span></span> My circumstances,
however, are slightly different and may help to figure out what the
real underlying problem is.<br>
<br>
The plugin we are developing depends on common-logging.jar. All works
fine in Eclipse 3.1.x, but in 3.2.M5a with TPTP 4..2.0 we experience
the reported exception. At first I figured it was a versioning problem
with the commons-logging shipped in <font color="#3333ff">o</font><font
color="#3333ff">rg.apache.jakarta_commons_logging_1.0.3</font > so I
replaced ours with the one shipped by TPTP. Guess what? It still caused
the exception. If I remove my plugin help works fine, if I remove only
commons-logging.jar from my plugin help works fine, but of course my
plugin is broken. Of point of interest we do <b>not</b> export this
jars packages in the Manifest, which I thought was supposed to give us
the control over exactly this type of problem<br>
<br>
Has a bug report been opened on this yet? If so a pointer to it would
be appreciated.<br>
<br>
Cheers,<br>
Joel<br>
<br>
<br>
</font><br>
Michael Moser wrote:
<blockquote cite="middup968$r94$1@utils.eclipse.org" type="cite">I
verified this twice now (by adding/removing a link to the TPTP install
directory in eclipse's links subdirectory):
<br>
enabling TPTP causes eclipse's built-in help to fail.
<br>
<br>
To reproduce: just click Help => Help Contents.
<br>
<br>
The error message is:
<br>
Help can not be displayed. The embedded application server could not
run
<br>
help web application. Check the log for details. [OK]
<br>
<br>
The corresponding entry in the log reads:
<br>
-----------------------------------
<br>
....
<br>
!ENTRY org.eclipse.tomcat 4 0 2006-03-09 14:03:20.436
<br>
!MESSAGE Exception occurred starting the embedded application server.
<br>
!STACK 0
<br>
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
<br>
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:532)
<br>
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(L ogFactoryImpl.java:272)
<br>
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java :414)
<br>
at org.apache.commons.digester.Digester.<init>(Di gester.java:346)
<br>
at
org.apache.catalina.realm.MemoryRealm.getDigester(MemoryReal m.java:278)
<br>
at org.apache.catalina.realm.MemoryRealm.start(MemoryRealm.java :348)
<br>
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.j ava:1173)
<br>
at
org.apache.catalina.core.StandardEngine.start(StandardEngine .java:363)
<br>
at org.apache.catalina.startup.Embedded.addEngine(Embedded.java :464)
<br>
at
org.eclipse.tomcat.internal.TomcatAppServer.start(TomcatAppS erver.java:146)
<br>
at
org.eclipse.help.internal.appserver.AppserverPlugin.startWeb appServer(AppserverPlugin.java:143)
<br>
at
org.eclipse.help.internal.appserver.AppserverPlugin.getAppSe rver(AppserverPlugin.java:41)
<br>
at
org.eclipse.help.internal.appserver.WebappManager.start(Weba ppManager.java:58)
<br>
at
org.eclipse.help.internal.base.BaseHelpSystem.ensureWebappRu nning(BaseHelpSystem.java:246)
<br>
at
org.eclipse.help.internal.base.HelpDisplay.displayHelpURL(He lpDisplay.java:164)
<br>
at
org.eclipse.help.internal.base.HelpDisplay.displayHelp(HelpD isplay.java:54)
<br>
at
org.eclipse.help.ui.internal.DefaultHelpUI.displayHelp(Defau ltHelpUI.java:122)
<br>
at
org.eclipse.ui.internal.help.WorkbenchHelpSystem.displayHelp (WorkbenchHelpSystem.java:822)
<br>
at
org.eclipse.ui.internal.actions.HelpContentsAction$1.run(Hel pContentsAction.java:83)
<br>
at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
<br>
at
org.eclipse.ui.internal.actions.HelpContentsAction.run(HelpC ontentsAction.java:81)
<br>
at org.eclipse.jface.action.Action.runWithEvent(Action.java:492 )
<br>
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:530)
<br>
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:480)
<br>
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:392)
<br>
at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java (Compiled
Code))
<br>
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:925)
<br>
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3287)
<br>
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2907)
<br>
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1899)
<br>
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1863)
<br>
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:417)
<br>
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
<br>
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:106)
<br>
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:99)
<br>
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
<br>
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
<br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:374)
<br>
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:169)
<br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<br>
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:85)
<br>
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:58)
<br>
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:60)
<br>
at java.lang.reflect.Method.invoke(Method.java:391)
<br>
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:338 )
<br>
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
<br>
at org.eclipse.core.launcher.Main.run(Main.java:977)
<br>
at org.eclipse.core.launcher.Main.main(Main.java:952)
<br>
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
<br>
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:416)
<br>
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(L ogFactoryImpl.java:525)
<br>
.... 47 more
<br>
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
<br>
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstru ctor(LogFactoryImpl.java:412)
<br>
.... 48 more
<br>
-----------------------------------
<br>
<br>
Hints / ideas / work-arounds?
<br>
<br>
Michael
<br>
<br>
</blockquote>
</body>
</html>
--------------030507050101000303010505--
|
|
|
| Re: TPTP crashes eclipse help [message #66743 is a reply to message #66722] |
Fri, 14 April 2006 17:04 |
| Eclipse User |
|
|
|
Joel Rosi-Schwartz wrote:
> Hi,
>
> I have just spent the last few hours beating my head against the
> proverbial wall, sure do will I had read this thread sooner :'( My
> circumstances, however, are slightly different and may help to figure
> out what the real underlying problem is.
> ...
> Has a bug report been opened on this yet? If so a pointer to it would be
> appreciated.
All the dupes point to bugzilla_#132020 <
https://bugs.eclipse.org/bugs/show_bug.cgi?id=132020 > as "the
original", and it shows as fixed in 3.2M6.
--
RDS
Randy D. Smith randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)
|
|
|
Goto Forum:
Current Time: Tue Nov 04 09:24:16 EST 2025
Powered by FUDForum. Page generated in 0.07100 seconds |
Home