You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@eventmesh.apache.org by mi...@apache.org on 2026/09/17 09:23:22 UTC
(eventmesh-site) branch master updated: docs(v2.0.0): port migration resync - 10105 traffic / 10106 admin / 10107 ws / 10108 a2a / 10205 grpc-reserved (#264)
This is an automated email from the ASF dual-hosted git repository.
xwm1992 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new d74efa412 docs(v2.0.0): port migration resync - 10105 traffic / 10106 admin / 10107 ws / 10108 a2a / 10205 grpc-reserved (#264)
d74efa412 is described below
commit d74efa412fb937530629df51b68a59168145c5db
Author: Eason Chen <qq...@gmail.com>
AuthorDate: Thu Sep 17 17:23:17 2026 +0800
docs(v2.0.0): port migration resync - 10105 traffic / 10106 admin / 10107 ws / 10108 a2a / 10205 grpc-reserved (#264)
Full resync from repo develop @ a026fd0fd: the runtime default ports moved back
onto the 1.x scheme (traffic 8080->10105, admin 8081->10106, WS 8082->10107,
A2A gateway ->10108, 10205 documented as RESERVED for a future gRPC server).
All docs swept; also fixes a 10100->10105 typo in the documentation map.
Conventions unchanged: index.md -> documentation-map.md, connectors README ->
connectors.md, site _category_.json preserved.
---
versioned_docs/version-v2.0.0/documentation-map.md | 4 ++--
versioned_docs/version-v2.0.0/feature/a2a.md | 28 +++++++++++-----------
versioned_docs/version-v2.0.0/feature/admin-api.md | 2 +-
.../version-v2.0.0/feature/client-java.md | 26 ++++++++++----------
.../feature/connectors/connectors.md | 2 +-
.../version-v2.0.0/feature/deployment.md | 14 +++++------
versioned_docs/version-v2.0.0/feature/http-api.md | 2 +-
.../version-v2.0.0/feature/observability.md | 2 +-
versioned_docs/version-v2.0.0/feature/pubsub.md | 8 +++----
versioned_docs/version-v2.0.0/feature/streaming.md | 16 ++++++-------
versioned_docs/version-v2.0.0/introduction.md | 8 +++----
.../version-v2.0.0/quickstart/configuration.md | 11 +++++----
.../version-v2.0.0/quickstart/getting-started.md | 24 +++++++++----------
13 files changed, 74 insertions(+), 73 deletions(-)
diff --git a/versioned_docs/version-v2.0.0/documentation-map.md b/versioned_docs/version-v2.0.0/documentation-map.md
index 64199f8b6..8e4073809 100644
--- a/versioned_docs/version-v2.0.0/documentation-map.md
+++ b/versioned_docs/version-v2.0.0/documentation-map.md
@@ -76,9 +76,9 @@ too.
- [Java client guide](feature/client-java.md) — the complete
`CloudEventsClient` / `A2AClient` API surface: builders, pub/sub patterns,
request-reply, transports, security, reliability, backends.
-- [HTTP API](feature/http-api.md) — every traffic endpoint on port 8080:
+- [HTTP API](feature/http-api.md) — every traffic endpoint on port 10105:
methods, request/response shapes, error codes.
-- [Admin API](feature/admin-api.md) — the operational surface on port 8081,
+- [Admin API](feature/admin-api.md) — the operational surface on port 10106,
including the fail-closed bearer-token guard.
- [Observability](feature/observability.md) — metrics (Prometheus + JSON),
traces, health checks, SLOs and alert rules.
diff --git a/versioned_docs/version-v2.0.0/feature/a2a.md b/versioned_docs/version-v2.0.0/feature/a2a.md
index 09c940431..7cbb9df25 100644
--- a/versioned_docs/version-v2.0.0/feature/a2a.md
+++ b/versioned_docs/version-v2.0.0/feature/a2a.md
@@ -191,7 +191,7 @@ The `A2AClient` provides a typed Java API for agent developers:
```java
A2AClient client = A2AClient.builder()
- .gatewayUrl("http://localhost:10105")
+ .gatewayUrl("http://localhost:10108")
.namespace("global")
.agentName("my-agent")
.agentCard(card)
@@ -401,7 +401,7 @@ The A2A Gateway provides a REST API for external clients and non-Java agents.
#### 5.3.1 Submit Task (Sync)
```bash
-curl -X POST 'http://localhost:10105/a2a/tasks?mode=sync' \
+curl -X POST 'http://localhost:10108/a2a/tasks?mode=sync' \
-H 'Content-Type: application/json' \
-d '{"targetAgent":"weather-agent","message":"Beijing"}'
```
@@ -418,7 +418,7 @@ Response:
#### 5.3.2 Submit Task (Async)
```bash
-curl -X POST 'http://localhost:10105/a2a/tasks?mode=async' \
+curl -X POST 'http://localhost:10108/a2a/tasks?mode=async' \
-H 'Content-Type: application/json' \
-d '{"targetAgent":"weather-agent","message":"Shanghai"}'
```
@@ -435,7 +435,7 @@ Response (HTTP 202):
#### 5.3.3 SSE Stream
```bash
-curl -N http://localhost:10105/a2a/tasks/task-a1b2c3d4/stream
+curl -N http://localhost:10108/a2a/tasks/task-a1b2c3d4/stream
```
Response (`text/event-stream`):
@@ -450,14 +450,14 @@ data: {"taskId":"task-a1b2c3d4","state":"completed","data":"The weather in Beiji
#### 5.3.4 List Agents
```bash
-curl http://localhost:10105/a2a/agents
+curl http://localhost:10108/a2a/agents
```
### 5.4 A2AClient SDK (Java)
```java
A2AClient client = A2AClient.builder()
- .gatewayUrl("http://localhost:10105")
+ .gatewayUrl("http://localhost:10108")
.namespace("global")
.agentName("my-agent")
.agentCard(card)
@@ -767,29 +767,29 @@ A2A Gateway 提供完整的 REST API,支持非 Java 客户端通过 HTTP 交
```bash
# 同步提交 task
-curl -X POST 'http://localhost:10105/a2a/tasks?mode=sync' \
+curl -X POST 'http://localhost:10108/a2a/tasks?mode=sync' \
-H 'Content-Type: application/json' \
-d '{"targetAgent":"weather-agent","message":"Beijing"}'
# 异步提交 task
-curl -X POST 'http://localhost:10105/a2a/tasks?mode=async' \
+curl -X POST 'http://localhost:10108/a2a/tasks?mode=async' \
-H 'Content-Type: application/json' \
-d '{"targetAgent":"weather-agent","message":"Shanghai"}'
# 查询状态
-curl http://localhost:10105/a2a/tasks/{taskId}
+curl http://localhost:10108/a2a/tasks/{taskId}
# 列出 tasks(支持 state/limit/offset)
-curl 'http://localhost:10105/a2a/tasks?state=COMPLETED&limit=20&offset=0'
+curl 'http://localhost:10108/a2a/tasks?state=COMPLETED&limit=20&offset=0'
# SSE 流式推送(含 heartbeat 保活)
-curl -N http://localhost:10105/a2a/tasks/{taskId}/stream
+curl -N http://localhost:10108/a2a/tasks/{taskId}/stream
# 健康检查
-curl http://localhost:10105/a2a/health
+curl http://localhost:10108/a2a/health
# 列出 agents
-curl http://localhost:10105/a2a/agents
+curl http://localhost:10108/a2a/agents
```
#### REST API 端点列表
@@ -812,7 +812,7 @@ curl http://localhost:10105/a2a/agents
```java
A2AClient client = A2AClient.builder()
- .gatewayUrl("http://localhost:10105")
+ .gatewayUrl("http://localhost:10108")
.namespace("global")
.agentName("my-agent")
.agentCard(card)
diff --git a/versioned_docs/version-v2.0.0/feature/admin-api.md b/versioned_docs/version-v2.0.0/feature/admin-api.md
index 987bfe587..8c5005d7b 100644
--- a/versioned_docs/version-v2.0.0/feature/admin-api.md
+++ b/versioned_docs/version-v2.0.0/feature/admin-api.md
@@ -1,7 +1,7 @@
# Admin API Reference
**Audience:** operators and dashboards. Every endpoint below lives on the
-**admin HTTP port (default 8081)**, served by `UniAdminServer` — a separate
+**admin HTTP port (default 10106)**, served by `UniAdminServer` — a separate
server so management traffic never competes with data traffic.
---
diff --git a/versioned_docs/version-v2.0.0/feature/client-java.md b/versioned_docs/version-v2.0.0/feature/client-java.md
index a57573fe1..b68f5b2cb 100644
--- a/versioned_docs/version-v2.0.0/feature/client-java.md
+++ b/versioned_docs/version-v2.0.0/feature/client-java.md
@@ -56,7 +56,7 @@ A typical client looks like this:
```java
CloudEventsClient client = CloudEventsClient.builder()
- .runtimeUrl("http://localhost:8080") // EventMesh Runtime HTTP endpoint
+ .runtimeUrl("http://localhost:10105") // EventMesh Runtime HTTP endpoint
.clientId("order-svc") // unique per JVM
.pollIntervalMs(500L) // long-poll cadence
.build();
@@ -120,10 +120,10 @@ org.apache.eventmesh.client.cloudevents.CloudEventsClient
```java
CloudEventsClient.builder()
- .runtimeUrl("http://localhost:8080") // required — Runtime HTTP endpoint
+ .runtimeUrl("http://localhost:10105") // required — Runtime HTTP endpoint
.clientId("my-service") // required — unique per JVM
.pollIntervalMs(500L) // long-poll cadence (default: builder default)
- .wsUrl("http://localhost:8082") // optional — required for subscribeWs
+ .wsUrl("http://localhost:10107") // optional — required for subscribeWs
.build();
```
@@ -138,7 +138,7 @@ Environment variables are honored via `System.getProperty` for tests:
```java
CloudEventsClient client = CloudEventsClient.builder()
- .runtimeUrl(System.getProperty("eventmesh.runtime.url", "http://localhost:8080"))
+ .runtimeUrl(System.getProperty("eventmesh.runtime.url", "http://localhost:10105"))
.clientId("demo-" + System.currentTimeMillis())
.build();
```
@@ -224,9 +224,9 @@ only difference is the **push direction**.
| Transport | Endpoint | Push direction | Port |
| --- | --- | --- | --- |
-| Long-poll | `POST /events/subscribe` | client-driven | Runtime HTTP port (default 8080) |
-| SSE | `GET /events/stream` (text/event-stream) | server push | Runtime HTTP port (default 8080) |
-| WebSocket | runtime WS endpoint | server push, bi-directional | Runtime WS port (default 8082, configurable) |
+| Long-poll | `POST /events/subscribe` | client-driven | Runtime HTTP port (default 10105) |
+| SSE | `GET /events/stream` (text/event-stream) | server push | Runtime HTTP port (default 10105) |
+| WebSocket | runtime WS endpoint | server push, bi-directional | Runtime WS port (default 10107, configurable) |
WebSocket needs a separate port because the WS upgrade is a different protocol
negotiation than plain HTTP. The Runtime starts the WS server on its own port
@@ -239,8 +239,8 @@ client.subscribeSse("orders", "BROADCAST", event -> { /* server-push */ });
// WebSocket — separate port
CloudEventsClient wsClient = CloudEventsClient.builder()
- .runtimeUrl("http://localhost:8080") // HTTP (publish / long-poll / SSE)
- .wsUrl("http://localhost:8082") // WS push
+ .runtimeUrl("http://localhost:10105") // HTTP (publish / long-poll / SSE)
+ .wsUrl("http://localhost:10107") // WS push
.clientId("ws-sub").build();
wsClient.subscribeWs("orders", "BROADCAST", event -> { /* WS push */ });
```
@@ -298,7 +298,7 @@ chunks flowing back, multi-turn conversation context).
```java
CloudEventsClient client = CloudEventsClient.builder()
- .runtimeUrl("http://localhost:8080").clientId("my-app").build();
+ .runtimeUrl("http://localhost:10105").clientId("my-app").build();
try (StreamingResponse r = client.streaming()
.openSession(OpenSession.builder().clientId(client.clientId()).build())
@@ -439,7 +439,7 @@ canceled`) on top of the same storage substrate. The client side is
```java
A2AClient client = A2AClient.builder()
- .gatewayUrl("http://localhost:8080") // Runtime A2A gateway (port 8080 by default)
+ .gatewayUrl("http://localhost:10105") // Runtime A2A gateway (port 10105 by default)
.namespace("default")
.agentName("order-agent")
.heartbeatInterval(30_000L)
@@ -567,7 +567,7 @@ Plain-text Kafka clusters need none of these.
public class Demo {
public static void main(String[] args) throws Exception {
CloudEventsClient client = CloudEventsClient.builder()
- .runtimeUrl(System.getProperty("eventmesh.runtime.url", "http://localhost:8080"))
+ .runtimeUrl(System.getProperty("eventmesh.runtime.url", "http://localhost:10105"))
.clientId("demo-" + System.currentTimeMillis())
.pollIntervalMs(500L)
.build();
@@ -616,7 +616,7 @@ The same `Demo` class runs unchanged on all three.
| Backend connection | Runtime startup log | `[storage] connected to <backend>` line; otherwise no subscriptions will fire |
| Security gate | Runtime response | `401` on first request → auth header missing; `429` → quota exhausted; `403` → ACL denied |
| Quota exhaustion | Runtime metrics | `eventmesh_security_gate_quota_*` per-tenant counters |
-| Dead-letter inspection | admin HTTP (port 8081) | `GET /admin/dlq?topic=<topic>` |
+| Dead-letter inspection | admin HTTP (port 10106) | `GET /admin/dlq?topic=<topic>` |
| A2A agent registry | `A2AClient.listAgents()` | Should return at least one `AgentCard` for `agentName` you registered |
See [docs/feature/deployment.md](deployment.md) for SLOs and
diff --git a/versioned_docs/version-v2.0.0/feature/connectors/connectors.md b/versioned_docs/version-v2.0.0/feature/connectors/connectors.md
index 7f7e4d760..843eac8ac 100644
--- a/versioned_docs/version-v2.0.0/feature/connectors/connectors.md
+++ b/versioned_docs/version-v2.0.0/feature/connectors/connectors.md
@@ -46,7 +46,7 @@ CONNECTOR_OPTS="-Dconnector.class=org.apache.eventmesh.connector.kafka.source.Ka
bin/start-connector.sh
```
-Common flags: `eventmesh.runtime.url` (default `http://localhost:8080`),
+Common flags: `eventmesh.runtime.url` (default `http://localhost:10105`),
`connector.offset.mode` (`remote` | `rocksdb` | `inmemory`), and for multiple
connectors per process the numbered form `-Dconnector.1.class=...`,
`-Dconnector.2.class=...` (any `-Dconnector.N.*` key is passed through to the
diff --git a/versioned_docs/version-v2.0.0/feature/deployment.md b/versioned_docs/version-v2.0.0/feature/deployment.md
index 6783d0a61..1e364e278 100644
--- a/versioned_docs/version-v2.0.0/feature/deployment.md
+++ b/versioned_docs/version-v2.0.0/feature/deployment.md
@@ -25,9 +25,9 @@ distribution does not start the A2A listener.
| Port | Server | Notes |
| --- | --- | --- |
-| 8080 | Traffic HTTP | `/events/*`, `/session/*`, `/agent/*`, legacy `/eventmesh/*` |
-| 8081 | Admin HTTP | `/admin/*` + `/metrics` (Prometheus); token-guarded |
-| 8082 | WebSocket *(opt-in)* | `-Deventmesh.ws.port=8082`; disabled by default |
+| 10105 | Traffic HTTP | `/events/*`, `/session/*`, `/agent/*`, legacy `/eventmesh/*` |
+| 10106 | Admin HTTP | `/admin/*` + `/metrics` (Prometheus); token-guarded |
+| 10107 | WebSocket *(opt-in)* | `-Deventmesh.ws.port=10107`; disabled by default |
## Running
@@ -37,7 +37,7 @@ distribution does not start the A2A listener.
docker run -d --name eventmesh \
-e EVENTMESH_STORAGE_TYPE=kafka \
-e EVENTMESH_KAFKA_NAMESRV=YOUR_KAFKA:9092 \
- -p 8080:8080 -p 8081:8081 \
+ -p 10105:10105 -p 10106:10106 \
apache/eventmesh:latest
```
@@ -62,7 +62,7 @@ onto `-D` system properties.
### Verify
```shell
-curl http://localhost:8081/admin/health # {"status":"UP"}
+curl http://localhost:10106/admin/health # {"status":"UP"}
```
## Kubernetes
@@ -95,7 +95,7 @@ Multi-instance coordination keys:
```properties
-Deventmesh.meta.type=nacos # cluster mode; currently: nacos
-Deventmesh.meta.addr=nacos:8848
--Deventmesh.instance.id=10.0.0.5:8080 # defaults to host:port
+-Deventmesh.instance.id=10.0.0.5:10105 # defaults to host:port
-Deventmesh.offset.meta=true # opt-in remote offset tier (see below)
```
@@ -113,7 +113,7 @@ process** — `eventmesh-connector-runtime` — and talk to the runtime over
HTTP + CloudEvents:
```shell
-docker run -e EVENTMESH_RUNTIME_URL=http://runtime:8080 eventmesh-connector:uni
+docker run -e EVENTMESH_RUNTIME_URL=http://runtime:10105 eventmesh-connector:uni
```
Connector definitions are managed through `/admin/connectors` (CRUD) and
diff --git a/versioned_docs/version-v2.0.0/feature/http-api.md b/versioned_docs/version-v2.0.0/feature/http-api.md
index dcdaeab73..d9538f6f3 100644
--- a/versioned_docs/version-v2.0.0/feature/http-api.md
+++ b/versioned_docs/version-v2.0.0/feature/http-api.md
@@ -2,7 +2,7 @@
**Audience:** application developers integrating with the EventMesh traffic
port directly (any language, no SDK required). Every endpoint below lives on
-the **traffic HTTP port (default 8080)** and is registered in
+the **traffic HTTP port (default 10105)** and is registered in
`UniHttpServer`. The Java SDK wraps all of these — see the
[Java client guide](client-java.md).
diff --git a/versioned_docs/version-v2.0.0/feature/observability.md b/versioned_docs/version-v2.0.0/feature/observability.md
index fe3b2470b..2fa1af954 100644
--- a/versioned_docs/version-v2.0.0/feature/observability.md
+++ b/versioned_docs/version-v2.0.0/feature/observability.md
@@ -14,7 +14,7 @@ Observability is **OpenTelemetry-first**: every metric is an OTel instrument
deployment configures (OTLP, Prometheus-via-OTel, …). For zero-dependency
scraping the admin server also mirrors the same counters:
-- `GET /metrics` — Prometheus text exposition (port 8081)
+- `GET /metrics` — Prometheus text exposition (port 10106)
- `GET /admin/metrics` — JSON snapshot
| Metric (Prometheus name) | Kind | Meaning |
diff --git a/versioned_docs/version-v2.0.0/feature/pubsub.md b/versioned_docs/version-v2.0.0/feature/pubsub.md
index 5ebafbf1b..0b9d4727a 100644
--- a/versioned_docs/version-v2.0.0/feature/pubsub.md
+++ b/versioned_docs/version-v2.0.0/feature/pubsub.md
@@ -38,7 +38,7 @@ legacy MeshMessage / OpenMessaging formats are adapted onto the same frame.
Raw HTTP:
```shell
-curl -X POST "http://localhost:8080/events/publish?topic=orders" \
+curl -X POST "http://localhost:10105/events/publish?topic=orders" \
-H "Content-Type: application/cloudevents+json" \
-d '{ ... event above ... }'
```
@@ -69,10 +69,10 @@ mode**. There are **no consumer groups** — EventMesh tracks offsets per
(topic, clientId) itself.
```shell
-curl -X POST http://localhost:8080/events/subscribe \
+curl -X POST http://localhost:10105/events/subscribe \
-H "Content-Type: application/json" \
-d '{"clientId":"order-svc","topic":"orders","mode":"LOAD_BALANCE"}'
-# → {"subscriptionId":"...", "instanceUrl":"http://10.0.0.5:8080"}
+# → {"subscriptionId":"...", "instanceUrl":"http://10.0.0.5:10105"}
```
The response's `instanceUrl` is the instance the subscriber should pin
@@ -142,7 +142,7 @@ Keys live in `eventmesh-runtime/conf/eventmesh.properties`
| Key | Default | Effect |
| --- | --- | --- |
-| `eventmesh.http.port` | `8080` | Traffic endpoints |
+| `eventmesh.http.port` | `10105` | Traffic endpoints |
| `eventmesh.ws.port` | `-1` (off) | WebSocket push transport |
| `eventmesh.delivery.topology` | `LOCAL_STICKY_PULL` | Single- vs multi-instance polling (see [Control plane](control-plane.md)) |
diff --git a/versioned_docs/version-v2.0.0/feature/streaming.md b/versioned_docs/version-v2.0.0/feature/streaming.md
index d049be998..383bc7956 100644
--- a/versioned_docs/version-v2.0.0/feature/streaming.md
+++ b/versioned_docs/version-v2.0.0/feature/streaming.md
@@ -10,9 +10,9 @@ long-poll, SSE, WebSocket, and the two streaming-session modes.
| Transport | Endpoint | Direction | Port | Best for |
| --- | --- | --- | --- | --- |
-| **HTTP long-poll** | `GET /events/poll` | client-driven | 8080 | Batch consumers, scheduled jobs, serverless; NAT-friendly |
-| **SSE** | `GET /events/stream` | server push (one-way) | 8080 | Browser/mobile push, dashboards, LLM token streams |
-| **WebSocket** | WS upgrade on the dedicated port | server push, bi-directional | 8082 (opt-in) | Low-latency interactive clients |
+| **HTTP long-poll** | `GET /events/poll` | client-driven | 10105 | Batch consumers, scheduled jobs, serverless; NAT-friendly |
+| **SSE** | `GET /events/stream` | server push (one-way) | 10105 | Browser/mobile push, dashboards, LLM token streams |
+| **WebSocket** | WS upgrade on the dedicated port | server push, bi-directional | 10107 (opt-in) | Low-latency interactive clients |
All three deliver identical CloudEvent payloads and share the same ACK /
retry / quota machinery — the only difference is the push direction.
@@ -20,7 +20,7 @@ retry / quota machinery — the only difference is the push direction.
## Long-poll
```shell
-curl "http://localhost:8080/events/poll?clientId=order-svc&timeoutMs=30000"
+curl "http://localhost:10105/events/poll?clientId=order-svc&timeoutMs=30000"
# → [{ "deliveryId": "...", "event": { ...CloudEvent... } }, ...]
```
@@ -31,7 +31,7 @@ Batches up to `max` (default 100) buffered events; blocks up to
## SSE
```shell
-curl -N "http://localhost:8080/events/stream?clientId=order-svc" \
+curl -N "http://localhost:10105/events/stream?clientId=order-svc" \
-H "Accept: text/event-stream"
```
@@ -42,15 +42,15 @@ frames as events arrive. Write failures nack the dispatcher immediately
## WebSocket
-The WS server is a separate port (`-Deventmesh.ws.port=8082`, disabled by
+The WS server is a separate port (`-Deventmesh.ws.port=10107`, disabled by
default) because the upgrade handshake is a different protocol negotiation.
The **client must configure `wsUrl` explicitly** — pointing it at the HTTP
port fails the handshake:
```java
CloudEventsClient wsClient = CloudEventsClient.builder()
- .runtimeUrl("http://localhost:8080") // publish / long-poll / SSE
- .wsUrl("http://localhost:8082") // WS push
+ .runtimeUrl("http://localhost:10105") // publish / long-poll / SSE
+ .wsUrl("http://localhost:10107") // WS push
.clientId("ws-sub").build();
wsClient.subscribeWs("orders", "BROADCAST", event -> { ... });
```
diff --git a/versioned_docs/version-v2.0.0/introduction.md b/versioned_docs/version-v2.0.0/introduction.md
index 601e5855d..6e98b0b1f 100644
--- a/versioned_docs/version-v2.0.0/introduction.md
+++ b/versioned_docs/version-v2.0.0/introduction.md
@@ -51,8 +51,8 @@ makes the rest of the properties possible:
```
┌─────────────────────────────┐
publishers / │ EventMesh Runtime(s) │ storage backend
- subscribers ─HTTP─▶│ 8080 traffic 8081 admin │─WAL──▶ RocketMQ / Kafka
- (SDK or curl) │ 8082 WebSocket (opt-in) │ (pluggable SPI)
+ subscribers ─HTTP─▶│ 10105 traffic 10106 admin │─WAL──▶ RocketMQ / Kafka
+ (SDK or curl) │ 10107 WebSocket (opt-in) │ (pluggable SPI)
└──────────────┬──────────────┘
│ meta (optional, multi-instance)
▼
@@ -91,10 +91,10 @@ makes the rest of the properties possible:
docker run -d --name eventmesh \
-e EVENTMESH_STORAGE_TYPE=kafka \
-e EVENTMESH_KAFKA_NAMESRV=YOUR_KAFKA:9092 \
- -p 8080:8080 -p 8081:8081 \
+ -p 10105:10105 -p 10106:10106 \
apache/eventmesh:latest
-curl -X POST "http://localhost:8080/events/publish?topic=hello" \
+curl -X POST "http://localhost:10105/events/publish?topic=hello" \
-H "Content-Type: application/cloudevents+json" \
-d '{"specversion":"1.0","id":"1","source":"/demo","type":"demo.hello","data":"world"}'
```
diff --git a/versioned_docs/version-v2.0.0/quickstart/configuration.md b/versioned_docs/version-v2.0.0/quickstart/configuration.md
index a0705ff1e..e459127ee 100644
--- a/versioned_docs/version-v2.0.0/quickstart/configuration.md
+++ b/versioned_docs/version-v2.0.0/quickstart/configuration.md
@@ -75,9 +75,10 @@ Usually set via `-D` by `bin/start.sh`; override here if needed.
| Key | Default | Description |
|---|---|---|
-| `eventmesh.http.port` | `8080` | Traffic HTTP (`/events/*`, `/agent/*`, `/session/*`) |
-| `eventmesh.admin.port` | `8081` | Admin HTTP (`/admin/*`, `/metrics`) |
-| `eventmesh.ws.port` | `-1` (disabled) | WebSocket push port; set e.g. `8082` to enable |
+| `eventmesh.http.port` | `10105` | Traffic HTTP (`/events/*`, `/agent/*`, `/session/*`) |
+| `eventmesh.admin.port` | `10106` | Admin HTTP (`/admin/*`, `/metrics`) |
+| `eventmesh.ws.port` | `-1` (disabled) | WebSocket push port; set e.g. `10107` to enable |
+| `eventmesh.grpc.port` | `10205` | RESERVED for the future gRPC protocol (not served yet; keeps the 1.x default warm) |
| `eventmesh.offset.path` | `./data/offset` | Local offset store directory |
## 4. Security
@@ -112,7 +113,7 @@ programmatically via `configureTopicRateLimit(topic, capacity, permitsPerSecond)
buckets make publish fail with `RateLimitedException` → HTTP `429` on the publish endpoint.
Cluster-wide limits can be inspected and adjusted at `POST /admin/ratelimit`.
-## 6. Admin endpoints (port 8081)
+## 6. Admin endpoints (port 10106)
| Endpoint | Purpose |
|---|---|
@@ -129,7 +130,7 @@ Cluster-wide limits can be inspected and adjusted at `POST /admin/ratelimit`.
| `GET/POST /admin/connectors` | connector definitions (CRUD) |
| `GET /admin/connector-workers` | connector worker registry |
-## 7. Traffic endpoints (port 8080)
+## 7. Traffic endpoints (port 10105)
Full request/response shapes: see the [client guide](../feature/client-java.md).
Summary:
diff --git a/versioned_docs/version-v2.0.0/quickstart/getting-started.md b/versioned_docs/version-v2.0.0/quickstart/getting-started.md
index ea1de2886..9413b201c 100644
--- a/versioned_docs/version-v2.0.0/quickstart/getting-started.md
+++ b/versioned_docs/version-v2.0.0/quickstart/getting-started.md
@@ -44,7 +44,7 @@ changes.
```shell
sudo docker pull apache/eventmesh:latest
sudo docker run -d --name eventmesh \
- -p 8080:8080 -p 8081:8081 \
+ -p 10105:10105 -p 10106:10106 \
apache/eventmesh:latest
```
@@ -53,8 +53,8 @@ dependency, ready for a smoke test as-is. For a real broker add
`-e EVENTMESH_STORAGE_TYPE=kafka` (or `rocketmq` / `rocketmq5`) and the
backend address keys shown below.
-Ports: `8080` = traffic HTTP (`/events/*`), `8081` = admin HTTP (`/admin/*`). The WebSocket
-push port (`8082`) is opt-in.
+Ports: `10105` = traffic HTTP (`/events/*`), `10106` = admin HTTP (`/admin/*`). The WebSocket
+push port (`10107`) is opt-in.
### Option B — From source
@@ -76,7 +76,7 @@ Storage-specific keys (all overridable via `-D` system properties) are documente
### Verify it is up
```shell
-curl http://localhost:8081/admin/health
+curl http://localhost:10106/admin/health
# {"status":"UP"}
```
@@ -86,7 +86,7 @@ Applications send standard [CloudEvents](https://cloudevents.io) 1.0 over HTTP.
means the event is durably in the WAL:
```shell
-curl -X POST "http://localhost:8080/events/publish?topic=orders" \
+curl -X POST "http://localhost:10105/events/publish?topic=orders" \
-H "Content-Type: application/cloudevents+json" \
-d '{
"specversion": "1.0",
@@ -105,17 +105,17 @@ then receive via one of three transports:
```shell
# 1. register: clientId + topic + distribution mode
-curl -X POST http://localhost:8080/events/subscribe \
+curl -X POST http://localhost:10105/events/subscribe \
-H "Content-Type: application/json" \
-d '{"clientId":"order-svc","topic":"orders","mode":"LOAD_BALANCE"}'
# 2a. HTTP long-polling (params: clientId, max, timeoutMs)
-curl "http://localhost:8080/events/poll?clientId=order-svc&max=100&timeoutMs=30000"
+curl "http://localhost:10105/events/poll?clientId=order-svc&max=100&timeoutMs=30000"
# → [{"deliveryId":"d-...","event":{...CloudEvent...}}, ...]
# 2b. after processing, acknowledge so the offset advances (at-least-once).
# One deliveryId per call - take it from the poll response above.
-curl -X POST http://localhost:8080/events/ack \
+curl -X POST http://localhost:10105/events/ack \
-H "Content-Type: application/json" \
-d '{"deliveryId":"d-..."}'
```
@@ -132,7 +132,7 @@ SSE and WebSocket push are also available; the raw HTTP forms are:
```shell
# SSE — server push over a long-lived HTTP connection
-curl -N "http://localhost:8080/events/stream?clientId=order-svc" \r
+curl -N "http://localhost:10105/events/stream?clientId=order-svc" \r
-H "Accept: text/event-stream"
# WebSocket — full-duplex server push over the dedicated WS port
@@ -140,7 +140,7 @@ curl -N "http://localhost:8080/events/stream?clientId=order-svc" \r
curl --include --no-buffer \r
-H "Connection: Upgrade" -H "Upgrade: websocket" \r
-H "Sec-WebSocket-Version: 13" -H "Sec-WebSocket-Key: dGVzdA==" \r
- "http://localhost:8082/events/stream?clientId=order-svc"
+ "http://localhost:10107/events/stream?clientId=order-svc"
```
The `CloudEventsClient` Java SDK wraps all three transports —
@@ -151,7 +151,7 @@ The `CloudEventsClient` Java SDK wraps all three transports —
```java
CloudEventsClient client = CloudEventsClient.builder()
- .baseUrl("http://localhost:8080")
+ .baseUrl("http://localhost:10105")
.build();
client.init();
@@ -180,4 +180,4 @@ Full API (request/reply, streaming sessions, lite topics, SSE/WS): see the
- [A2A gateway](../feature/a2a.md) — agent-to-agent messaging (Experimental)
- Admin API (`/admin/*`) quick reference: `metrics`, `subscriptions`, `offsets`, `clients`,
`client/reject`, `dlq/replay`, `dlq/browse`, `ratelimit`, `health`, `connectors`,
- `connector-workers` on port 8081
+ `connector-workers` on port 10106
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: commits-help@eventmesh.apache.org