0004683: ThreadPool full

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004683

[Resin]

minor

always

07-25-11 12:12

07-28-11 16:47

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

4.0.20

Summary

0004683: ThreadPool full

Description

(rep by Amir Langer)

java.lang.IllegalStateException: Thread pool full
    at com.caucho.env.thread.ThreadPool.scheduleImpl(ThreadPool.java:598)
    at com.caucho.env.thread.ThreadPool.start(ThreadPool.java:513)
    at com.caucho.network.listen.TcpSocketLink.requestAccept(TcpSocketLink.java:635)
    at com.caucho.network.listen.SocketLinkThreadLauncher.launchChildThread(SocketLinkThreadLauncher.java:77)
    at com.caucho.env.thread.AbstractThreadLauncher.startConnection(AbstractThreadLauncher.java:404)
    at com.caucho.env.thread.AbstractThreadLauncher.runTask(AbstractThreadLauncher.java:441)
    at com.caucho.env.thread.AbstractTaskWorker.run(AbstractTaskWorker.java:160)
    at com.caucho.env.thread.ResinThread.runTasks(ResinThread.java:164)
    at com.caucho.env.thread.ResinThread.run(ResinThread.java:130)

This exception is then repeated continuously and resin then is basically just busy generating exceptions.

It is happening in our continuous integration env. and the usage in both cases is identical.

We tried various different thead pool settings

Our current thread pool settings are:

            <thread-max>1024</thread-max>
            <thread-idle-max>256</thread-idle-max>
            <thread-idle-min>32</thread-idle-min>

and we tried to play with the numbers a bit but none of the changes seemed to make a difference to the difference in behaviour.

For some reason 4.0.20 uses all the threads and blows up while 4.0.19-snapshot-2 will happily work even with a thread-max of 512.

Additional Information

"http://*:9090-66968" [^] daemon prio=10 tid=0x0000000053c3d000 nid=0x6add runnable [0x0000000043285000]
   java.lang.Thread.State: RUNNABLE
    at com.caucho.vfs.JniSocketImpl.readNative(Native Method)
    at com.caucho.vfs.JniSocketImpl.read(JniSocketImpl.java:380)
    - locked <0x0000000720d070b0> (a java.lang.Object)
    at com.caucho.vfs.JniStream.readTimeout(JniStream.java:100)
    at com.caucho.vfs.ReadStream.fillWithTimeout(ReadStream.java:1135)
    at com.caucho.network.listen.TcpSocketLink.threadKeepalive(TcpSocketLink.java:1283)
    at com.caucho.network.listen.TcpSocketLink.processKeepalive(TcpSocketLink.java:1266)
    at com.caucho.network.listen.TcpSocketLink.handleRequestsImpl(TcpSocketLink.java:1124)
    at com.caucho.network.listen.TcpSocketLink.handleRequests(TcpSocketLink.java:1055)
    at com.caucho.network.listen.TcpSocketLink.handleAcceptTask(TcpSocketLink.java:903)
    at com.caucho.network.listen.AcceptTask.doTask(AcceptTask.java:74)
    at com.caucho.network.listen.ConnectionTask.runThread(ConnectionTask.java:97)
    at com.caucho.network.listen.ConnectionTask.run(ConnectionTask.java:80)
    at com.caucho.network.listen.AcceptTask.run(AcceptTask.java:59)
    at com.caucho.env.thread.ResinThread.runTasks(ResinThread.java:164)
    at com.caucho.env.thread.ResinThread.run(ResinThread.java:130)

Attached Files

Relationships

Notes
(0005408) ferg 07-28-11 16:47	network/0230

Issue History
Date Modified	Username	Field	Change
07-25-11 12:12	ferg	New Issue
07-28-11 16:47	ferg	Note Added: 0005408
07-28-11 16:47	ferg	Assigned To	=> ferg
07-28-11 16:47	ferg	Status	new => closed
07-28-11 16:47	ferg	Resolution	open => fixed
07-28-11 16:47	ferg	Fixed in Version	=> 4.0.21
07-28-11 16:47	ferg	Additional Information Updated
09-16-11 02:50	apleshi	Issue Monitored: apleshi

Mantis 1.0.0rc3[^]

31 total queries executed.
26 unique queries executed.