ssl-listener/tcp-listener custodian shutdown

[Curtis Dutton]

Are ssl-listener's and tcp-listeners' custodian aware?

I'm having a problem with some of my test's that depend upon ssl-listener. When the test fails, after the custodian that owns all of the test resources is shutdown, the listener seems to remain as upon re-running the test I get a 

 tcp-listen: listen failed

  port number: 60000

  system error: Address already in use; errno=98

Thanks,

   Curt

[Matthias Felleisen]

The third argument, reuse?, needs to be #true to get quick turnaround: http://docs.racket-lang.org/reference/tcp.html?q=tcp-listen#%28def._%28%28lib._racket%2Ftcp..rkt%29._tcp-listen%29%29

--
You received this message because you are subscribed to the Google Groups "Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
To post to this group, send email to racke...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAPChLEoW6tUVYfPxyU%2BZU7q9_1xf-vNyyVHbVo43qPtK1DOfFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Neil Van Dyke]

BTW, this could be considered a TCP or OS question, more than a Racket one.

When one wants to debug something like this, as a developer on a real
computer, one should be able to see the states of different TCP ports in
use. On GNU/Linux and some other modern Unixy OSes, for example, `lsof
-i TCP` is one way to see the states.

https://en.wikipedia.org/wiki/Transmission_Control_Protocol#Protocol_operation
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.halu101/constatus.htm

And if one wants to see traces of packets over time, including TCP
control, then run something like Wireshark or `tcpdump`. These, too,
are open source software.