I\'ve got a Play (1.2.4) application that\'s working fine on my Windows 7 64bit dev machine.
I had a few crashes when I was running on Java 7.0 beta; this JavaVM cra
This is definitely a bug with Java due to Eclipse compiler.
There is a bug to track on play.lighthouse.
It does seem that CRUD classes exacerbate the issue, and low memory too; the issue will tend to disappear, and only come back for hot-compilation (modifying Java code without restarting), and even there not always.
On the other side, deploying in JBoss definitely brings to full crashes.
With little crud classes and lot of available memory the situation improves, so as a workaround when you really can't do anything else: reduce to the minimum the number of CRUD classes; using the @For
decorator again seems to worsen things.
Also, using Java 6 is much more stable - less memory sensitive - in particular with JBoss.
I'll mark this as solved because, beside the CRUD trick and the suggestion to use Java 6, there's nothing else that can be done at this level.
Just update JDK to latest Jdk 1.7 7u7 and problem will be solved , was facing the issue now resolved by udgrading jvm
I think your Classes needs to much space. See
PSPermGen total 40448K, used 40403K [0x000000067c400000, 0x000000067eb80000, x0000000686a00000)
object space 40448K, 99% used [0x000000067c400000,0x000000067eb74e08,0x000000067eb80000)
so I would recommend to increase the permsize and create an bug report at openjdk. Because I think a OutOfMemoryError should be thrown.
Here you can get more information about the permsize.