Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RTCP_MSG_IN Error] Bad RTCP header identifier, closing connection. v2.0.0 [9141] #1268

Closed
wutianze opened this issue Jun 26, 2020 · 3 comments

Comments

@wutianze
Copy link

wutianze commented Jun 26, 2020

Hi
One Publisher and one subscriber communicate with each other through the internet using TCPv4TransportDescriptor. The message size is 10k, the qos set for the writer is RELIABLE, max_blocking_time is 5s. The subscriber received some messages(usually 50-90 messages), and then crashed with [RTCP_MSG_IN Error] Bad RTCP header identifier, closing connection.
When using the default Best Effort setting, I ran into this error too.

  • Fast-RTPS version: v2.0.0
  • OS: Ubuntu18.04
@EduPonz EduPonz changed the title [RTCP_MSG_IN Error] Bad RTCP header identifier, closing connection. v2.0.0 [RTCP_MSG_IN Error] Bad RTCP header identifier, closing connection. v2.0.0 [9141] Aug 28, 2020
@EduPonz
Copy link

EduPonz commented Aug 28, 2020

Hi @wutianze ,

We had also detected this issue on our side. We will allocate resources for this as soon as we have them, since we'd like a stable TCP transport in the upcoming releases. We'll keep you posted

@MiguelCompany
Copy link
Member

Should be fixed by #1957

@MiguelCompany
Copy link
Member

Closing via #1957 and corresponding backports.

Feel free to reopen if still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants