[jboss-jira] [JBoss JIRA] Commented: (JBAS-5325) Out of Memory error: Cannot start new thread. SpyJMSException
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Wed Mar 19 03:47:50 EDT 2008
[ http://jira.jboss.com/jira/browse/JBAS-5325?page=comments#action_12403536 ]
jaikiran pai commented on JBAS-5325:
------------------------------------
Aneesh,
Let's continue this discussion in the user forums, where you already have started a topic http://www.jboss.com/index.html?module=bb&op=viewtopic&t=132103
> Out of Memory error: Cannot start new thread. SpyJMSException
> -------------------------------------------------------------
>
> Key: JBAS-5325
> URL: http://jira.jboss.com/jira/browse/JBAS-5325
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossAS-4.0.2RC1
> Environment: Windows, jboss 4.0.2
> Reporter: aneesh vasanthan
> Priority: Critical
>
> Hi ,
> we are using jboss4.0.2 as our application server. we are facing a major problem in jms connection. It happens very frequently. After a restart will be fine for sometime n again it crashes.The exception trace is as shown below. expecting ur eteemed reply.
> Application server: jboss 4.0.2
> Application deployed in : jboss\server\default
> 2008-03-18 15:03:48,328 DEBUG [org.apache.coyote.tomcat5.CoyoteAdapter] Requested cookie session id is 639091685F164A589266650426F9B40F
> 2008-03-18 15:14:02,234 DEBUG [org.apache.coyote.tomcat5.CoyoteAdapter] Requested cookie session id is 639091685F164A589266650426F9B40F
> 2008-03-18 19:22:29,234 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Exiting on unexpected error in read task; - nested throwable: (java.lang.reflect.UndeclaredThrowableException)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:147)
> at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:398)
> at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:342)
> at java.lang.Thread.run(Thread.java:536)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> ... 4 more
> Caused by: java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start(Native Method)
> at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.addThread(PooledExecutor.java:520)
> at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:880)
> at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:296)
> ... 1 more
> 2008-03-18 19:27:29,234 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Thread.java:536)
> Caused by: java.io.IOException: ping timeout.
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
> ... 2 more
> 2008-03-18 19:32:29,250 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Thread.java:536)
> Caused by: java.io.IOException: ping timeout.
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
> ... 2 more
> 2008-03-18 19:37:29,265 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Thread.java:536)
> Caused by: java.io.IOException: ping timeout.
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
> ... 2 more
> 2008-03-18 19:42:29,281 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Thread.java:536)
> Caused by: java.io.IOException: ping timeout.
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
> ... 2 more
> 2008-03-18 19:47:29,296 WARN [org.jboss.mq.Connection] Connection failure:
> org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
> at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
> at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
> at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
> at java.lang.Thread.run(Thread.java:536)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list