uil2.SocketManager -> exiting on unexpected error
jschanz Nov 16, 2004 5:34 AMHI folks,
i'm running here a installation of jboss 4.0.0. After a while the server runs into an ouf of memory error.
2004-11-16 11:08:45,074 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin ReadTask.run
2004-11-16 11:08:45,074 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin WriteTask.run
2004-11-16 11:08:45,074 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectOutputStream
2004-11-16 11:08:45,074 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created ObjectInputStream
2004-11-16 11:08:45,075 DEBUG [org.jboss.mq.il.uil2.SocketManager] Exiting on unexpected error in read task
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)
at java.lang.Thread.run(Thread.java:534)
2004-11-16 11:08:45,075 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on unexpected error in read task
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)
at java.lang.Thread.run(Thread.java:534)
2004-11-16 11:08:45,075 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
2004-11-16 11:08:45,076 DEBUG [org.jboss.mq.il.uil2.SocketManager] End WriteTask.run
2004-11-16 11:12:57,870 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2004-11-16 11:12:57,870 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,880 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2004-11-16 11:20:27,880 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,884 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,887 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,890 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,893 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,896 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
2004-11-16 11:20:27,899 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=jboss2, password=--hidden--}
With JBoss 3.2.5 my client application couldn't reconnect to the jms queue. With 4.0.0 it seems that it works ...
The following parameters are set in run.conf:
MAX_FD="maximum"
JAVA_OPTS="-server -Xms128m -Xmx256m"
The base system is SuSE Linux Enterprise Server.
Is this problem a server or a client problem?
Thanks,
Jens