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

End of stream error when running the server #18

Open
rlander opened this issue Jan 13, 2013 · 3 comments
Open

End of stream error when running the server #18

rlander opened this issue Jan 13, 2013 · 3 comments

Comments

@rlander
Copy link

rlander commented Jan 13, 2013

Hi!

I'm following the tutorials on https://github.com/dylan-lang/http/tree/master/server/examples/web-in-60 . The code compiles fine, the webserver starts but I'm getting an "End of stream" error:

    2013-01-13T20:25:42.000+0000 info  [Master thread] Starting HTTP Server HTTP Server
    2013-01-13T20:25:42.000+0000 info  [Master thread] Server root directory is /vagrant/dylan-progs/web60-dynamic-content/_build/bin/../
    2013-01-13T20:25:42.000+0000 debug [Master thread] Attempting connection to HTTP Listener for 0.0.0.0:8887 via 127.0.0.1
    2013-01-13T20:25:42.000+0000 info  [HTTP Listener for 0.0.0.0:8887] HTTP Listener for 0.0.0.0:8887 ready for service
    2013-01-13T20:25:42.000+0000 debug [Master thread] Connection to HTTP Listener for 0.0.0.0:8887 successful
    2013-01-13T20:25:42.000+0000 info  [Master thread] HTTP Server 0.9 ready for service
    2013-01-13T20:25:42.000+0000 debug [HTTP Responder 1] Error handling request: End of stream {<byte-char-tcp-socket>}
@waywardmonkeys
Copy link
Member

This is normal and can be ignored. After the server starts up, it connects to itself just to be sure the port is open. I'm not convinced of the utility of this and I also dislike the error message.

@rlander rlander closed this as completed Jan 14, 2013
@waywardmonkeys
Copy link
Member

I'm willing to leave this open so that we fix it. You aren't the first to ask about it.

@cgay
Copy link
Member

cgay commented Jan 22, 2013

Not sure why I thought this was necessary at the time. Possibly there was a bug in shutting down if the port was already in use. It's fine with me if it's removed, especially since one can listen on multiple ports now and it's not clear shutting down would be the right thing in any case.

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