Hi Greg,
these are unrelated to Akka: logback tells you about its own initialization.
Regards,
Roland
1 feb 2014 kl. 22:15 skrev tigerfoot :
> Hello,
>
> When I fire up my ActorSystem I get a block of logs like this:
>
> 15:05:24,742 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Hello,
When I fire up my ActorSystem I get a block of logs like this:
15:05:24,742 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Could NOT find resource [logback.groovy]
15:05:24,742 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Could NOT find resource [logback-test.xml]
That was it! Thanks!
On Thursday, January 30, 2014 4:11:14 PM UTC-6, tigerfoot wrote:
>
> Hello,
>
> I'm getting the exception below from 2.3.0-RC1, triggered by this code:
>
> val cfg = ConfigFactory.parseString(s"""
> akka.remote.netty.tcp.port = $port
> spray {
> can {
> serv
Hi Tino,
Readers: WARNING, going off on a "technical"/philosophical tangent below.
(Patrik has already answered most of it from a practical perspective.)
On Sat, Feb 1, 2014 at 3:24 AM, Tino Adams wrote:
> Hi Vic
>
>
>
> On Saturday, February 1, 2014 10:09:52 AM UTC+11, √ wrote:
>
>> Hi Tino,
One thing to add here is that we prefer to talk about reliability instead of
guarantees. The practical consequence in this case is that while we reliably
deliver the Terminated message (and failures, internal signals etc.), it might
not actually get into the mailbox if you happen to configure a
