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

TCPStream::connect() does not return an error when there are no connections free #34

Open
bremoran opened this issue Oct 27, 2015 · 2 comments
Labels

Comments

@bremoran
Copy link
Contributor

When allocating a TCP protocol control buffer fails, TCPStream::connect() and TCPStream::open() should return an error code.

@ciarmcom
Copy link
Member

ARM Internal Ref: IOTSFW-1092

@bremoran
Copy link
Contributor Author

bremoran commented Nov 2, 2015

The sockets layer and the LwIP adaptor forward failure codes correctly. The problem here is that LwIP's behaviour on allocation of a TCP Protocol Control Block is to kill off a previous control block if the current control block is of higher priority. By default, LwIP sets all TCP PCBs to the same priority, so this seems to allow LwIP to kill off an existing connection in order to allocate the current one.

Since this is LwIP internal behaviour, it is not viable to fix this issue.

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

No branches or pull requests

2 participants