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

server.stop produces an error: java.net.SocketException: socket closed #74

Closed
processing-bugs opened this Issue Feb 10, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@processing-bugs

processing-bugs commented Feb 10, 2013

Original author: b...@processing.org (June 07, 2010 00:16:57)

This bug automatically added from:
http://dev.processing.org/bugs/show_bug.cgi?id=89

Comment from fry, 2005-07-18 22:14

server.stop produces an error:
java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)

example attached.

Original issue: http://code.google.com/p/processing/issues/detail?id=35

@processing-bugs

This comment has been minimized.

Show comment
Hide comment
@processing-bugs

processing-bugs Feb 10, 2013

From b...@processing.org on June 07, 2010 00:16:58
Comment from fry, 2005-07-18 22:16

Created an attachment (id=5)
test sketch that shows the problem

processing-bugs commented Feb 10, 2013

From b...@processing.org on June 07, 2010 00:16:58
Comment from fry, 2005-07-18 22:16

Created an attachment (id=5)
test sketch that shows the problem

@benfry benfry added help wanted and removed bug labels Nov 15, 2014

@kfeuz

This comment has been minimized.

Show comment
Hide comment
@kfeuz

kfeuz Nov 19, 2014

Contributor

I believe this issue has been resolved with pull request #2474 which has been merged in for some time. The exception is expected and is being properly caught. We still report the exception as "Server SocketException: Socket closed" if you want a different message or no message I would be happy to submit a new pull request. Otherwise I think this issue can be closed.

Contributor

kfeuz commented Nov 19, 2014

I believe this issue has been resolved with pull request #2474 which has been merged in for some time. The exception is expected and is being properly caught. We still report the exception as "Server SocketException: Socket closed" if you want a different message or no message I would be happy to submit a new pull request. Otherwise I think this issue can be closed.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Nov 19, 2014

Member

Great, thanks for checking into it.

Member

benfry commented Nov 19, 2014

Great, thanks for checking into it.

@benfry benfry closed this Nov 19, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment