Logging Pattern - not logging the cause

Question

Hi all,

I am having some issues with logging. After reviewing JBoss Seam source code, I believe the problem is there. I would like to see JBoss Seam migrate to SLF4J since Hibernate code already uses it.

I think the issue is I don't have log4j available and I don't have Logback configured to use JDK logging.

I guess for the time-being, I need to use one of those to get the logs functioning again.

Actually, on second thought, I will just use a static logger. The advantage of the JBoss Seam logger (once it works), is that it can process EL, but honestly, I'm not using that anywhere in my logs. It is a nice feature to have, but I can still get what I want without support for EL.

Walter

Answer 1

I don't know the answer to your question, but I found the following useful in this context.

• Printing full stack trace
• Chained Exceptions

I also think that the answer you want either depends on lowering the logging level (so that you have more detailed logs) or more detailed logging where the logger is used. That is, it has nothing to do with the format. But this is a guess and likely wrong.

Answer 2

The pattern is fine. Which version of logback are you using? Can you show the exact line of code where you issue the logging request? As in:

logger.error("some exception", e);

From the above it is not clear how logback is involved in logging the exception. You seem to be throwing an exception but not logging it...