On 7/24/06, Ben Sommerville <[EMAIL PROTECTED]> wrote:
A final option may be to use a different JDK impl. E.g. I'm pretty sure that Jrockit (from bea) doesn't have a perm gen space & hence wont get the same problem (or at least might manifest it in a different way that is easier to diagnose). That's a pretty radical step tho, especially if your app is in production & has undergone a lot of testing in its current environment.
I've seen exactly the same issue with JRockit and unfortunately, nothing more detailed to help diagnosing the problem. In addition, in the latests versions of JRockit, they made their memory leak tool only available to JRockit licensed customers... And that far I've found sun's Jmap and Jhat much more powerful. Something in the redeployment is defenitly different with the JDK 1.6though. On windows, a redeployment is way faster than with previous versions. Thanks, Henri.
