Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0004765 [Resin] block always 09-16-11 02:52 10-04-11 16:07
Reporter apleshi View Status public  
Assigned To ferg
Priority normal Resolution fixed  
Status closed   Product Version 4.0.22
Summary 0004765: ThreadPool full, same as 0004683
Description [11-09-15 06:27:00.838] {resin-port-null:8080} WarningService: java.lang.IllegalStateException: Thread pool full
[11-09-15 06:27:00.838] {resin-port-null:8080} java.lang.IllegalStateException: Thread pool full
                                                at com.caucho.env.thread.ThreadPool.scheduleImpl(
                                                at com.caucho.env.thread.ThreadPool.start(
                                                at com.caucho.env.thread.AbstractThreadLauncher.startConnection(AbstractThreadLauncher
                                                at com.caucho.env.thread.AbstractThreadLauncher.runTask(
                                                at com.caucho.env.thread.ResinThread.runTasks(

Our current thread pool settings are:
Additional Information
Attached Files  jvm-default.log [^] (106,075 bytes) 09-16-11 02:52

- Relationships

- Notes
09-16-11 03:06

we have three servers running resin as web service, I send request from http_load and then all three servers run out of thread the same time.
09-16-11 14:20

Take a look at your line 62.

From the thread dump, there are a large number of threads writing data to something like System.out or System.err.
09-18-11 18:57

yes, there is System.out writing something to file, and at that time we run out of harddisk, is this the reason?
10-04-11 15:56

Yes, that's very possible.

In a production system, System.out should be very limited. Normally, you would want to use java.util.logging for that kind of information and use the "fine" level, so it's not normally getting logged.

I'll check the logging routines to see if they should handle out-of-disk issues better, but this doesn't directly look like a Resin bug.
10-04-11 16:07

I'm changing the flushing to reduce contention, which should help this case a bit, but the main change should be to reduce the System.out logging and use a finer java.util.logging level instead.

- Issue History
Date Modified Username Field Change
09-16-11 02:52 apleshi New Issue
09-16-11 02:52 apleshi File Added: jvm-default.log
09-16-11 03:06 apleshi Note Added: 0005508
09-16-11 14:20 ferg Note Added: 0005510
09-18-11 18:57 apleshi Note Added: 0005513
09-23-11 01:11 amukas Issue Monitored: amukas
10-04-11 15:56 ferg Note Added: 0005538
10-04-11 16:07 ferg Note Added: 0005539
10-04-11 16:07 ferg Assigned To  => ferg
10-04-11 16:07 ferg Status new => closed
10-04-11 16:07 ferg Resolution open => fixed
10-04-11 16:07 ferg Fixed in Version  => 4.0.24

Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
40 total queries executed.
31 unique queries executed.
Powered by Mantis Bugtracker