Why is my RVA host showing many sockets remaining in a CLOSE_WAIT state?
Article ID: KB0092244
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
If a direct client terminates while RVA was not reading from its socket and does not have anything to send to that client, RVA may not detect the client is gone and as a result may not close its socket. This means that the RVA host will show multiple sockets remaining in a CLOSE_WAIT state.
This behaviour is not a defect, but more a "fact of life".
One way to avoid this would be to have a backend beacon that would ensure that periodic messages are sent to all clients. If such a beacon were to be implemented, no connection would remain in CLOSE_WAIT longer than 1 beacon interval. For instance, you could make the following changes in your code:
- Applet is subscribing to a dummy subject, which it will discard upon reception
- Or have a backend application sending dummy messages at regular interval.
If a direct client terminates while RVA was not reading from its socket and does not have anything to send to that client, RVA may not detect the client is gone and as a result may not close its socket. This means that the RVA host will show multiple sockets remaining in a CLOSE_WAIT state.
This behaviour is not a defect, but more a "fact of life".
One way to avoid this would be to have a backend beacon that would ensure that periodic messages are sent to all clients. If such a beacon were to be implemented, no connection would remain in CLOSE_WAIT longer than 1 beacon interval. For instance, you could make the following changes in your code:
- Applet is subscribing to a dummy subject, which it will discard upon reception
- Or have a backend application sending dummy messages at regular interval.
Issue/Introduction
Why is my RVA host showing many sockets remaining in a CLOSE_WAIT state?
Environment
Product: TIBCO Rendezvous
Version: 7.x.x
OS: All
--------------------
Feedback
Yes
No
Powered by
