I am using atmosphere runtime version 0.6.1 in my application running on JBoss-6.0.0. The application was running fine for the last 3 months, until last week, when it started giving the OutOfMemory error.
The first two times, it came at the gap of 2 days. Today, I faced this issue thrice. I even restarted the server twice, but again no luck.
The stacktrace is :
at java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(Unknown Source) [:1.6.0_24]at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source) [:1.6.0_24]at java.util.concurrent.AbstractExecutorService.submit(Unknown Source) [:1.6.0_24]at org.atmosphere.cpr.DefaultBroadcaster$1.run(DefaultBroadcaster.java:211) [:0.6.1]at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [:1.6.0_24]at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [:1.6.0_24]at java.util.concurrent.FutureTask.run(Unknown Source) [:1.6.0_24]at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [:1.6.0_24]at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.6.0_24]
The machine has a 6GB RAM and I have provided the following settings to JBOSS : -XX:MaxPermSize=512M -Xms512m -Xmx1024m
Please do help me out on this.
can you get a thread dump when the error occur? I suspect there is too many Broadcaster which aren't getting garbage collected. Upgrading to a newer version of Atmosphere may solve the issue as well.
Thanks and sorry for the delay.
On 11-09-14 7:08 AM, Jacob Daniel wrote:
|Free forum by Nabble||Edit this page|