Admin: Ports
From Resin 3.0
(Difference between revisions)
| Line 19: | Line 19: | ||
; Keepalive Comet | ; Keepalive Comet | ||
: The number of Comet/Async connections waiting for the next data from the application | : The number of Comet/Async connections waiting for the next data from the application | ||
| + | |||
| + | == Troubleshooting == | ||
| + | |||
| + | Typically, this table will is used to check the expected load against the current load. If you see 1000 threads when the server is | ||
| + | lightly loaded, there is a likely problem. If you see 0 idle threads, the server is having trouble keeping up. | ||
Latest revision as of 21:58, 27 September 2010
The TCP Ports table shows the statistics for each port that Resin is listening to.
- Status
- Reports the current connectivity of the port. ACTIVE, WARMUP and FAIL are the main states
- Threads-Active
- The current number of threads allocated to this port that are actively processing a request
- Threads-Idle
- The number of idle threads waiting to accept a new request to this port
- Threads-Total
- The total number of threads, the sum of the idle and active
- Keepalive-Total
- The number of open connections in a keepalive state
- Keepalive-Thread
- The number of keepalives using a dedicated thread to wait for the next data
- Keepalive-Non-Block
- The number of keepalives using nonblocking I/O without a thread to wait for the next data
- Keepalive Comet
- The number of Comet/Async connections waiting for the next data from the application
[edit] Troubleshooting
Typically, this table will is used to check the expected load against the current load. If you see 1000 threads when the server is lightly loaded, there is a likely problem. If you see 0 idle threads, the server is having trouble keeping up.
