Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Memory Analyzer (MAT) » Namespace reporting is not ebavled
Namespace reporting is not ebavled [message #2685] Sun, 24 August 2008 12:06 Go to next message
barak is currently offline barakFriend
Messages: 5
Registered: July 2009
Junior Member
Hello all,

I'm trying to hunt some leak using mat. I've generated an heap dump using
jmap. The dumo loaded by mat, but when clicking on Leak Suspects, an
exception is raised: java.io.IOException parser configuration problem:
namespace reporting is not enabled.

What should I configure in order to make the Leak suspects report working?

Thanks,

Barak.
Re: Namespace reporting is not ebavled [message #3095 is a reply to message #2685] Mon, 25 August 2008 10:57 Go to previous messageGo to next message
Andreas Buchen is currently offline Andreas BuchenFriend
Messages: 113
Registered: July 2009
Senior Member
Hi Barak,

this sounds like the saxon parser...

> exception is raised: java.io.IOException parser configuration problem:
> namespace reporting is not enabled.

Can you provide the full stack trace (Window -> Show error Log)? Also, can
you tell me a little bit more about your setup (standalone vs. embedded
into IDE)? And which JDK you are using.


If you want, create a bug in bugzilla. These allows us to track the
problem more easily:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=MAT


Thanks,

Andreas.
Re: Namespace reporting is not enabled [message #3120 is a reply to message #3095] Mon, 25 August 2008 11:22 Go to previous messageGo to next message
barak is currently offline barakFriend
Messages: 5
Registered: July 2009
Junior Member
Hi,

Thanks for helping, and sorry for the typos in the previous post...

So, I download the standelone Eclipse Memory Analyzer from
www.eclipse.org. I'm running Windows XP, professional edition, Java
version is:
java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02-b06)
Java HotSpot(TM) Client VM (build 1.6.0_02-b06, mixed mode).

The dump was created on linux box (Centos5, same jdk), using jmap.

Here is the stack:

eclipse.buildId=unknown
java.version=1.6.0_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
Command-line arguments: -os win32 -ws win32 -arch x86


Error
Mon Aug 25 14:12:14 IDT 2008
java.io.IOException: Parser configuration problem: namespace reporting is
not enabled

The other 2 frames in the stack (somehow I cant copy them) show exactly
the same: Parser configuration problem: namespace reporting is not enabled.

Thanks for any help, I'll try to open the bug soon.

Barak.
Re: Namespace reporting is not enabled [message #3153 is a reply to message #3120] Mon, 25 August 2008 16:04 Go to previous messageGo to next message
Andreas Buchen is currently offline Andreas BuchenFriend
Messages: 113
Registered: July 2009
Senior Member
Barak wrote:

> I'm running Windows XP, professional edition, Java
> version is:
> java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b06)
> Java HotSpot(TM) Client VM (build 1.6.0_02-b06, mixed mode).

I was able to reproduce the problem, if (and only if) I configure my
installation to use the SAXON (http://saxon.sourceforge.net/) XSLT
Processor.
I will do some more tests and then check in the changes.


So, with the next build, this should not happen. But maybe we can get your
current installation running: It's unclear where exactly the configuration
to use SAXON is picked up. Do you have an idea? (I had to specifically
say:
-Djavax.xml.transform.TransformerFactory=net.sf.saxon.Transf ormerFactoryImpl)

Maybe specify to run a particular vm, like:

MemoryAnalyzer.exe -vm <path/to/vm/bin/>

And then use a clean Jdk 1.6 (you have update 02, maybe update 07).

Let me know if that works for you! Thanks.

Andreas.
Re: Namespace reporting is not enabled [message #3256 is a reply to message #3153] Tue, 26 August 2008 09:27 Go to previous messageGo to next message
barak is currently offline barakFriend
Messages: 5
Registered: July 2009
Junior Member
Hi,

I'm really waiting the next build :-)

Running MemoryAnalyzer.exe -vm <path/to/vm/bin/> yields the same rusults.
But, expolring the jdk installation, I've discovered an endoresed folder
/path/to/jdk/lib/endorsed which contains saxon8-*.jar files, I guess this
is solves the mystery. These jars needed for our product developement, so
I can't remove them for good :-). I did remove this folder, restart mat,
and the same good old exception raised :-(.

I'll be glad for further help. Can you tell me when the next build will be
available?

Thanks,

Barak.
Re: Namespace reporting is not enabled [message #3291 is a reply to message #3256] Tue, 26 August 2008 12:40 Go to previous messageGo to next message
Andreas Buchen is currently offline Andreas BuchenFriend
Messages: 113
Registered: July 2009
Senior Member
Barak, drop me an email at andreas dot buchen at sap dot com. Let me know
the OS version you need. I will provide you one.
Re: Namespace reporting is not enabled [message #3525 is a reply to message #3153] Wed, 27 August 2008 15:47 Go to previous message
Andreas Buchen is currently offline Andreas BuchenFriend
Messages: 113
Registered: July 2009
Senior Member
For those interested in the technical details. The problem was that the
SAXON transformer is a little bit more accurate as to what it expects. At
one point during the report generation, a XML document was created.
Somehow along those lines:

SAXTransformerFactory tf = (SAXTransformerFactory)
SAXTransformerFactory.newInstance();
TransformerHandler handler = tf.newTransformerHandler();
[...]
handler.startDocument();
[...]
AttributesImpl atts = new AttributesImpl();
[...]
handler.startElement("", "", "part", attrib);

The last line needed change: I added URI and localName.

handler.startElement("http://www.eclipse.org/mat/report/", "part", "part",
attrib);

The relevant diff is this one:

http://dev.eclipse.org/viewcvs/index.cgi/trunk/plugins/org.e clipse.mat.report/src/org/eclipse/mat/report/internal/Result Renderer.java?root=Technology_MAT&r1=107&r2=117
Previous Topic:Error running reports on Linux
Next Topic:Any known issues with analyzing huge heap dumps?
Goto Forum:
  


Current Time: Wed Nov 26 04:45:48 GMT 2014

Powered by FUDForum. Page generated in 0.01921 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software