- logback-user - mailman3.qos.ch

Redirect stderr-stdout standard streams
by Gilles Gaillard 23 Feb '10

23 Feb '10

Hi, I'm new to logback and would like to know if the following already exist / is possible, i searched the mailing list but did not find this. I've a GUI application performing usual logging through logback (that's ok) and would ensure that any unexpected failure(s) be logged. For example, unexpected errors occuring on the swing EDT go the std err. Usually I would do this by redirecting the standard out/err streams to some file output. Note also that I would like to ensure that logs from different threads will log properly. For example, stack traces should not be mangled by other logs. I wonder it is possible to do this through the logback configuration. If not what would be the best way. Thanks, -- Gilles

1 0

Status of Jira LBCORE-131?
by laboo 19 Feb '10

19 Feb '10

Hello logbackers, I've been bitten by the issue detailed in Jira as LBCORE-131. It's a fairly serious bug as it causes a loss of data, but there have been no replies to the issue as yet. I'm just curious if incorporating the suggested fix is on the todo list? http://old.nabble.com/-JIRA--Created%3A-%28LBCORE-131%29-SizeAndTimeBasedFN… I apologize in advance if this is not the correct way to ask about Jira issues. Please advise if I'm out of order here. Thanks, Mark -- View this message in context: http://old.nabble.com/Status-of-Jira-LBCORE-131--tp27657302p27657302.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Reduce to 0, logback startup output message...
by José Juan Montiel 18 Feb '10

18 Feb '10

Hi, i read few post about how to reduce de verbosity of startup messages o logback. In "Automatic printing of status messages in case of warning or errors" of [1] write... Instead of invoking StatusPrinter programmatically from your code, you can instruct the configuration file to dump status data, even in the absence of errors. To achieve this, you need to set the debug attribute of the configuration element, i.e. the top-most element in the configuration file, as shown below. Please note that this debug attribute relates only to the status data. It does not affect logback's configuration otherwise, in particular with respect to logger levels. (If you are asking, no, the root logger will not be set to DEBUG.) in special... Please note that this debug attribute relates only to the status data. It does not affect logback's configuration. The question is? How can i reduce to 0 "logback's configuration" messages? This is a little problen, because o tomcat, this messages goes to catalina.out and make that other problems on startup where dificult to find. Any idea? Thanks. [1] http://logback.qos.ch/manual/configuration.html -- Jose Juan Montiel Martinez Eurobits Technologies Calle Musgo 3, 1ª Planta 28023 Madrid T +34-917080300 F +34-913077480 josejuan.montiel(a)eurobits.es http://www.eurobits.com

1 0

How to output all errors to console, and errors+mesgs to logfile?
by Rob 14 Feb '10

14 Feb '10

Hello, I'm a new user and struggling to achieve the following: 1) All "error" messages must go to stdout and a logfile. 2) Based on com.example.myclass level settings, messages also go to logfile. My problem is I can't get both requirement 1 and 2 working simultaneously. The following results in debug messages going to the console. Using additivity="false" results in errors from com.example.myclass not going to the console. Any suggestion is welcome! <configuration> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> ... <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> ... <logger name="com.example.myclass" level="debug"> <appender-ref ref="ROLLING"/> </logger> <root level="error"> <appender-ref ref="CONSOLE"/> <appender-ref ref="ROLLING"/> </root> </configuration> Thanks, Robert

3 3

Logback Eclipse Plugin Status?
by Jeff Jensen 08 Feb '10

08 Feb '10

The download page [0] has had "It will be upgraded in the coming weeks." on it for quite a few months. Is there a status update to share? Is it being discontinued? Regarding the statement "It expects logback version 0.9.9.", will it fail with 0.9.18? I could not find a list of Eclipse versions it should work with. Anyone using it with Galileo? I was about to just "try it", but have had problems in the past trying to recover from incompatibilities, so hesitate. Also, as a feature, we were hoping for a simple picklist of log levels (or regexp to apply to the view) to real-time filter the view vs drop incoming messages. Any plans for a plugin update site vs manual install? [0] http://logback.qos.ch/download.html

7 16

DB Appender with H2
by Klaus Teller 28 Jan '10

28 Jan '10

Hi, Have anybody succeeded in using H2 as the underlying database for the logback databse appender? I'm getting the following exception and would very much appreciate any input. Gregoire. -ERROR in ch.qos.logback.core.joran.spi.Interpreter@43:14 - RuntimeException in Action for tag [appender] java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect at java.lang.IllegalStateException: DBAppender cannot function if the JDBC driver does not support getGeneratedKeys method *and* without a specific SQL dialect at at ch.qos.logback.core.db.DBAppenderBase.start(DBAppenderBase.java:59) at at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:92) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:307) -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 2

logback equivalent to log4j SocketHubAppender
by D.M. 27 Jan '10

27 Jan '10

Hello to all, is there an equivalent in logback for the log4j Socket*Hub*Appender? We use this, to check the current logging via connecting Chainsaw to the remote logging machine from time to time. It is said, that this has very few overhead on the logging machine in the case, when no one is listening. Thanks in advance, Dieter Müller

2 1

Logback implementation for MySQL database
by Shivashankar Heggade Ramachandra Bhatt 08 Jan '10

08 Jan '10

Hi, One of our MAVEN project is using Logback and it is having requirement to store the log content into MySQL db (version 5.0). Below are my Logback configuration and the output for the same. CONFIGURATION <configuration debug="false"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>[%level] %X{module} %msg%n</pattern> </layout> </appender> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <url>jdbc:mysql://localhost:3306/logback_db</url> <user>root</user> <password>mypassword</password> <insertHeaders>true</insertHeaders> </connectionSource> </appender> <root> <level value="${ROOT_LOGGER_LEVEL}"/> <appender-ref ref="DB" /> </root> <root> <level value="${ROOT_LOGGER_LEVEL}"/> <appender-ref ref="STDOUT"/> </root> </configuration> OUTPUT IN THE CONSOLE For correct db parameters [INFO] [app-core:internal] Driver name=MySQL-AB JDBC Driver Driver version=mysql-connector-java-5.0.8 ( Revision: ${svn.Revision} ) supportsGetGeneratedKeys=true true For wrong db parameters [INFO] [app-core:internal] false The above configuration is not creating any db tables and not able to store the content. Please let me know the necessary changes to these configurations. Thanks in advance... -- Thanks and Regards Shivashankar iGATE is Ranked No. 1 in DQ-IDC best IT employer survey and Ranked No.2 by Business Today-Mercer Human Resource Consulting-TNS in a cross industry survey of Best Companies to work for in India ----------------------------------------------------------------DISCLAIMER--------------------------------------------------------- Information transmitted by this EMAIL is proprietary to iGATE Group of Companies and is intended for use only by the individual or entity to whom it is addressed and may contain information that is privileged, confidential, or exempt from disclosure under applicable law. If you are not the intended recipient of this EMAIL immediately notify the sender at iGATE or mailadmin(a)igate.com and delete this EMAIL including any attachments

1 0

Logback suddenly stopped logging
by Jorge Morales Pou 07 Jan '10

07 Jan '10

Hi cecki, >From the status messages we suspected the same as you, that it was caused by an IOException. Probably there are problems with disk (we are checking this) but the thing is that we were using log4j for 2 years now and working with no problems, and the day we switched to logback, we had this problem almost every hour (no fixed pattern here). We had do restart our application in order to get loggin back. Our disk was not full, so this is not the cause. We reverted back to log4j over slf4j, to get back logging without problems. Of course there are some differences between configuration from logback and log4j, so probably this configuration differences make it work without problem in log4j. I assume that the problem is an IOException on renaming the file that leaves the appender closed, so no more writing on this appender is possible. In our tests this didn't happen. we didn't test with as high througput as production environment, and also disks were different so the IOError might not have happened.

1 0

LoggingContext JNDI not working in Session EJB using Thread
by miguel goyena 07 Jan '10

07 Jan '10

Hi everybody: I'm starting using logback, and I have a strange behauvour of logback. I'm using LoggingContextSelect JNDI. My application es an ear deployed in JBOSS, with three WAR and a EJB session jar. One of the servlet in a WAR uses the Sesssion EJB. In the EJB Session Method I create a Thread, and start it MandarMensajes threadException = new MandarMensajes(tipo,cuantos,cadaCuanto); threadException.start(); In this thread the run method uses logback for logging. Logger logger = LoggerFactory.getLogger(this); logger.logDebug("Hola"); But the logger I get have a default context!!!!!!, not the context defined in the JNDI. Only happends this when a use the thread in the Session EJB. If I use the MandarMensajes thread in the servlet everything is correct. If I get a logger anywhere else in the EJB Session everything is correct. If I use the run() method in the EJB Session everything is correct. Even if I get the MDC objet when thread is executing, all the values I put in servlet are there; but the context is default, so it never uses my logback.xml!!!!. I don't know if it is a logback bug, or if I'm doing something wrong I don't know if I've explained myself correctly, sorry my english is poor Thanks a lot

2 3