As usual Michael, I appreciate you sarcasm.
I *DID* look in that directory. THEY'RE NOT THERE!!
The three jar files that are there are:
naming-common.jar
naming-resources.jar
servlet.jar
tools.jar
I am using version 4.0.4. As I stated in the below
How should I control how many instances I want of a given servlet?
In my case I would like just one.
I don't think you can control that, usually there is only one instance per Servlet
Engine. Are you trying to say that you don't want to have more than one REQUEST being
handled by the
Just drop the pool, dbcp, and commons into common/lib like you
mentioned. Then follow the guide. In Tomcat 4.1 you don't have to put
the factory parameter in your JNDI setup, but it will be required for
4.0.x.
4.0.x comes with Tyrex, but it has had problems and they are dropping
it. You
Yeah, I just downloaded the jars and I think I'll give this a shot.
Thanks.
Neal
-Original Message-
From: Andrew Conrad [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 28, 2002 10:29 PM
To: 'Tomcat Users List'
Subject: RE: Setting up connection pooling via JNDI
Just drop the pool,
Hi
I am facing strange problem at one of my customers side.
I am using tomcat 3.3 for my devlopment and its working fine.
But at one of customers side tomcat crases unknowingly. It even does not
compile a simple jsp. The os at the client side is solaris,
WHen tomcat starts and a simple
I'm not going to claim that it's 100% safe, but 3.3.1 is mostly a bug-fix
release over 3.3a. However, AFAIK, no jars were added or removed between
the two so you are on pretty safe ground. I don't remember what changed in
Jasper (but you can check the release-notes to see), so if you are using
I'm still struggling to make basic JNDI work with MySQL. I've download all
the jars you mentioned, but I keep getting the following error during
context lookup:
javax.naming.NamingException: Exception creating DataSource:
org.hsql.jdbcDriver
at
My best advise is to start over. You are missing many critical elements of
server.xml, and many of the ones you left in are in the wrong order. With
the possible exception of *Realm, *Connector, or *Config, you shouldn't
remove or re-order any of the elements in the shipping server.xml. See
On Wed, 28 Aug 2002, neal wrote:
Date: Wed, 28 Aug 2002 22:25:32 -0700
From: neal [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Setting up connection pooling via JNDI
As usual Michael, I appreciate you sarcasm.
I
201 - 209 of 209 matches
Mail list logo
