Hello, I've been wondering whether it's possible to get underlying exception in Tcp.CommandFailed on Bind? Looking at
https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/io/TcpListener.scala#L63 I see all exceptions getting caught and logged but not passed to the CommandFailed message. With jdk1.8.0_25's ServerSocket.java, there could be multiple failure outcomes: - socket is closed - already bound - unsupported address type - unresolved address - a SecurityException - an IOException which most of the time would mean "address already in use" I would very much like to get this information back to my higher-level code, for example by adding the NonFatal(e) exception to the Tcp.CommandFailed somehow. Am I missing something here, or would that require patching Akka? Thanks. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
