You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by robert burrell donkin <ro...@gmail.com> on 2006/03/21 22:10:20 UTC
Requesting volunteers to regression test commons-logging release candidate
hello one and all
JCL 1.1 is now very close to being released. we've done a lot of
testing and spent a long time analysing the code base. we think we've
solved as many of the issues with the 1.0.x series of releases which
can be without breaking compatibility.
we're now approaching some major downstream projects which have used
the 1.0.x series releases to see if anyone would be willing to run
regression tests to make sure we haven't introduced any problems with
this release. if no issues emerge then it's expected that this release
candidate will be the final one.
IIRC remy had plans for a next generation replacement (cool by me BTW,
we're just trying to fix as many problems as possible for existing
users) but i'm not really sure how advanced these plans are.
i'd be very grateful if volunteers woul step up to regression test the
latest release candidate (RC6) as a replacement for whichever 1.0.x
release is used against as many tomcat versions as possible. it's
available in cvs.apache.org/repository and from
http://people.apache.org/~rdonkin/commons-logging.
TIA
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Requesting volunteers to regression test commons-logging release candidate
Posted by robert burrell donkin <ro...@gmail.com>.
On 3/23/06, Remy Maucherat <re...@apache.org> wrote:
> robert burrell donkin wrote:
> > hello one and all
> >
> > JCL 1.1 is now very close to being released. we've done a lot of
> > testing and spent a long time analysing the code base. we think we've
> > solved as many of the issues with the 1.0.x series of releases which
> > can be without breaking compatibility.
> >
> > we're now approaching some major downstream projects which have used
> > the 1.0.x series releases to see if anyone would be willing to run
> > regression tests to make sure we haven't introduced any problems with
> > this release. if no issues emerge then it's expected that this release
> > candidate will be the final one.
> >
> > IIRC remy had plans for a next generation replacement (cool by me BTW,
> > we're just trying to fix as many problems as possible for existing
> > users) but i'm not really sure how advanced these plans are.
>
> I'd be interested to know what were those cool NG plans :D
in that case, it's probably one of those rumours things :)
for some reason using java.util logging and supporting log4j through a
java.util logging provider (i believe boris unckel has one of these
beasts more or less working now) springs into my mind but that's
probably my well known overactive imagination at work...
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Requesting volunteers to regression test commons-logging release candidate
Posted by robert burrell donkin <ro...@gmail.com>.
On 3/23/06, Remy Maucherat <re...@apache.org> wrote:
> Remy Maucherat wrote:
> > Ok, I tested it by replacing my existing commons-logging-api in the bin
> > folder, and it doesn't behave as it was before. For some reason, it
> > doesn't seem to be using java.util.logging by default anymore (I have no
> > other logging framework installed anywhere).
>
> Forget it, I found out why: it's simply that the java.util.logging is
> not in the -api JAR anymore. So it is not a drop in update for Tomcat,
> as I think we'll have to do some repackaging.
or maybe we reconsider the packaging. i'll revisit the email archives
and see whether this decision was taken for good enough reasons.
cheers :)
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Requesting volunteers to regression test commons-logging release
candidate
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> Ok, I tested it by replacing my existing commons-logging-api in the bin
> folder, and it doesn't behave as it was before. For some reason, it
> doesn't seem to be using java.util.logging by default anymore (I have no
> other logging framework installed anywhere).
Forget it, I found out why: it's simply that the java.util.logging is
not in the -api JAR anymore. So it is not a drop in update for Tomcat,
as I think we'll have to do some repackaging.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Requesting volunteers to regression test commons-logging release
candidate
Posted by Remy Maucherat <re...@apache.org>.
robert burrell donkin wrote:
> hello one and all
>
> JCL 1.1 is now very close to being released. we've done a lot of
> testing and spent a long time analysing the code base. we think we've
> solved as many of the issues with the 1.0.x series of releases which
> can be without breaking compatibility.
>
> we're now approaching some major downstream projects which have used
> the 1.0.x series releases to see if anyone would be willing to run
> regression tests to make sure we haven't introduced any problems with
> this release. if no issues emerge then it's expected that this release
> candidate will be the final one.
>
> IIRC remy had plans for a next generation replacement (cool by me BTW,
> we're just trying to fix as many problems as possible for existing
> users) but i'm not really sure how advanced these plans are.
I'd be interested to know what were those cool NG plans :D
> i'd be very grateful if volunteers woul step up to regression test the
> latest release candidate (RC6) as a replacement for whichever 1.0.x
> release is used against as many tomcat versions as possible. it's
> available in cvs.apache.org/repository and from
> http://people.apache.org/~rdonkin/commons-logging.
Ok, I tested it by replacing my existing commons-logging-api in the bin
folder, and it doesn't behave as it was before. For some reason, it
doesn't seem to be using java.util.logging by default anymore (I have no
other logging framework installed anywhere).
The output looks like this:
[INFO] Http11AprProtocol - Initialisation de Coyote HTTP/1.1 sur http-8080
[INFO] AjpAprProtocol - Initializing Coyote AJP/1.3 on ajp-8009
[INFO] Catalina - Initialization processed in 861 ms
[INFO] StandardService - DÚmarrage du service Catalina
[INFO] StandardEngine - Starting Servlet Engine: Apache Tomcat/5.5.0-dev
[INFO] StandardHost - XML validation enabled
[INFO] balancer] - org.apache.webapp.balancer.BalancerFilter: init():
ruleChain: [org.apache.webapp.balancer.RuleChain:
[org.apache.webapp.balancer.ru
les.URLStringMatchRule: Target string: News / Redirect URL:
http://www.cnn.com],
[org.apache.webapp.balancer.rules.RequestParameterRule: Target param
name: paramName / Target param value: paramValue / Redirect URL:
http://www.yahoo.com],
[org.apache.webapp.balancer.rules.AcceptEverythingRule: Redire
ct URL: http://jakarta.apache.org]]
[INFO] jsp-examples] - ContextListener: contextInitialized()
[INFO] jsp-examples] - SessionListener: contextInitialized()
[INFO] servlets-examples] - ContextListener: contextInitialized()
[INFO] servlets-examples] - SessionListener: contextInitialized()
[INFO] Http11AprProtocol - DÚmarrage de Coyote HTTP/1.1 sur http-8080
[INFO] AprEndpoint - Failed to create poller with specified size of 16384
[INFO] AjpAprProtocol - Starting Coyote AJP/1.3 on ajp-8009
[INFO] StoreLoader - Find registry server-registry.xml at classpath resource
[INFO] Catalina - Server startup in 4257 ms
This output is an integrated logger, right ?
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Requesting volunteers to regression test commons-logging release candidate
Posted by robert burrell donkin <ro...@gmail.com>.
On 3/24/06, Costin Manolache <co...@gmail.com> wrote:
>
> An alternative is to use the 'no discovery, no plugins, no layers'
> implementation of commons-logging
> that we have in sandbox :-) - which just implements the commons-logging
> APIs
> hardcoding everything to java.util.logging. People who want log4j or
> another
> logger can replace
> the jar with the 'official' discovery-based implementation if they need
> it.
>
> There are a lot of benefits of having a logger with discovery and a
> mini-logger if no real logger is found, but
> for tomcat we know java.util will be found, and it avoids a lot of
> problems
> to just use the hardcoded one.
+1
sounds like a good plan
static binding has many advantages especially when dealing with high level
classloaders. it should also be much more preformant. i'll check out the
sandbox this weekend and double check the implementation for any known
issues with static binding JCL implementations.
if a user deploys a web application that uses and ships with JCL, then AFAIK
when deployed in a parent-last classloader the dynamic discovery mechanism
should work fine.
may need to check that the workaround put in place for the hot deployment
memory leak functions ok with the proposed configuration.
- robert
Re: Requesting volunteers to regression test commons-logging release candidate
Posted by Costin Manolache <co...@gmail.com>.
An alternative is to use the 'no discovery, no plugins, no layers'
implementation of commons-logging
that we have in sandbox :-) - which just implements the commons-logging APIs
hardcoding everything to java.util.logging. People who want log4j or another
logger can replace
the jar with the 'official' discovery-based implementation if they need it.
There are a lot of benefits of having a logger with discovery and a
mini-logger if no real logger is found, but
for tomcat we know java.util will be found, and it avoids a lot of problems
to just use the hardcoded one.
Costin
On 3/21/06, robert burrell donkin <ro...@gmail.com> wrote:
>
> hello one and all
>
> JCL 1.1 is now very close to being released. we've done a lot of
> testing and spent a long time analysing the code base. we think we've
> solved as many of the issues with the 1.0.x series of releases which
> can be without breaking compatibility.
>
> we're now approaching some major downstream projects which have used
> the 1.0.x series releases to see if anyone would be willing to run
> regression tests to make sure we haven't introduced any problems with
> this release. if no issues emerge then it's expected that this release
> candidate will be the final one.
>
> IIRC remy had plans for a next generation replacement (cool by me BTW,
> we're just trying to fix as many problems as possible for existing
> users) but i'm not really sure how advanced these plans are.
>
> i'd be very grateful if volunteers woul step up to regression test the
> latest release candidate (RC6) as a replacement for whichever 1.0.x
> release is used against as many tomcat versions as possible. it's
> available in cvs.apache.org/repository and from
> http://people.apache.org/~rdonkin/commons-logging.
>
> TIA
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>