Re: [akka-user] Re: Propagation of error messages for Tcp Connect

This is ticket: https://github.com/akka/akka/issues/13861 and it has been confirmed that it is to be improved. A good way to make things happen is to submit a pull request ;-) Cheers, Patrik On Tue, Jun 10, 2014 at 5:11 AM, Chad Selph wrote: > Sorry to hi-jack this 2 month old thread; but I ac

[akka-user] Re: Propagation of error messages for Tcp Connect

Sorry to hi-jack this 2 month old thread; but I actually had the same problem and having it in "DEBUG" log isn't quite enough for me. Basically there's a feature of my app that could use the failure mode for diagnostics: "timeout" in our use-case typically means someone forgot to open their fir

Re: [akka-user] Re: Propagation of error messages for Tcp Connect

Yeah actually if the debug could be turned to ERROR or even WARNING I could live with that. Of course, other users of this might consider that annoying given they might not care about seeing that in their logs. Perhaps this new reactive thing the akka team is working on makes all of this obsol

Re: [akka-user] Re: Propagation of error messages for Tcp Connect

Yea, sorry. I did not see that you have already dug the source code. On Wed, Apr 9, 2014 at 5:54 PM, Martynas Mickevičius < martynas.mickevic...@typesafe.com> wrote: > Hi Andrew, > > you can see detailed reason by turning on DEBUG log messages. > > Here is the code that handles outgoing TCP conn

[akka-user] Re: Propagation of error messages for Tcp Connect

Hi Andrew, you can see detailed reason by turning on DEBUG log messages. Here is the code that handles outgoing TCP connections: https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/io/TcpOutgoingConnection.scala#L45 -- Martynas Mickevičius Typesafe –