You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "J.R. Heisey" <JR...@aol.com> on 2004/04/10 19:24:31 UTC
Jar order in classpath
What is the proper order for the jars in the class path.
Sometimes I get the error
org.apache.commons.logging.impl.Jdk14Logger.class
does not implement Log class.
Sometimes I do not get the error. I can just restart Tomcat and
the exception goes way. Is there some unsychronized threading
issue in the startup code?
I'm running the Tomcat 4.0.6 under NetBeans 3.5.1 with Struts 1.1.
Any issues there?
--
Regards,
J.R. Heisey
650.328.8687
I do not wish to be on any list used for telemarketing or mass mailings
and/or I wish to be added to any do not call or mail list.
Support anti-Spam legislation.
Join the fight http://www.cauce.org/
Support Instant Runoff Voting (IRV)
http://www.fairvote.org/irv
http://www.fairvoteca.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Jar order in classpath
Posted by Christian Bollmeyer <ja...@christianbollmeyer.de>.
On Saturday 10 April 2004 19:24, J.R. Heisey wrote:
Hi,
1. Considering the CLASSPATH issue: 'first come, first
serve'. I would suspect you may have multiple, different
versions of commons.logging in your CLASSPATH.
How that's set up exactly in your environment(s)
(Tomcat uses a separate one), I can't tell from here.
2. IMHO threading issues are not in play here, as
unimplemented interfaces would show up at
compilation stage. Therefore, the version used
by the NetBeans environment obviously implements
the Log interface, while the one used by the
integrated Tomcat does not. Just guessing,
though. The usual starting point would be
checking /WEB-INF/lib.
HTH,
-- Chris.
> What is the proper order for the jars in the class path.
> Sometimes I get the error
> org.apache.commons.logging.impl.Jdk14Logger.class
> does not implement Log class.
> Sometimes I do not get the error. I can just restart Tomcat and
> the exception goes way. Is there some unsychronized threading
> issue in the startup code?
>
> I'm running the Tomcat 4.0.6 under NetBeans 3.5.1 with Struts 1.1.
> Any issues there?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Jar order in classpath and Exception Jdk14Logger does not implement
Log class
Posted by "J.R. Heisey" <JR...@aol.com>.
JRHeisey@aol.com wrote:
> What is the proper order for the jars in the class path.
> Sometimes I get the error
> org.apache.commons.logging.impl.Jdk14Logger.class
> does not implement Log class.
> Sometimes I do not get the error. I can just restart Tomcat and
> the exception goes way. Is there some unsychronized threading
> issue in the startup code?
>
> I'm running the Tomcat 4.0.6 under NetBeans 3.5.1 with Struts 1.1.
> Any issues there?
>
--
Regards,
J.R. Heisey
650.328.8687
I do not wish to be on any list used for telemarketing or mass mailings
and/or I wish to be added to any do not call or mail list.
Support anti-Spam legislation.
Join the fight http://www.cauce.org/
Support Instant Runoff Voting (IRV)
http://www.fairvote.org/irv
http://www.fairvoteca.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Jar order in classpath
Posted by Craig McClanahan <cr...@apache.org>.
J.R. Heisey wrote:
> What is the proper order for the jars in the class path.
> Sometimes I get the error
> org.apache.commons.logging.impl.Jdk14Logger.class
> does not implement Log class.
> Sometimes I do not get the error. I can just restart Tomcat and
> the exception goes way. Is there some unsychronized threading
> issue in the startup code?
>
> I'm running the Tomcat 4.0.6 under NetBeans 3.5.1 with Struts 1.1.
> Any issues there?
>
Error messages like the one you encountered are not actually based on
class path ordering ... they are caused when there is more than one copy
of the class visible in the class loaders hierarchy. You should always
ensure that, if a set of classes is visible in the servlet container's
class loader (such as being in "common/lib" in Tomcat), you should *not*
also have those classes in your /WEB-INF/lib directory. This gets more
difficult to manage when you're using an IDE -- unfortunately, I am not
familiar enough with how NetBeans does its Tomcat integration to offer
any specific advice here.
However, Tomcat 4.0.x has issues in its class loading implementation ...
a more up-to-date version (4.1.29 or 5.0.19) would be my strong
recommendation.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org