Hello Richard,
Based on my experience everything depends from the archive size. I have
about 5 archives that have a size around 5 MB. My test executes with
each archive 20 actions like deploy/undeploy/redeploy and so on. If to
execute with these 5 archive that 100 actions totally, then with a big
probability appserver either hung up, for example will occupy 100% CPU,
or will crash. Early in a testing cycle I've opened bugs that describe
these issues, then eventually these bugs were closed. I let these
bugs be closed, because I think that it is not a very realistic case,
i.e. probably users will not do 1000 times deploy/undeploy and don't
restart appserver during this period of time. Without "big" archives
about 2000 such actions (deploy/undeploy/...) can be performed without
these issues. But also I saw that "big" archives (about 5 MB) can
kill appserver quickly with 64 bit JVM.
Thank you,
Elena
Richard Kolb wrote:
> Hi Cats
>
> Similar problem with EJB's
>
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11160
>
> regards
> Richard
>
>
> 2009/11/24 Richard Kolb <rjdkolb_at_gmail.com <mailto:rjdkolb_at_gmail.com>>
>
> Hi Cats
>
> When investigating a non heap memory leak I found a heap memory issue.
>
> I redeployed the 4k war 900 times and pop.
> *Can I beg someone for a unit test please please.*
>
> Actually unit tests to redeploy each sample 1000 times would be
> great. *cough*
>
> Heap issue:
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=11159
>
>
> regards
> Richard.
>
>