Jk2 logging

[costinm]

Hi,

A quick proposal ( vote ? ): I would like to start using commons-logging
in jk2. Right now it has println() style, but beeing able to benefit 
from the fine control that log4j ( and other loggers ) provides 
would help a lot.

If nobody oposes, I will check in a current build of commons-logging
( with the option to override it for those who like downloading 
each individual dependency ).


Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Jk2 logging

[Mladen Turk]

Hi,

Recently there was a question on the Users List about log messages in
the Apache's error.log.
I've changed the INFO logging to get logged as notice instead of warning
(cause it may be misleading as the user reported).
Now, I propose to change the every occurrence of the following:

if( ch->mbean->debug > 0 )
env->l->jkLog(env, env->l, JK_LOG_INFO, 
to the :
if( ch->mbean->debug > 0 )
env->l->jkLog(env, env->l, JK_LOG_DEBUG, 

There are lots of places in the code where the second is used, but we
should be consistent across the entire source code.
I'll make the necessary commits, as soon I finish the macro.

MT.


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Jk2 logging

[GOMEZ Henri]

>A quick proposal ( vote ? ): I would like to start using 
>commons-logging
>in jk2. Right now it has println() style, but beeing able to benefit 
>from the fine control that log4j ( and other loggers ) provides 
>would help a lot.
>
>If nobody oposes, I will check in a current build of commons-logging
>( with the option to override it for those who like downloading 
>each individual dependency ).

+1


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Jk2 logging

[Bill Barker]

- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 18, 2002 10:00 AM
Subject: Jk2 logging


> Hi,
>
> A quick proposal ( vote ? ): I would like to start using commons-logging
> in jk2. Right now it has println() style, but beeing able to benefit
> from the fine control that log4j ( and other loggers ) provides
> would help a lot.
>
> If nobody oposes, I will check in a current build of commons-logging
> ( with the option to override it for those who like downloading
> each individual dependency ).
>
+1
>
> Costin
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: Jk2 logging

[jean-frederic clere]

[EMAIL PROTECTED] wrote:
> 
> Hi,
> 
> A quick proposal ( vote ? ): I would like to start using commons-logging
> in jk2. Right now it has println() style, but beeing able to benefit
> from the fine control that log4j ( and other loggers ) provides
> would help a lot.
> 
> If nobody oposes, I will check in a current build of commons-logging
> ( with the option to override it for those who like downloading
> each individual dependency ).

+1

> 
> Costin
> 
> --
> To unsubscribe, e-mail:   
> For additional commands, e-mail: 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Jk2 logging

[Remy Maucherat]

> Hi,
>
> A quick proposal ( vote ? ): I would like to start using commons-logging
> in jk2. Right now it has println() style, but beeing able to benefit
> from the fine control that log4j ( and other loggers ) provides
> would help a lot.

+1.

> If nobody oposes, I will check in a current build of commons-logging
> ( with the option to override it for those who like downloading
> each individual dependency ).

-0.5. The current property system looks ok to me, and Tomcat itself already
depends on commons-logging (indirectly), so why do that ? If you want to do
that because of API stability concerns with commons-logging, then I think
you should postpone using it until it is a bit more stable.

Remy


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Jk2 logging

[costinm]

On Tue, 19 Feb 2002, Remy Maucherat wrote:

> > If nobody oposes, I will check in a current build of commons-logging
> > ( with the option to override it for those who like downloading
> > each individual dependency ).
> 
> -0.5. The current property system looks ok to me, and Tomcat itself already
> depends on commons-logging (indirectly), so why do that ? If you want to do
> that because of API stability concerns with commons-logging, then I think
> you should postpone using it until it is a bit more stable.

It's a matter of taste mostly. I can live with the current property 
system, but I prefer the build to be as simple as possible - 
 'checkout the tree and type ant', without downloading other 
packages, installing them, editing properties, etc. 

That's a 'taste' shared by other jakarta projects. I used to believe
it is evil, and I argued a lot against it, but it certainly has
the benefit of beeing more friendly to new contributors, who don't 
spend all day working on jk. 

An alternative is to require the user to checkout both
jakarta-commons, and j-t-c ( and maybe j-t, j-t-4 ), like
we used to do in the old days ( with jakarta-tools ).
I just want an alternative to 'download and install and configure'.

Costin







--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: Jk2 logging

[costinm]

On Mon, 8 Jul 2002, Mladen Turk wrote:

> Hi,
> 
> Recently there was a question on the Users List about log messages in
> the Apache's error.log.
> I've changed the INFO logging to get logged as notice instead of warning
> (cause it may be misleading as the user reported).
> Now, I propose to change the every occurrence of the following:
> 
> if( ch->mbean->debug > 0 )
>   env->l->jkLog(env, env->l, JK_LOG_INFO, 
> to the :
> if( ch->mbean->debug > 0 )
>   env->l->jkLog(env, env->l, JK_LOG_DEBUG, 
> 
> There are lots of places in the code where the second is used, but we
> should be consistent across the entire source code.
> I'll make the necessary commits, as soon I finish the macro.

+1

Just make sure the 'important' messages ( and errors ) are visible
in error.log, using the default Apache level.

The log has 2 filters - one is the jkLog level, and the second
is the global LogLevel in httpd.conf ( or whatever win32 uses for
the Event log ).

Costin  


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

JK2 logging with IIS

[Derrick Koes]

The documentation for setting up a logger for JK2 is below.  I've tried using 
logger.file and logger.win32 for my IIS configuration, but no luck.  Can 
someone please send the right configuration steps to configure JK2 logging with 
IIS?  I'm trying to locate a "bug" in JK (not present in JK2) by comparing logs 
as a first step.  Maybe I have a registry setting missing.

Registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi 
Redirector\2.0]
"serverRoot"="C:\\jk2-connector"
"extensionUri"="/jakarta/isapi_redirector2.dll"
"workersFile"="C:\\jk2-connector\\conf\\workers2.properties"
"logLevel"="INFO"

Thanks,
Derrick

loggers 

Any connector based on jk2, at least has a default logger, that can be reached 
using the "logger" alias, the logger used is the more appropiate for the 
plataform/server combination, Apache2 under in any platform has logger.apache2 
as default, IIS on his only platform uses logger.win32, and Any apache 1 
install uses logger.file as default.., the config file lets you change that 
defaults, you can end using logger.file in IIs i.e

The properties shared by all loggers are: Property name Default Description 
level INFO Text of the log level. Strings supported: EMERG, ERROR, INFO, DEBUG 


logger.file 

Property name Default Description 
file ${serverRoot}/logs/jk2.log Log file. XXX you may be able to change this at 
runtime, to implement rolling.  



logger.win32 

logger used in the IIS server by default, it ends at native Application Event 
Log.


logger.apache2 

Logger used in Apache2 servers, it normally in ends in error.log