We are using Tomcat 3.3 Final. Having a curious problem on certain jsp
pages that try to dynamically load classes located in a jar in the
WEB-INF/lib area of the web application. The apparent differential is
the use of jsp:include tags within the page.
The details are as follows:
Using Weblogic
The documentation in 3.3 on classpaths is quite good, with an excellent
graphic describing classloaders and how/where things get loaded.
http://localhost:8080/doc/tomcat-ug.html#configuring_classes
Would also suggest familiarity with the Servlet and JSP specs (ie, an
understanding of
Picked this up from the archive for the list and curious if anyone has
responded to it. We see the same thing. Under Tomcat 3.3 with WL 5.1 we
get a partial stack trace on the console of Tomcat anytime an app level
exception comes back over the wire, using WL 6.1 it gets worse than that
and the
One option is a load balancer that will handle session affinity, either on
it's own or through a custom cookie/url rewrite. This is a problem with
almost all web application server solutions, certainly not unique to
Tomcat/JSP.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
We are in the process of upgrading to Tomcat 3.2.1 from 3.1 and have
experienced an issue with class loading which we did not see before.
We started getting class not found exceptions while trying to do a naming
lookup to a Weblogic 510 sp8 server. Under 3.1 this was not an issue. We
placed the
There seem to be a number of issues with 3.2.1, some of which prevent us
from moving to it. Looking for any insight into workarounds, fixes, or
strategy (ie wait till 3.3?). From perusing the list, we don't seem to be
alone in experiencing these. Unfortunately, I haven't gotten a feel for
out Jboss?
It has embedded tomcat 3.2.1 support (tomcat
runs in same VM), it's open source , and supported
by a very active and dynamic group of developpers.
Chris
Andrew Gilbert wrote:
There seem to be a number of issues with 3.2.1, some of which prevent us
from moving to it. Looking for any
I have made two posts to the list about similar problems with 3.2.1 and
using JNDI/RMI (EJB's) and not figured much out. Not having the time to
delve further I backed off to Tomcat 3.1. You may try that for the interim.
Any feedback from any of the implementors that would help us start to figure
Good thread. This is an extremely frustrating issue. As is apparent from
this dicussion, other threads, and our own experience, it is not easy or
pretty integrating the latest stable Tomcat (3.2.1) into a full J2EE
environment.
I am going to give the solution suggested below a try in our
: Classpath/loader problems internal to tomcat 3.2.1 [Fwd:
RMI and Tomcat]
Hello,
Thank you very much David Wall and Andrew Gilbert for your answer.
Well I would really like that the way how class loading should work in
Tomcat, works this way. I am using 3.2.1.
I am using Jeremie that is a RMI like
Carlos,
Thanks. This is interesting. Can you explain what the effect of
Thread.setContextClassLoader() is? Does it make classes from the
WEB-INF/lib and WEB-INF/classes area avaiable to classes loaded by
the boot class or system class loader?
Andrew
-Original Message-
From: Carlos
You can make them visible, but the class from the boot classloader or
system classloader has to know what to do -- it calls
Thread.getContextClassLoader() to get the class loader for the current
thread, and asks *that* classloader to create the new object, instead
of
using the "new" operator.
In the process of trying to upgrade our existing application from 3.3 to 4.1.12 I
suffered some pain by not reading the release notes. Reminder to others who try:
The invoker servlet is commented out by default in TOMCAT_HOME/conf/web.xml.
If you don't have servlet mappings in your
Anyway, short of disabling JMX support, of dealing with the following when trying to
use mod_jk (versus mod_jk2) under 4.1.12?
ServerLifecycleListener: createMBeans: MBeanException
java.lang.Exception: ManagedBean is not found with Ajp13Connector
at
Will ask this again in different manner. Looks like there is no MBean support in
4.1.12 for the AJP13 (mod_jk) Apache connector. Is there any easy way to remedy this,
short of disabling JMX support?
Thanks.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands,
We are finding this a particularly frustrating experience, and it seems to be a weak
point either/or both in specification and implementation (or a fatal flaw in our basic
approach - but would add we are consistent at least with the intent of the EJB
specs). Would appreciate input and
Yoav and JeanFrancios,
Thank you both for your replies. They were helpful and somewhat reassuring.
At the general level:
We are aware that Tomcat is not a full J2EE container. But servlets calling EJB's is
bread and butter stuff. We have been successfully using Tomcat to talk to WebLogic for
Edmund,
See Craig's response to my thread RE: Classpath Issues, Tomcat 4.X and J2EE
Interoperability frustrations...
You might want to go the JBoss to JBoss route. In fact I would strongly recommend it.
Andy
-Original Message-
From: Mitchell, Edmund [mailto:[EMAIL PROTECTED]]
and J2EE Interoperability
frustrations...
On Thu, 10 Oct 2002, Andrew Gilbert wrote:
Date: Thu, 10 Oct 2002 11:42:05 -0400
From: Andrew Gilbert [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Classpath Issues
-Original Message-
From: Andrew Gilbert
Sent: Thursday, October 10, 2002 3:39 PM
To: Tomcat Users List
Cc: 'Craig R. McClanahan'; 'Jean-Francois Arcand'; 'Shapira,
Yoav'; Tim
Segall
Subject: RE: Classpath Issues, Tomcat 4.X and J2EE Interoperability
frustrations...
Craig,
I
.X and J2EE Interoperability
frustrations...
On Thu, 10 Oct 2002, Andrew Gilbert wrote:
Date: Thu, 10 Oct 2002 16:23:21 -0400
From: Andrew Gilbert [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Classpath
21 matches
Mail list logo
