http_server: Not receiving Websocket messages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- api, backend, networking
Research direction
Start by reproducing the reconnection behavior with the provided http_server configuration, focusing on websocket message handling and the broken-pipe warning. Determine why reconnections fail or stop delivering messages, then verify that repeated reconnects reliably receive messages without the warning.
Written by the indexing model from the issue text.
Description
When initially connecting, everything works as expected. However, upon reconnection, message handling becomes inconsistent. Sometimes messages are delivered, but this is very random, and often the reconnection fails entirely.
In some cases, the following warning appears in the logs:
WARN Failed to send message: write tcp 172.25.0.8:4195->172.25.0.1:57554: write: broken pipe @service=redpanda-connect label="" path=root.output
Running config:
logger:
level: ALL
format: logfmt
add_timestamp: false
static_fields:
'@service': redpanda-connect
input:
kafka:
addresses: ["redpanda:9092"] # No default (required)
topics: ["TEST"] # No default (required)
target_version: 2.1.0 # No default (optional)
consumer_group: "test"
checkpoint_limit: 1024
auto_replay_nacks: true
buffer:
none: {}
pipeline:
threads: -1
processors: []
output:
broker:
pattern: fan_out
outputs:
- stdout: {}
# - kafka:
# addresses: ["redpanda:9092"] # No default (required)
# topic: "OUTPUT" # No default (required)
- http_server:
ws_path: /get/ws
allowed_verbs:
- GET
Any guidance or suggestions on how to resolve this issue would be greatly appreciated.
- Dominant language
- Go
- Stars
- 571
- Forks
- 121
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 15
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from redpanda-data/benthos
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
redpanda-data/benthos#404 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
redpanda-data/benthos#503 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
redpanda-data/benthos#502 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 72/100
redpanda-data/benthos#481 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
redpanda-data/benthos#469 ·
Maintainers usually reply within 1 day
All issues in redpanda-data/benthos
Similar issues
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
txn2/mcp-data-platform#1984 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
kind/docs prio/P2
Difficulty 1/5 Under an hour Newbie friendliness 95/100
agent-substrate/substrate#1986 ·
Maintainers usually reply within 1 day