BTW, generally speaking, server applications should silently ignore
ClientAbortException and not log them.
Gili
Anil Gangolli wrote:
To set the log level for a given logger/ log category, you edit
WEB-INF/classes/log4j.properties file within the exploded Roller web
app. By convention, the log categories are the fully qualified class
names of the class from which the logging is done. Whole packages can
be enabled by using the package name.
So by adding/editing a line of the form
log4j.category.class.or.package.name=LEVEL
(where you replace "class.or.package.name" with the qualified class or
package name you want and LEVEL with the level (e.g. DEBUG) that you
want, will set the level for that class or package.
You'll see some examples in the shipped log4j.properties.
--a.
Greg Hamer wrote:
Anil,
Thank you for getting back to me.
Our Roller server is a stock install so I have filed bug ROL-850 in
JIRA for the ClientAbortException on login.
Regarding the MediaCast exception, I will research it further, write
it up and file it in the JIRA. Yes, it does happen consistently with
certain URLs so I will include those urls in the bug report..
Regarding the MediaCast exceptions, could you advise me how to enable
debug logging? I ask because I see statements in the code executing
both mLogger.error() and mLogger.debug(). The code that I looked at is
based on the following error() that is both in the roller.log and in
the stdout: ERROR 2005-10-13 23:33:11,250
WeblogEntryFormAction:checkMediaCast - ERROR checking MediaCast URL
Looking at the source for the indicated method (checkMediaCast() on
WeblogEntryFormAction), I see that it includes logic to execute both
mLogger.error() and mLogger.debug(). However, as our server is
currently configured I am seeing no debug() messages.
fyi ... we will be upgrading our server as soon as Roller 1.3 is
released.
Thank you again for your assistance. In case I do not hear back from
you today, I hope that you will have an enjoyable weekend.
Best regards,
g
--
http://www.desktopbeautifier.com/