Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. go to Help -> Help Contents
2. get a page with "The document that you have requested is not available. The
link may be wrong or you not have the corresponding product feature installed."
instead of the Eclipse help.
Here's the tomcat output of from 'eclipse -consolelog':
17-Apr-07 5:18:50 AM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
17-Apr-07 5:18:51 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.20
17-Apr-07 5:18:51 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
17-Apr-07 5:18:52 AM org.apache.catalina.loader.WebappLoader start
INFO: Dual registration of jndi stream handler: URLStreamHandlerFactory already set
17-Apr-07 5:18:52 AM org.apache.catalina.loader.WebappLoader setClassPath
INFO: Unknown loader
17-Apr-07 5:18:54 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-127.0.0.1-60439
17-Apr-07 5:18:55 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-127.0.0.1-60439
That output is the same as what gets spit out on a working FC-6 so that won't
help with this problem.
I tested help with Sun's VM and it's working so this is a GCJ problem. I'll work
on narrowing down a test case.
Tom / Andrew / Gary,
Just thought I'd let you know that this is in the pipes. I'll let you know when
I've narrowed it down a little.
You say here that "output is the same as what gets spit out on a working FC-6".
I take it, then, that this bug is not an F7 regression, and has been around for
some considerable time. Is this correct?
Sorry, I wasn't clear there. What I meant to say was that text output from
-consolelog is the same as FC-6 so that doesn't help debug the problem. This is
in fact a Fedora 7 regression.
OK, I'm looking now.
This is because Eclipse needs MX4J. Try this fix:
sudo ln -sf /usr/share/java/mx4j/mx4j.jar /usr/share/java/gcj-endorsed
That fixes the problem, thanks!
In what sense does it need it? Does it specifically require MX4J features, or
does it just not work with libgcj's javax.management?
Oops, never mind, I just saw
Created attachment 154051 [details]
Patch for Classpath
I have tested this bug with libgcj HEAD and it fixes the problem.
Patch committed to redhat/gcc-4_1-branch, awaiting respin.
To Ben Konrath
A new gcc build is at
Please try it. Please close this Bugzilla entry if the bug is now fixed.
Yep, the bug is fixed with gcc-4.1.2-12.