[jboss-dev-forums] [Design of EJB 3.0] - Re: Classloading problem in proxy factories

[ALRubinger]

Hard to say.

The new JAR attached to the JIRA definitely cleans up the held reference in the ObjectOutputStream, as verified by Profiling the heap.

However, I can't nail down the cause of the transient failure, which suggests that either the test isn't foolproof (though t looks pretty well-written - there's lots of GC requests followed by memory flooding to push out soft references), or that the reference isn't getting cleared immediately (is there some lag in place)?

I also tried running the test on my Win32 partition using JBossProfiler, which can force a GC via its JMVTIInterface.  However, this resulted in lots of:

[JVMTIInterface] 4069000 references received

...followed by OutOfMemoryErrors.

Long story short, I'd feel better about a tag if there were no transient failures.  Is there a chance that "clear" on the OOS isn't getting called upon return of the InvocationResponse, or does it wait a bit?  Maybe there's a race between that clear and the client returning, triggering the test to check for cleared CL?

S,
ALR

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173530#4173530

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173530