Hi Mark,
Your report is very interesting. I do quite a bit of maintenance on
logging and digester, and a little on beanutils, so would definitely be
keen to figure out what's going on here.
It would help if you could provide more details on exactly what
behaviour you are seeing. In particular,
Simon Kitching wrote:
It would help if you could provide more details on exactly what
behaviour you are seeing. In particular, are you seeing this exception
immediately on startup of a fresh Tomcat install, or is it *any* webapp
that triggers this, or a specific one? It will be easiest to
Mark Thomas wrote:
You say you've tried commons-logging 1.1.0. Can you please confirm for
me that you replaced the commons-logging.jar file in $TOMCAT_HOME/lib
with the commons-logging-api.jar from the binary download of
commons-logging 1.1? You might want to try setting the following
Hi Mark,
Firstly, the 1.1.0 release of commons-logging will hopefully not have
this problem; you don't indicate what version of commons-logging is
present when this problem occurs. Could you try upgrading the JCL
implementation in the tomcat path to the latest version and see what
happens?
Simon Kitching wrote:
Firstly, the 1.1.0 release of commons-logging will hopefully not have
this problem; you don't indicate what version of commons-logging is
present when this problem occurs. Could you try upgrading the JCL
implementation in the tomcat path to the latest version and see what
