diff --git a/defaults/yacy.init b/defaults/yacy.init
index d9d2c2007..ad819f6ca 100644
--- a/defaults/yacy.init
+++ b/defaults/yacy.init
@@ -225,10 +225,10 @@ bootstrapLoadTimeout = 20000
# milliseconds
clientTimeout = 10000
-# maximal number of httpd sessions
-# a client may open several connections at once, and the httpdMaxBusySessions value sets
-# a limit on the number of concurrent connections
-httpdMaxBusySessions = 200
+# maximum number of concurrently active incoming HTTP requests
+# remote requests above this limit receive HTTP 503; local requests are exempt
+# the historical httpdMaxBusySessions key name is retained for configuration compatibility
+httpdMaxBusySessions = 200
# maximum number of simultaneously open outgoing HTTP connections in the general pool (net.yacy.cora.protocol.http.HTTPClient)
http.outgoing.pool.general.maxTotal = 200
diff --git a/help/Connections_p.md b/help/Connections_p.md
index b965f1841..8253576fb 100644
--- a/help/Connections_p.md
+++ b/help/Connections_p.md
@@ -1,24 +1,25 @@
---
page: htroot/Connections_p.html
help: help/Connections_p.md
-title: Server Connection Tracking
+title: Connection and Request Tracking
package: monitoring-performance
access: admin
kind: admin-page
backend_java: source/net/yacy/htroot/Connections_p.java
---
-# Server Connection Tracking
+# Connection and Request Tracking
## Purpose
-Server Connection Tracking shows open and recent connections.
+Connection and Request Tracking shows active incoming HTTP requests separately from active outgoing client connections.
-Use it when requests appear stuck, slow, or unexpectedly numerous.
+Use it when requests appear stuck, slow, or unexpectedly numerous, or when outgoing HTTP activity needs inspection.
## What You Can Do Here
-- Server Connection Tracking shows open and recent connections.
+- Incoming HTTP Requests contains one row per request currently executing, including concurrent requests sharing one keep-alive connection.
+- Outgoing Connections contains YaCy client connections tracked by the outgoing HTTP client.
- Filter or limit the view to the symptom being investigated.
- Use the observation to decide the next crawler, index, network, or configuration action.
@@ -38,11 +39,11 @@ Administrator access is required. YaCy protects `_p` pages as administration pag
Page backend: `source/net/yacy/htroot/Connections_p.java`.
-No request parameters are needed for normal use of this page.
+No request parameters are needed for normal use of this page. The page refreshes every three seconds.
## What To Expect
-Expect observations: counts, logs, queues, timing, network rows, thread states, or resource values. Monitoring does not fix the issue by itself; it points to the next page or setting to change.
+The incoming count falls when synchronous processing returns or asynchronous processing completes, times out, or fails. Its displayed limit applies to remote requests; local requests are displayed but exempt from rejection. This count is not the number of TCP connections or servlet sessions.
## Related Pages
diff --git a/help/PerformanceQueues_p.md b/help/PerformanceQueues_p.md
index 2edd5b5d3..6cae6dbf1 100644
--- a/help/PerformanceQueues_p.md
+++ b/help/PerformanceQueues_p.md
@@ -12,7 +12,7 @@ backend_java: source/net/yacy/htroot/PerformanceQueues_p.java
## Purpose
-Queue Performance shows processing queues and worker behavior.
+Queue Performance shows processing queues, worker behavior, and concurrency limits.
Use it to find bottlenecks between crawling, parsing, indexing, and response generation.
@@ -28,7 +28,7 @@ Monitoring pages read live peer state from queues, logs, network tables, memory
| Control | Meaning | Values or examples |
| --- | --- | --- |
-| `#[name]#_maxActive` | Enables the named feature. | Integer value. |
+| `#[name]#_maxActive` | Maximum concurrent activity for the named workload. | Positive integer. The Incoming HTTP Requests row limits active remote requests, not TCP connections or servlet sessions. |
## Correct Use
@@ -60,7 +60,9 @@ The table explains values that an agent or script must set deliberately. Paramet
| `Crawler Pool_maxActive` | Enables the named feature. | Set only when this option is part of the intended request; otherwise omit it and let YaCy use the page default. |
| `Robots.txt Pool_maxActive` | Enables the named feature. | Set only when this option is part of the intended request; otherwise omit it and let YaCy use the page default. |
| `crawlPauseRemotesearch` | User or account value. | Set only when this option is part of the intended request; otherwise omit it and let YaCy use the page default. |
-| `httpd Session Pool_maxActive` | Enables the named feature. | Set only when this option is part of the intended request; otherwise omit it and let YaCy use the page default. |
+| `poolConfig` | Applies the submitted crawler, robots.txt, and incoming HTTP request limits. | Include this submit parameter and preserve the current values of limits that are not being changed. |
+| `Incoming HTTP Requests_maxActive` | Positive integer maximum for concurrently active incoming HTTP requests. | Takes effect immediately and is persisted as `httpdMaxBusySessions`; the same value is restored when YaCy restarts. Non-positive values are ignored. |
+| `httpd Session Pool_maxActive` | Legacy alias for `Incoming HTTP Requests_maxActive`. | Accepted for existing automation, but new integrations should use the corrected parameter name. |
Example request shape:
@@ -73,7 +75,7 @@ Content-Type: application/x-www-form-urlencoded
## What To Expect
-Expect observations: counts, logs, queues, timing, network rows, thread states, or resource values. Monitoring does not fix the issue by itself; it points to the next page or setting to change.
+The page reports each workload's current activity and concurrency limit. “Incoming HTTP Requests” counts requests currently executing in the servlet pipeline; it is not a TCP connection pool and not an HTTP session count. Submitting `poolConfig` changes the limits immediately. The incoming request limit persists across restart; remote requests exceeding it receive HTTP 503, while local requests remain exempt from rejection.
## Related Pages
diff --git a/help/Status.md b/help/Status.md
index e8ef1c1b6..eaff3b48c 100644
--- a/help/Status.md
+++ b/help/Status.md
@@ -12,7 +12,7 @@ backend_java: source/net/yacy/htroot/Status.java
## Purpose
-Console Status is the operational dashboard for the peer.
+Console Status is the operational dashboard for the peer. Its Incoming HTTP Requests metric reports requests currently executing and the configured remote-request limit; it does not report TCP connections or servlet sessions.
Use it first to see identity, uptime, network position, indexing state, and important warnings.
@@ -64,7 +64,7 @@ GET /Status.html?aquirerelease=...&ResetTraffic=...&continueCrawlJob=...&jobType
## What To Expect
-Expect observations: counts, logs, queues, timing, network rows, thread states, or resource values. Monitoring does not fix the issue by itself; it points to the next page or setting to change.
+Expect observations including active incoming HTTP requests and their configured limit. Follow that metric to Connection and Request Tracking for individual requests or Concurrency Limits to change the limit. Local requests count as active but are exempt from rejection.
## Related Pages
diff --git a/htroot/Connections_p.html b/htroot/Connections_p.html
index 95f23fc9c..3c66c8bd0 100644
--- a/htroot/Connections_p.html
+++ b/htroot/Connections_p.html
@@ -1,7 +1,7 @@
- YaCy '#[clientname]#': Server Connection Tracking
+ YaCy '#[clientname]#': Connection and Request Tracking
#%env/templates/metas.template%#
@@ -9,9 +9,9 @@
#%env/templates/header.template%#
#%env/templates/submenuAccessTracker.template%#
- Server Connection Tracking
- Incoming Connections
- Showing #[numActiveRunning]# active connections from a max. of #[numMax]# allowed incoming connections.
+ Connection and Request Tracking
+ Incoming HTTP Requests
+ Active HTTP requests: #[numActiveRunning]#. Remote-request limit: #[numMax]#. Local requests are exempt.