Ah good. That makes sense - I was trying to see in the latest source code where this stems for and simply couldn't figure it out...
BTW, I agree it is a bit strange. I only did it because I wanted to get a stack trace and the debug methods don't allow supplying an exception. But indeed I've replaced it with a string parameter that details the stack trace, so I can use a debug method, which makes both the source code and the logs more readable. Anyway thanks a lot! On Fri, Aug 29, 2014 at 9:43 AM, Patrik Nordwall <[email protected]> wrote: > Using log.isDebugEnabled followed by log.error is a bit strange in my > opinion. > > Anyway, what you are looking for was solved here: > https://github.com/akka/akka/pull/15413 > > It is not released yet. > > Cheers, > Patrik > > > On Thu, Aug 28, 2014 at 1:35 PM, Adam <[email protected]> wrote: > >> Hi, >> >> One more follow up question. >> When using the setting advised by the documentation for this scenario ( >> http://doc.akka.io/docs/akka/snapshot/java/logging.html#SLF4J) the only >> real gap from what I need is that with akka.logLevel set to DEBUG and with >> the SLF4J binding configured to INFO, writing code like this: >> >> >> if (logger.isDebugEnabled()) { >> logger.error("This is an error"); >> } >> >> >> Will cause the above error to be logged, which isn't really what I'd >> expect to happen (I'd expect nothing to be logged). >> >> If I were to use the event bus to circumvent this, it would probably >> resolve many cases of this happening (depending on how often this code is >> reached and how often I’d be polling the configuration), but it wouldn’t >> really make this go away. >> So should I really go down this road, or is this really a bug that could >> be fixed in Akka? >> Or maybe this is actually an intended limitation? >> >> -- >> >>>>>>>>>> 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. >> > > > > -- > > Patrik Nordwall > Typesafe <http://typesafe.com/> - Reactive apps on the JVM > Twitter: @patriknw > > -- > >>>>>>>>>> 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 a topic in the > Google Groups "Akka User List" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/akka-user/zTzAKjkQ5tc/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- >>>>>>>>>> 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.
