Since the log source is specified directly as a String by the 
LocalActorRefProvider the originating class name is 
«akka.event.DummyClassForStringSources». The reason is that this LogAdapter 
needs to be initialized before the ActorSystem is up and running; we could 
potentially use LogSource.fromClass instead, but that would then not identify 
the ActorSystem’s address anymore in all cases (especially during start-up 
where it might be rather interesting). Another possibility would be to add a 
specific LogSource for this case; if the DummyClass… does not suffice for your 
purposes, could you file a ticket?

Thanks for raising this,

Roland

> 15 jun 2015 kl. 22:31 skrev GG <[email protected]>:
> 
> Just to put this in perspective, this logging line generated 6.5GB of logs in 
> about 10 minutes on one of our machines so it's more than just an annoyance 
> for us.
> 
> 
> 
> On Monday, June 15, 2015 at 12:30:38 PM UTC-7, GG wrote:
> I've got a pretty good handle on configuring Akka logging through a 
> logback.xml file. Almost everything is logging as configured with the 
> exception of LocalActorRefProvider. My system is configured using 
> akka-cluster and it seems that each attempt to look up an actor first goes 
> through LocalActorRefProvider which insists on logging a message about failed 
> path resolution:
> 
> [debug] LocalActorRefProvider(akka://ClusterSystem) - resolve of path 
> sequence [/user/token-mgr-proxy/TokenManager#396699396] failed
> 
> My logs are littered with these and similar lines. I can't seem to find a way 
> to control the logging from just this one class. I've  muted everything from 
> package akka.actor in my logback.xml and event tried referencing this class 
> directly via its FQCN and via short name (notice it's not printing a FQCN in 
> the log line even though my logback.xml is configured to do so).
> 
> Has anyone else run into this problem or have any ideas on how I might be 
> able to resolve the issue?
> 
> 
> -- 
> >>>>>>>>>> Read the docs: http://akka.io/docs/ <http://akka.io/docs/>
> >>>>>>>>>> Check the FAQ: 
> >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html 
> >>>>>>>>>> <http://doc.akka.io/docs/akka/current/additional/faq.html>
> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user 
> >>>>>>>>>> <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 [email protected] 
> <mailto:[email protected]>.
> To post to this group, send email to [email protected] 
> <mailto:[email protected]>.
> Visit this group at http://groups.google.com/group/akka-user 
> <http://groups.google.com/group/akka-user>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.



Dr. Roland Kuhn
Akka Tech Lead
Typesafe <http://typesafe.com/> – Reactive apps on the JVM.
twitter: @rolandkuhn
 <http://twitter.com/#!/rolandkuhn>

-- 
>>>>>>>>>>      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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to