Hi,
I do some stress tests and memory leak detector shows that number of
_javassist_ instances is growing very fast. With this simple use case:
@SessionScoped @Named public class SampleBean {}
and in JSF page:
<h:outputText value="#{sampleBean}" />
<h:commandButton value="submit" />
With simulated 30 concurrent users (jmeter) and few minutes of running
java heap contains thousands instances SampleBean_javasssist_. After one
hour it is over one milion. First I thought that this is memory leak in
javassist as discussed id this mail thread but I use
javassist-3.12.1.GA.jar
Any ideas?
Thanks,
Martin Kočí
Gurkan Erdogdu píše v Po 28. 06. 2010 v 22:45 -0700:
> Hello Mark;
>
> What is the release of alpha-1? I think we were little late :)
>
>
> Thanks;
>
> --Gurkan
>
>
> ________________________________
> From: Mark Struberg <[email protected]>
> To: [email protected]
> Sent: Wed, June 23, 2010 5:02:34 PM
> Subject: [DISCUSSION] javassist-3.12
>
> Hoi!
>
> Since javassist-3.11 has quite remarkable mem leaks, we should use
> javassist-3.12 for our RC1 (or -alpha-1) release.
>
> The problem is that javassist-3.12 is still not uploaded to maven.central.
> Pete and Andrew Dinn are working on that but it will most probably take a few
> further weeks since Pete is not available atm (JBoss world, etc).
>
> The release is available on the public jboss edge maven repo:
>
> http://repository.jboss.org/maven2-brew
>
> Wdyt, should we use this repo or should we continue delivering with
> javassist-3.11 for now and upgrade to 3.12 later?
>
> We can also write in our README that we know about the mem leaks and that
> people should upgrade to 3.12 theirselfs if needed.
>
> LieGrue,
> strub
>
