qarks.com

[simonInOz]

Hi - JLeak looks interesting.
But I can't seem to make it function properly (Windows XP).
The log says

[spampete]

Hello Simon

can you make another test using http://www.qarks.com/jleak/jleak.jar ?

let me know if it helps.

Pierre

[simonInOz]

Hi Pierre,

I tried the new jar, with the same result. Just to be sure it was not something silly like spaces in file paths, I made sure the file paths were clear of spaces, moving Eclipse to c:\eclipse and the workspace to c:\workspace
This was running inside Eclipse (clean install of current version as of yesterday). Java 1.6.0_05

Annoying - it looks like some weird security problem.

The JLeak box pops up nicely, listing 4 classes I do indeed want to track, but does not actually work of course, unfortunately.

Any ideas? (I tried removing JMX to see if that was it, but no go - see logs below).

Simon (in Sydney where it is surprisingly cold and windy)

[spampete]

I have updated the test jar, can you have another try with http://www.qarks.com/jleak/jleak.jar ?

It contains a fix which I never had to use until now, but which can solve the ClassNotFoundException issue you are experiencing. This fix is non deterministic since it relies on the fact the given class loader used to instantiate your classes extends URLClassLoader, and you do not necesarily own the class loader...

If it does not help, I would suggest that you isolate the class instantiation which fails, SymmetricCipherUtil, and create the most simple eclipse project possible showing the issue, that you could send me over by mail so I can try debugging.

Pierre

[spampete]

So, just to let people know, since we ended up fixing this issue by email..

the ClassNotFoundException has indeed been fixed through adding the jleak archive to all the application class loaders involved. The fix is not fully deterministic since all class loaders do not necessarily extend URLClassLoader nor use a parent class loader extending it.

At least, it fixed Simon's issue, but then another one I cannot reproduce showed up on Simon's environment, with a strange LinkageError when opening the 2nd window showing where the instance have been created.

The release 1.0.2 fixes issues on serialized classes which used to generate unmarshalling exceptions due to incompatible serialVersionUID. Most of the issue is fixed, but some classes on my test bench still produce the issue, so not fully fixed. An exclude list allows filtering those classes, but this is just a workaround. If anyone has a clue on this one, just let us know !!

JLeak is not as perfect as commercial memory leak detectors, but remember it is free. I hope it can also be considered as a good example for developers who would like working with javassist.

cheers

[spampete]

ok, issue with the few classes which still had unmarshalling exceptions is fixed with a small patch within javassist.

If you are interested in the topic, please go to http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146712

cheers