was the LGPL chosen as the license to
employ for Logback?
--
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
___
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo
are definitely interested.
Happy new year,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
___
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user
on a marker value. However, it turns out that this is not
possible in practice. Thus, in the current code of logback
isDebugEnabled(Marker) simply delegates to isDebugEnabled().
Thanks for your help,
Thanks for your interest in logback,
Yoram
--
Ceki Gülcü
Logback: The reliable, generic
___
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
___
Logback-user mailing list
developing a project (www.sf.net/projects/ohla)
that has both a library (for clients) and an executable (server).
Best wishes for the ohla project.
Thanks,
Michael
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
could put together to do the
right thing. I'm not yet familiar enough with logback to answer that
myself, so your input is appreciated.
anders
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
Hello all,
I am happy to announce the immediate availability of logback version
0.9.18, consisting mainly of bug fixes and minor enhancements. After a
very long investigation resulting in somewhat a better understanding
of licensing issues, logback is now dual-licensed under the EPL 1.0
and LGPL
I am having trouble understanding your quesiton.
The LoggerContext.stop and LoggerContext.reset are closely related, except that
the former also calls marks the LoggerContext as stopped.
ContextDetachingSCL is only needed when a ContextSelector has been installed
because in that case the
Hello Jorge,
From the status messages you provided, it looks like an IO failure has occurred
and that RollingFileAppender is having trouble falling back on its feet. I'd be
suprised if log4j fared any better in the presence of the same IO failure but I
might be wrong.
Anyway, I have created
Hello Klaus,
The error message is pretty informative. DBAppender cannot function if
the JDBC driver does not support getGeneratedKeys method *and* without
a specific SQL dialect. As it appears that H2 does not support the
getGeneratedKeys method, an H2-specific dialect is required which at
should be pretty trivial.
[1] http://www.h2database.com/h2.pdf
On 28/01/2010 7:39 AM, Ceki Gülcü wrote:
Hello Klaus,
The error message is pretty informative. DBAppender cannot function if
the JDBC driver does not support getGeneratedKeys method *and* without
a specific SQL dialect
Hello Aleksey,
What you describe would be a pretty useful feature to have. Can you please enter
an enhancement request on our jira?
Best regards,
On 01/02/2010 11:12 AM, Aleksey Didik wrote:
Hello all,
I need to name my log file as /${host-name}.log/ and the question is,
how can I do it?
Assuming jetty uses child-first a.k.a. local-first class loading order, I would
recommend to bundle slf4j and logback jar in your war file.
Jetty used to have the opposite class loading order, i.e. parent-first, but I am
under the impression that it changed to local-first class loading in
for this strategy but it does not
affect slf4j users, unless of course they are using log4j or if they are using
jcl-over-slf4j.
Yes, it's complicated...
[1] http://docs.codehaus.org/display/JETTY/Classloading
On 04/02/2010 9:41 AM, Ceki Gülcü wrote:
Assuming jetty uses child-first a.k.a. local-first
in any feedback as to how it behaves in the wild.
On 23 Feb 2010, at 12:07, Ceki Gülcü wrote:
Hello Gilles,
If as Nikolas suspects, swing uses java.util.logging which it probably
does, then go with his suggestion of redirecting j.u.l. to SLF4J.
If for some reason swing actually writes directly
You are right. ContextBasedDiscriminator will not help you because the context
name is retreived from the LoggingEvent which ultimately gets its value from the
calling logger. If the calling logger is attached to the wrong context,
ContextBasedDiscriminator will give you the wrong context name.
In my opinion, the current thread class loader is too low level to be of use.
Retrieving values from JNDI is a bit safer (we don't have to keep around
references to class loaders) and also allows us set/get context names.
On 01/03/2010 2:00 PM, Robert Elliot wrote:
Can't you sift on
Hello Ingo,
Properties of the logger context are part of each logging event sent
to the SocketAppender. You can set a context property 'k' to value 'v'
as follows:
LoggerContext lc = (LoggerContext)
org.slf4j.LoggerFactory.getILoggerFactory();
lc.putProperty(k, v);
Are you seeing any status messages?
On 04/03/2010 3:49 PM, Mohammad Haider wrote:
Hi,
I have created three tables for logback according to documentation.
I have the following config. file:
?xml version=1.0 encoding=UTF-8?
configuration debug=true scan=true scanPeriod=30 seconds
appender
- Attaching appender
named [DB] to Logger[ROOT]
11:01:55,312 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - End of
configuration.
Ceki Gülcü wrote:
Are you seeing any status messages?
On 04/03/2010 3:49 PM, Mohammad Haider wrote:
Hi,
I have created three tables for logback
On 04/03/2010 5:59 PM, Mohammad Haider wrote:
Thank you for quick reply.
I got the following output after putting the statusListener tag
12:58:33,750 |-ERROR in ch.qos.logback.classic.db.DBAppender[DB] -
problem appending event org.postgresql.util.PSQLException: ERROR: column
EVENT_ID does
Change references from ${context} to ${contextName} as
JNDIBasedContextDiscriminator is hardwired to use the key contextName.
On 05/03/2010 12:04 AM, Ceki Gülcü wrote:
Just remove Keycontext/Key
On 05/03/2010 12:00 AM, toxel wrote:
Hello
I have a little question when I use configuration
1) You can only have *one *nested-appender within SiftingAppender.
To manage *two* nested appender families, create *two* sifted appenders.
2) FileNamePatterntbank-${contextName}.%d{-MM-dd}.log.zip looks
suspicious, it should probably be
There is no way to filter logback's internal messages by level. In general,
logback will output its internal state after it is configured and only in case
of errors or if you set debug=true in the configuration element.
Have you attached a status listener in your configuration file? For
The config file snippet looks good. I really don't see how the error you are
seeing could occur. Which version of logback are you using?
You could you also provide the whole config file?
On 10/03/2010 12:56 AM, Federico Schroder wrote:
Hello, I'm having problems trying to use the gmail
No, logback does not offer this functionality although it would be very easy to
write one. Just copy and paste threshhold filter and inverse the comparison logic.
Here it is:
public class InvertedThresholdFilter extends FilterILoggingEvent {
Level thresholdLevel;
@Override
public
Hello Matthias,
SiftingAppender tracks appenders with the help of a sub-component called
AppenderTracker. The tracker will close appenders which have not been used in
the last 30 minutes. It looks like you need to close the nested fike appender
immediately without waiting the 30 minutes.
If
Fixed in a recent commit.
On 17/03/2010 3:05 PM, Ceki Gülcü wrote:
Hello Matthias,
SiftingAppender tracks appenders with the help of a sub-component called
AppenderTracker. The tracker will close appenders which have not been
used in the last 30 minutes. It looks like you need to close
Hello Christian,
You can register a status listener which will be notified anytime a new status
message is created. See [1]. Logback ships with a listener called
OnConsoleStatusListener which prints status messages on the console. It is
installed as
configuration
statusListener
Hello all,
I am happy to announce the immediate availability of logback version
0.9.19. This version introduces a new core component called encoder
which will hopefully pave the way for various new exciting features.
Please refer to the the news page for precise details.
Hello Matthieu,
The encoding property has been renamed as Charset and now is part of the
encoder. The config file snippet becomes:
appender name=STDOUT class=ch.qos.logback.core.ConsoleAppender
encoder
pattern%d %t [%-5level] - %-40class{40} - %msg%n/pattern
charsetUTF-8/charset
Hello Ted,
Could you please file a bug report with a test case?
TIA,
On 25/03/2010 6:18 PM, Ted Meng wrote:
Hi:
I put an include directive in my logback.xml
configuration
include file=includedConfig.xml /
/configuration
the includedConfig.xml is in the same directory (classpath)
as the
If you wish to reference a resource on the class path, use the resource
attribute. Example:
configuration
include resource=includedConfig.xml/
/configuration
This is already explained in the docs but not very explicitly.
On 25/03/2010 6:18 PM, Ted Meng wrote:
Hi:
I put an include
report for file type
Ceki Gülcü wrote:
If you wish to reference a resource on the class path, use the
resource attribute. Example:
configuration
include resource=includedConfig.xml/
/configuration
___
Logback-user mailing list
Logback-user@qos.ch
Hi Joern,
I'll add jdbcdslog to the list of slf4j based projects on
http://slf4j.org/download.html
On 31/03/2010 11:52 AM, Joern Huxhorn wrote:
I've just seen this this post on theserverside.com.
It looks quite interesting and is using SLF4J as the logging framework.
On 01/04/2010 12:41 PM, WM YEOH wrote:
Hi Ceki,
Thank you for the guidance.
I think I better start all over again what was the actual problem to give
you a better picture.
I am currently upgrading the sun one apps server from 7.1 to 9.1 (in UNIX
platform), common-logging.jar,
Hello all,
I am happy to announce the immediate availability of logback version
0.9.20. In addition to bug fixes, this version introduces conditional
processing of configuration files.
Please refer to the the news page for precise details.
http://logback.qos.ch/news.html
You can download
Hello Ted,
Could you post your configuration file?
On 03/04/2010 3:07 AM, Ted Meng wrote:
Hello:
when the log needs to be rotated often, many temporary files
like *.tmp are being produced and left there forever.
I saw the following mailing thread and did not see futher info
Hello Albert,
Have you looked at SiftingAppender [1]? All you need is to insert the request so
that your custom discriminator makes use of it. You could even use the
MDCBasedDiscriminator which ships with logback. In a servlet filter just insert
the request id into the MDC and let
visit the following URL.
http://qos.ch/mailman/listinfo/announce
--
Ceki Gülcü
Logback: The reliable, fast and flexible logging framework for Java.
http://logback.qos.ch
___
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo
Hello Edwin,
The chapter on logging separation [1] should be helpful, in particular
the section entitled Taming static references in shared libraries.
HTH,
[1] http://logback.qos.ch/manual/loggingSeparation.html
On 28/04/2010 4:56 PM, Dhondt, Edwin wrote:
I've got 4 web applications. They
-user-boun...@qos.ch] On
Behalf Of Ceki Gülcü
Sent: woensdag 28 april 2010 17:28
To: logback users list
Subject: Re: [logback-user] Log separation
Hello Edwin,
The chapter on logging separation [1] should be helpful, in particular
the section entitled Taming static references in shared libraries
-
From: logback-user-boun...@qos.ch [mailto:logback-user-boun...@qos.ch] On
Behalf Of Ceki Gülcü
Sent: woensdag 28 april 2010 17:50
To: logback users list
Subject: Re: [logback-user] Log separation
The example is not wrong. You probably read the chapter too quickly.
On 28/04/2010 5:41 PM
On 28/04/2010 9:10 PM, Chris Helck wrote:
Thanks, this seems to be what I'm looking for, but I'm having a few problems.
1. I've checked the source code and I only see ListAppender being used in
AppenderTrackerTest and StringListAppender. You said it's is used extensively,
am I missing
On 29/04/2010 2:14 AM, Ralph Goers wrote:
I find myself wondering if you really want what you say you do. If
you want to be able to view all the activity for a particular webapp a
very practical way to do this is to use a tool like Splunk that can
aggregate all the log data and then report
On 29/04/2010 9:33 AM, Ralph Goers wrote:
What you are asking to do can be done by having a logger for the
classes in the common jar (presumably they are all using the same
package name at some level) that is configured with 2 appenders. Each
appender is then configured with a filter so
On 29/04/2010 8:59 AM, Dhondt, Edwin wrote:
[snip]
That is, coming back to the starwars example when I open the yoda.log
I only want to see log messages produced in the context of running the
Yoda webapp. That is, when I open the kenobi.log I only want to see
log messages produced in the
On 29/04/2010 10:55 AM, Dhondt, Edwin wrote:
So can I be sure that when following all the steps in [1] the yoda
web-app will only write to yoda.log and the Kenobi web-app will only
write to Kenobi.log indepent on which application is started first and
calls the shared code the first ? That
You should add the following to the beginning of your config file to see
logback's attempts, if any, at deleting the files:
statusListener
class=ch.qos.logback.core.status.OnConsoleStatusListener /
Is your application long-lived or short-lived? Does it come up for a
short while and shut
Were you able to solve it?
On 23/05/2010 2:53 PM, Joel Rosi-Schwartz wrote:
Hi,
I have a bit of strange problem that I do not understand at all.
I am working on sorting out a bit of a nightmare at work. We have 100s
of project that get mixed in various way into applications packaged in
war's
Hello all,
I am happy to announce the immediate availability of logback version
0.9.23, a maintenance release containing only bug fixes.
Please refer to the the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full source code, class files
Hi Lance,
If your config file is called logback.groovy, logback will
automatically pick it up. To programmatically invoke a groovy config
file, you would need to work with GafferConfigurator as Joran only
deals with XML files, not Groovy. You would write:
import
The run method expects a URL, a File or the script itself (as a String).
Try this:
gafferConfigurator.run(new File(c:/tmp/aaa.groovy));
On 30/06/2010 3:43 PM, Lance White wrote:
Afraid not...
I seem to get a variety of errors depending on what the script file is...
With a script file
Hello all,
Just a day after 0.9.23, I am happy to announce the immediate
availability of logback version 0.9.24, a maintenance release
containing only bug fixes.
Please refer to the the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full
Andreas,
Thank you for this report. I believe the same issue was reported in
http://jira.qos.ch/browse/LBCORE-155
Cheers,
On 05/07/2010 8:27 AM, Andreas Dejung wrote:
I had the same problem and I think I know why J
Solaris does interrupt IO blocked thread which then causes the
Hi Sander,
ContextSelector is one way of demultiplexing events per
bundle. Another way is through SiftingAppender (or GSiftingAppender
its equivalent in Groovy) which might be more convenient to use.
Regardless of whether you use ContextSelector or
SiftingAppender/GSiftingAppender, you first
On 07/07/2010 4:41 PM, David Savage wrote:
Hi there,
I've just run into a problem with using logback in a jvm where the
security manager is enabled. The trace of the exception is as follows:
java.security.AccessControlException: access denied
(java.lang.RuntimePermission getClassLoader)
at
I believe that the consumption of the interrupt flag by java.io code
*only* occurs on Solaris, even then, you can prevent that behavior by
starting the JVM with the -XX:-UseVMInterruptibleIO option.
Given that the issue is Solaris-specific and preventable with the
-XX:-UseVMInterruptibleIO
Hello Greg,
Assuming that the development host is different than the production
host, you can use conditional statements in logback.groovy to cater
for both environments. This is what we now do internally at QOS.ch and
find it more convenient than having two distinct config files.
Holler if you
Hi Steve,
I guess Joern could answer your question most authoritatively since he
knows Lilith best.
On 09/07/2010 5:02 PM, Steve Johnson wrote:
Greetings,
I apologize in advance if my question is obviously documented somewhere
already. If so, I haven't been able to find those docs and
Hi Joern, Hi Robert,
Thank you both for your comments.
To my understanding, Thread.interrupt is an intrathread communication
mechanism which does not work on most environments, e.g. Windows and
Linux. Thus, most code would use intra-thread communication mechanism
*other* than Thread.interrupt.
Thank you for sharing this info.
On 12/07/2010 2:06 PM, Joern Huxhorn wrote:
I've just realized that the current JVM on Mac is also throwing
InterruptedIOException
ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
at
On 12/07/2010 4:49 PM, Sander de Groot wrote:
Ah i see. Maybe the SiftingAppender is even a better option!
But even with the SiftingAppender the problem is the same, like you said
I need a way to differentiate between bundles.
I'd like to differentiate based on the bundle name (or symbolic
Hi Espen,
As far as performance goes, using a turbo filter would not bring any
benefits (as in zero benefit) which goes to explain why appenders take
regular filters a not turbo filters. As Ralph ruggested earlier, just
use a regular filter and you will be fine.
On 13/07/2010 3:53 PM, Espen
Hi Jesse,
See the chapter on logback architecture [1] for the interaction of
loggers and appenders. You might also find the chapter on filters [2].
The MDC [3] and SiftingAppender [4] combination is a very powerful
alternative to the traditional combination of loggers and appenders.
[1]
When you are sure that the underlying framework is logback, you can cast
an org.slf4j.Logger instance into ch.qos.logback.classic.Logger. The
latter has a method to retrieve an appender by name [1].
I hope this helps,
[1]
The line numbers in the stack trace you sent indicate an earlier version
of logback, probably version 0.9.20 or 0.9.21.
In the past we also ran into problems while testing SMTPAppender with
SubethaSMTP. If my memory serves me correctly, it was due to a race
condition. Maybe the server is
On 23/07/2010 5:46 PM, Jeff Jensen wrote:
Hi Ceki, thanks for the reply.
Welcome.
Yes, I upgraded to 0.9.24 while investigating this problem. I must have
captured the stack before that.
OK.
I wondered about a race condition too. To try mitigate that at
SubethaSMTP start/shutdown, I added
Hello Omar,
You are perhaps not familiar with the the restrictions that apply to
RollingFileAppender in prudent mode. These restrictions are documented
at: http://logback.qos.ch/manual/appenders.html#prudentWithRolling
HTH,
On 23/07/2010 8:06 PM, Omar Alrubaiyan wrote:
(oops, re-posting
On 24/07/2010 12:36 AM, Omar Alrubaiyan wrote:
I'm not running the logger in prudent mode, there's only one logger
object running on one JVM which receives RMI calls. Infact, I did try
turning on prudent mode to see if it made a difference and the logger
stopped outputting any log
In logback the Level class is final and cannot be extended. However, you
can use markers instead. Markers are part of the SLF4J API.
What does your custom level do?
On 28/07/2010 5:04 PM, Lars Fischer wrote:
Hello,
I would like to switch an existing system from log4j to Logback. The
SMTPAppender now manages multiple buffers simultaneously, sending only
the relevant buffer in case of a triggering event (usually an error).
Thus, you can have SMTPAppender send you an email containing the events
for the current user. Anyway, if you wish to have the buffer size
settable to
Interesting. The only explanation I would have for this behavior would
be OS support in append mode (when you set the append property to true).
Which JDK are you using?
On 27/08/2010 8:11 PM, Becker, Thomas wrote:
I had a question about multiple JVMs writing to a single logfile. I’m
aware of
Hi Melchior,
It's indeed a bug. Thank you. I just corrected it in git. Fortunately,
while TRACE_INT is used all over the code, TRACE_INTEGER is only used by
JaninoEventEvaluator so it's not as serious a bug as it could be.
Cheers,
On 02/09/2010 4:40 PM, o...@mrab.de wrote:
Hi all,
I'm
On 06/09/2010 10:09 PM, Jeff Jensen wrote:
Heh, due to one of my fav things of Logback (parametric logging), there are
no if(logger.isDebugEnabled()) calls in the codebase (makes me happy).
But that does lead to an idea I looked into a bit of what is logged/what are
methods called for the
On 06/09/2010 11:31 AM, Ari Meyer wrote:
Thanks Ralph -- good to see Ceki's response to the same question, albeit
2 yrs earlier. Makes me think I should have voiced my justifications
for a 1.0 label years ago, as doubtless many people are likewise waiting
for 1.0 to try out logback, but get by
Hi Bob,
It looks like you forgot to invoke start() on the rolling policy instance.
HTH,
On 15/09/2010 3:32 AM, Bob DeRemer wrote:
Hi Logback community,
I hope the problem is operator error, but I can’t seem to figure this
out. My java webapp requirements are such that we need to
In the getResourceOccurenceCount method of the
ch.qos.logback.core.util.Loader class, it is assumed that the
getResource method of the class loader instance will return a non-null
enumeration. This assumption does apparently not hold in Felix.
Please enter a bug report so that we can fix the
Hello all,
I am happy to announce the release of logback version 0.9.25. Please
refer to the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full source code, class files and
documentation on our download page, shown below.
Hello,
Have a look at
http://logback.qos.ch/manual/configuration.html#cumulative
and
http://logback.qos.ch/manual/configuration.html#overrridingCumulativity
HTH,
On 14/10/2010 12:58 PM, LongkerDandy wrote:
Hi
I've write a config like this
configuration
appender name=Chii2FILE
Hello all,
I am happy to announce the release of logback version 0.9.26. Please
refer to the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full source code, class files and
documentation on our download page, shown below.
There are several waays to make logback, spring and slf4j to work
together. Here is the simplest maven dependency declaration which is
known to work nicely.
dependencies
dependency
groupIdorg.springframework/groupId
artifactIdspring-context/artifactId
Hello Dawson,
Contrary to spring for example, logback relative paths are relative to
the current working directory and not relative to the referencing file.
HTH,
On 08/11/2010 3:37 PM, Dawson Mossman wrote:
Has anyone had to do this type of thing before? If I cannot use a
relative path, are
directory whereas .../x.txt designates the file
x.txt located one directory above the current working directory,
../../x.txt designates -- well you get the idea.
On 08/11/2010 3:52 PM, Ceki Gülcü wrote:
Hello Dawson,
Contrary to spring for example, logback relative paths are relative to
the current
Hi Nikhil,
Are you sure the slowness is due to logback? What happens when you
replace logback-classic.jar with slf4j-nop.jar?
On 19/11/2010 7:35 PM, nikhil diwan wrote:
Hi,
I have a startup_batch file in which I make a call to JAVA application
which is responsible for starting up my
Hello Colm,
You could add a filter into the nested appender so that when the value
for the MDC key isolatedLogName is null, the event is denied. For example,
appender name=SIFTER
class=ch.qos.logback.classic.sift.SiftingAppender
discriminator
keyisolatedLogName/key
What do you mean by Tomcat logs? The http access log?
If so, please see http://logback.qos.ch/access.html
On 02/12/2010 6:54 PM, Pradnya Gawade wrote:
Hi,
I want to get the tomcat logs through logback. I got following
reference related to it and planning to try it, the only difference in
my
Hello all,
I am happy to announce the release of logback version 0.9.27. Please
refer to the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full source code, class files and
documentation on our download page, shown below.
Hello Jonas,
It looks good to me. Here are few suggestions:
1) Try the latest version of logback
2) In FileNamePattern change all backward slashes to forward slashes
HTH,
On 12/01/2011 2:31 PM, Jonas Pacheco wrote:
Forgot to mention: logback-0.9.19
2011/1/12 Jonas Pachecojo...@kidux.com.br:
Try adding a status listener:
configuration
statusListener
class=ch.qos.logback.core.status.OnConsoleStatusListener /
...
/configuration
See also http://logback.qos.ch/manual/configuration.html#statusListener
On 13/01/2011 8:19 AM, Sumanth Donthi wrote:
Do not see records logging
Hi Olivier,
Adding a status listener is usually a good idea:
configuration
statusListener
class=ch.qos.logback.core.status.OnConsoleStatusListener /
...
/configuration
Then see what logback is telling you.
HTH,
--
Ceki
On 23/01/2011 10:47 AM, Olivier Catteau wrote:
Hello,
I'd like
Hello Markus,
Logback-access requires the Tomcat valve. Are you confusing
logback-access and the JNDIContextSelector? The latter is a
logback-classic feature and independent of logback-access.
Is there a copy of slf4-api.jar or logback-classic.jar in your web-app?
On 25/01/2011 8:52 PM,
I forgot to mention that conditional processing requires the janino
library.
On 25/01/2011 7:53 PM, Ceki Gülcü wrote:
Hello Michael,
Adding a status listener is usually a good idea:
configuration
statusListener
class=ch.qos.logback.core.status.OnConsoleStatusListener /
...
/configuration
Hi Markus,
ContextSelectors intervene during logger retrieval. However, since
logback-access does not have a notion of loggers, ContextSelectors do
not work with logback-access. You could use filters to separate logs per
web-app.
As for status information appearing twice, do you have both
Without janino.jar on your class path, did logback configuration fail
silently?
On 25/01/2011 9:26 PM, Michael C Rosenstein wrote:
On 1/25/2011 14:58, Ceki Gülcü wrote:
I forgot to mention that conditional processing requires the janino
library.
Yes! Adding janino.jar and commons
Hello all,
I am happy to announce the release of logback version 0.9.28. Please
refer to the news page for precise details.
http://logback.qos.ch/news.html
You can download logback, including full source code, class files and
documentation on our download page, shown below.
Hi Gunnar,
Conditionals (if/then/else) in logback.xml require the janino
library. Do you have conditionals in your logback.xml?
On 29/01/2011 6:02 PM, Gunnar Eketrapp wrote:
Hi!
I have problems getting my webapp to start under tomcat6.
I am currently facing problem such as ...
Caused by:
On 26/01/2011 1:17 AM, Michael C Rosenstein wrote:
On 1/25/11 3:28 PM, Ceki Gülcü wrote:
Without janino.jar on your class path, did logback configuration fail
silently?
Yes. Also silently failed w/o commons-compiler.jar.
In the absence of Janino on the classpath, logback should now
On 08/02/2011 10:46 PM, Fabio Erculiani wrote:
I need to set a property value on my custom Logger class, and I need
to do it through logback.xml like I was able to do with log4j. If
that's not possible, fine, I'll find another way to do the same. Just
wanted to know if there would be a way from
Hi Benoit,
Including the CSS in a jar file and then including it via a custom
CssBuilder should not be a problem. Try to write one and see how it goes.
As for ExplicitCssBuilder, I think all you need is to define a String
property called cssTest, the rest should be automatically taken
care
1 - 100 of 233 matches
Mail list logo
