[jira] [Updated] (QPID-7355) qpid-cpp-client holding open file descriptors to dead tcp sockets after connection is closed
[
https://issues.apache.org/jira/browse/QPID-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chester Knapp updated QPID-7355:
Description:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in one of our applications.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
Here's some representative output from lsof:
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
For what its worth, we don't see this issue in another of our applications,
which uses a driver built from the qpid-cpp-0.34-rc branch.
was:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
Here's some representative output from lsof:
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
For what its worth, we don't see this issue in another of our applications,
which uses a driver built from the qpid-cpp-0.34-rc branch.
> qpid-cpp-client holding open file descriptors to dead tcp sockets after
> connection is closed
>
>
> Key: QPID-7355
> URL: https://issues.apache.org/jira/browse/QPID-7355
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
>Reporter: Chester Knapp
>
> We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in one of our
> applications.
> I'm noticing a lot of open files (to dead TCP sockets) that are being held
> open and it appears that they are qpid related (this project don't open any
> TCP connections other than what the qpid client handles).
> Is there perhaps something I need to do on the underlying
> qpid::messaging::Connection other than call close() in order for the file
> descriptor to be closed?
> Here's some representative output from lsof:
> {code}
> #lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
> COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
> NODE NAME
> cloudisti 6387 6404root 55u sock0,6 0t0
> 66423 protocol: TCP
> {code}
> {code}
> # lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
> 192
> {code}
> For what its worth, we don't see this issue in another of our applications,
> which uses a driver built from the qpid-cpp-0.34-rc branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7355) qpid-cpp-client holding open file descriptors to dead tcp sockets after connection is closed
[
https://issues.apache.org/jira/browse/QPID-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chester Knapp updated QPID-7355:
Description:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
Here's some representative output from lsof:
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
For what its worth, we don't see this issue in another of our applications,
which uses a driver built from the qpid-cpp-0.34-rc branch.
was:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
Here's some representative output from lsof:
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
> qpid-cpp-client holding open file descriptors to dead tcp sockets after
> connection is closed
>
>
> Key: QPID-7355
> URL: https://issues.apache.org/jira/browse/QPID-7355
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
>Reporter: Chester Knapp
>
> We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
> I'm noticing a lot of open files (to dead TCP sockets) that are being held
> open and it appears that they are qpid related (this project don't open any
> TCP connections other than what the qpid client handles).
> Is there perhaps something I need to do on the underlying
> qpid::messaging::Connection other than call close() in order for the file
> descriptor to be closed?
> Here's some representative output from lsof:
> {code}
> #lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
> COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
> NODE NAME
> cloudisti 6387 6404root 55u sock0,6 0t0
> 66423 protocol: TCP
> {code}
> {code}
> # lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
> 192
> {code}
> For what its worth, we don't see this issue in another of our applications,
> which uses a driver built from the qpid-cpp-0.34-rc branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7355) qpid-cpp-client holding open file descriptors to dead tcp sockets after connection is closed
[
https://issues.apache.org/jira/browse/QPID-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chester Knapp updated QPID-7355:
Description:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
Here's some representative output from lsof:
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
was:
We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
I'm noticing a lot of open files (to dead TCP sockets) that are being held open
and it appears that they are qpid related (this project don't open any TCP
connections other than what the qpid client handles).
Is there perhaps something I need to do on the underlying
qpid::messaging::Connection other than call close() in order for the file
descriptor to be closed?
{code}
#lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
NODE NAME
cloudisti 6387 6404root 55u sock0,6 0t0
66423 protocol: TCP
{code}
{code}
# lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
192
{code}
> qpid-cpp-client holding open file descriptors to dead tcp sockets after
> connection is closed
>
>
> Key: QPID-7355
> URL: https://issues.apache.org/jira/browse/QPID-7355
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
>Affects Versions: qpid-cpp-0.34
>Reporter: Chester Knapp
>
> We use the qpid-cpp-client-0.34-6.el7.x86_64 driver in our project.
> I'm noticing a lot of open files (to dead TCP sockets) that are being held
> open and it appears that they are qpid related (this project don't open any
> TCP connections other than what the qpid client handles).
> Is there perhaps something I need to do on the underlying
> qpid::messaging::Connection other than call close() in order for the file
> descriptor to be closed?
> Here's some representative output from lsof:
> {code}
> #lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | head -n 1
> COMMANDPID TIDUSER FD TYPE DEVICE SIZE/OFF
> NODE NAME
> cloudisti 6387 6404root 55u sock0,6 0t0
> 66423 protocol: TCP
> {code}
> {code}
> # lsof | grep "^cloud" | grep -v ESTABLISHED | grep TCP | wc -l
> 192
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
