You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Zhenyu Yang (Jira)" <ji...@apache.org> on 2022/05/11 00:59:00 UTC
[jira] [Updated] (QPID-8589) connection not fully closed
[ https://issues.apache.org/jira/browse/QPID-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhenyu Yang updated QPID-8589:
------------------------------
Description:
We have been using Qpid C++ 1.39.0 broker/client for quite a while and recently start to encounter some error. The exact repro steps are not clear yet, but it seems more often under resource stress like more concurrent jobs or queue limit exceeded (as shown below). When it happens, we usually see a few things (may or may not happen together).
# "[Broker] error Channel exception: session-busy: Session already attached"
# "[Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:xxxxx timed out: closing" (note, we use loopback address)
# "[Broker] ... resource-limit-exceeded"
# "[Client] error session-busy: Session detached by peer"
# a few client TCP sockets left in CLOSE-WAIT state
# for the same client, its CPU goes to 100%, strace shows nothing while gdb attach shows call stack around "Send --> waitForCapacity"
Your help in trouble-shooting is highly appreciated, thank you!
was:
We have been using Qpid C++ 1.39.0 broker/client for quite a while and recently start to encounter some error. The exact repro steps are not clear yet, but it seems more often under resource stress like more concurrent jobs or queue limit exceeded (as shown below). When it happens, we usually see a few things (may or may not happen together).
# "[Broker] error Channel exception: session-busy: Session already attached"
# "[Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:xxxxx timed out: closing"
# "[Broker] ... resource-limit-exceeded"
# "[Client] error session-busy: Session detached by peer"
# a few client TCP sockets left in CLOSE-WAIT state
# for the same client, its CPU goes to 100%, strace shows nothing while gdb attach shows call stack around "Send --> waitForCapacity"
Your help in trouble-shooting is highly appreciated, thank you!
> connection not fully closed
> ---------------------------
>
> Key: QPID-8589
> URL: https://issues.apache.org/jira/browse/QPID-8589
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Affects Versions: qpid-cpp-1.39.0
> Reporter: Zhenyu Yang
> Priority: Major
>
> We have been using Qpid C++ 1.39.0 broker/client for quite a while and recently start to encounter some error. The exact repro steps are not clear yet, but it seems more often under resource stress like more concurrent jobs or queue limit exceeded (as shown below). When it happens, we usually see a few things (may or may not happen together).
> # "[Broker] error Channel exception: session-busy: Session already attached"
> # "[Protocol] error Connection qpid.127.0.0.1:5672-127.0.0.1:xxxxx timed out: closing" (note, we use loopback address)
> # "[Broker] ... resource-limit-exceeded"
> # "[Client] error session-busy: Session detached by peer"
> # a few client TCP sockets left in CLOSE-WAIT state
> # for the same client, its CPU goes to 100%, strace shows nothing while gdb attach shows call stack around "Send --> waitForCapacity"
> Your help in trouble-shooting is highly appreciated, thank you!
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org