subject:"connection pooling"

Hi, I have a sort of theoretical question.  I'm
wondering about the pros and cons of using a one
connection per tomcat session strategy for connecting
to a Postgresql server rather than connection pooling.
 

My users generally login in the morning and keep my
app open for extended periods of time, usually
serveral hours at least.  The one connection per
session method seems to work well.  Here are the
reasons I'm using it.

1.  Can cache prepared statements, something that is
more problematic to do with a generic connection pool.

2.  Have better control of connection releases via the
finalize() method in a session helper class that
contains the one single connection.

3.  Easier to code and implement than connection
pooling.

4.  Potentially faster than connection pooling because
of only one connection open per session.  

Are there issues that I'm overlooking?  If I had more
users with shorter sessions, would it make a
difference?


Thanks.




__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection pooling verse one connection per session

2005-03-10 Thread QM

On Thu, Mar 10, 2005 at 10:31:41AM -0800, Mark Winslow wrote:
: Hi, I have a sort of theoretical question.  I'm
: wondering about the pros and cons of using a one
: connection per tomcat session strategy for connecting
: to a Postgresql server rather than connection pooling.

The great benefit of pooling is that objects that aren't being
(actively) used by one person/login/etc can be used by another.  
Put another way, the Connection objects aren't specific to a user, so
there's no need to treat them as such.  (If you've done any EJB, think
of Stateless vs Stateful Session Beans.)

You say your users are logged into your app all day; but are they
constantly streaming data from the minute they login to the minute they
logout?  If not, then holding open the DB connection for them isn't
helping much.  (I'd hesitate to say it's doing harm or anything bad,
just that it's not helping.)

For this same reason, pooling also helps in scalability: when a
Connection is idle (not being used by anyone), someone else can use it.  



: 1.  Can cache prepared statements, something that is
: more problematic to do with a generic connection pool.

True; but have you seen a significant performance gain due to prepared
statement caching?


: 2.  Have better control of connection releases via the
: finalize() method in a session helper class that
: contains the one single connection.

I'm not sure I understand this.  If your app is written such that
data-access code fetches a Connection as needed, then returns it to the
pool when it's done (Connection#close()), then what other control would
you need?

You realize, for a pooled connection, close() doesn't really shutdown
the network connection.  It just sends the Connection object back to the
pool.


: 3.  Easier to code and implement than connection
: pooling.

Again, I don't understand this.  Please explain.


: 4.  Potentially faster than connection pooling because
: of only one connection open per session.  

Yes and no. The connection pool keeps the connection open all the time;
so users who go through a pooled Connection object don't suffer any
first time access hits.

-QM


-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection pooling verse one connection per session

OK, I see your points and they are well taken.  A lot
of my concern has to do with this 

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/printer/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations

There is one problem with connection pooling. A web
application has to explicetely close ResultSet's,
Statement's, and Connection's.

So I don't close my result sets, etc.  I have say 5
unique connection hits per page.  Say the tomcat
connection trash collector (set with
removeAbandoned=true) runs every 1 minute.  In one
minute a user can easily hit 5 pages.  That's 25
connections I've created and used for that user
instead of just 1.  

Am I wrong about this?  

A lot of my confusion has to do with the details of
how the underlying connection pool code works and how
efficient it is.  For instance can you assume that the
overhead to create a Pooled Connection based an an
already established connection is negligable? 
Releasing it the same thing?  There are threading
issues involved with connection pools.  Do they create
inefficient blocking conditions?

I understand that there are problems associated with
hanging onto a resource like a connection for extended
periods of time.  It's sort of a non-standard thing to
do and maybe not worth any potential cpu/memory
benefits.  I think I'm probably trying to talk myself
into droping my strategy and implementing connection
pools.

Thanks.

--- QM [EMAIL PROTECTED] wrote:
 On Thu, Mar 10, 2005 at 10:31:41AM -0800, Mark
 Winslow wrote:
 : Hi, I have a sort of theoretical question.  I'm
 : wondering about the pros and cons of using a one
 : connection per tomcat session strategy for
 connecting
 : to a Postgresql server rather than connection
 pooling.
 
 The great benefit of pooling is that objects that
 aren't being
 (actively) used by one person/login/etc can be used
 by another.  
 Put another way, the Connection objects aren't
 specific to a user, so
 there's no need to treat them as such.  (If you've
 done any EJB, think
 of Stateless vs Stateful Session Beans.)
 
 You say your users are logged into your app all day;
 but are they
 constantly streaming data from the minute they login
 to the minute they
 logout?  If not, then holding open the DB connection
 for them isn't
 helping much.  (I'd hesitate to say it's doing
 harm or anything bad,
 just that it's not helping.)
 
 For this same reason, pooling also helps in
 scalability: when a
 Connection is idle (not being used by anyone),
 someone else can use it.  
 
 
 
 : 1.  Can cache prepared statements, something that
 is
 : more problematic to do with a generic connection
 pool.
 
 True; but have you seen a significant performance
 gain due to prepared
 statement caching?
 
 
 : 2.  Have better control of connection releases via
 the
 : finalize() method in a session helper class that
 : contains the one single connection.
 
 I'm not sure I understand this.  If your app is
 written such that
 data-access code fetches a Connection as needed,
 then returns it to the
 pool when it's done (Connection#close()), then what
 other control would
 you need?
 
 You realize, for a pooled connection, close()
 doesn't really shutdown
 the network connection.  It just sends the
 Connection object back to the
 pool.
 
 
 : 3.  Easier to code and implement than connection
 : pooling.
 
 Again, I don't understand this.  Please explain.
 
 
 : 4.  Potentially faster than connection pooling
 because
 : of only one connection open per session.  
 
 Yes and no. The connection pool keeps the connection
 open all the time;
 so users who go through a pooled Connection object
 don't suffer any
 first time access hits.
 
 -QM
 
 
 -- 
 
 software  -- http://www.brandxdev.net
 tech news -- http://www.RoarNetworX.com
 
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection pooling verse one connection per session

2005-03-10 Thread QM

On Thu, Mar 10, 2005 at 12:30:22PM -0800, Mark Winslow wrote:
:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/printer/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations
:
: There is one problem with connection pooling. A web
: application has to explicetely close ResultSet's,
: Statement's, and Connection's.

I'd hardly say that's a problem; that's just good coding practice. =)
(example: When I'm done cooking, I should turn off the stove. Is that a
problem with stoves, or just how stoves work?)

Connection cleanup maintenance is straightforward: liberally sprinlke
finally{} blocks around data access code. -and if that's abstracted out
into a layer, and a separate set of objects, you shouldn't have to look
in that many places to insert said finally{} blocks.

: For instance can you assume that the
: overhead to create a Pooled Connection based an an
: already established connection is negligable?

A pooled connection usually *is* an established connection. The idea of
pooling (any sort of object pooling) is that the app (here, Tomcat)
instantiates some number of said objects ahead of time, such that
they're ready to use when needed. In some cases the objects are created
on-demand but then kept around for future use.

Pooled Connection objects are wrapped in another object (that also
implements Connection) that intercepts close() calls. Instead of
actually closing the connection, it returns the object to the pool.

: There are threading
: issues involved with connection pools.

Such as...? As long as you treat a Connection as a hot potato -- hold
on to it only as long as you need, then pitch it -- there should be no
such threading issues. -and as long as you only fetch Connection objects
from the DataSource, then you should never run into an issue where two
sections of code get the same Connection.

: It's sort of a non-standard thing to
: do and maybe not worth any potential cpu/memory
: benefits. I think I'm probably trying to talk myself
: into droping my strategy and implementing connection
: pools.

For me, it's mostly a design issue. I design my apps such that I can
switch the connection source (pooled, one-off, etc) and the code is none
the wiser. It just knows, I get a Connection here, and I call close()
on it when I'm done. Whether close() really terminates a network
connection/DB session, or just returns an object to the pool, it doesn't
matter...

-QM

software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection pooling verse one connection per session

I'm still not entirely sure about this issue.  The
close/=null + finally blocks make for pretty ugly and
error prone code if you ask me.

Why doesn't the connection pool encapsulate closing
anyway?  Can't it encapsulate closing into the
finalize() methods?  Are there ordering issues for
closing ResultSets, Statements, and Connections? Is
infrequent garbage collection an issue?

I'm asking about encapsulating into the finalize()
methods because I don't like the asthetics of all the
close/=null + finally statements.  I believe they make
for confusing and error prone code and would like a
way to make my own encapsulating classes.


--- QM [EMAIL PROTECTED] wrote:
 On Thu, Mar 10, 2005 at 12:30:22PM -0800, Mark
 Winslow wrote:
 :

http://jakarta.apache.org/tomcat/tomcat-5.5-doc/printer/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations
 : 
 : There is one problem with connection pooling. A
 web
 : application has to explicetely close ResultSet's,
 : Statement's, and Connection's.
 
 I'd hardly say that's a problem; that's just good
 coding practice. =)
 (example: When I'm done cooking, I should turn off
 the stove.  Is that a
 problem with stoves, or just how stoves work?)
 
 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

On Thu, Mar 10, 2005 at 10:31:41AM -0800, Mark Winslow wrote:
 
 2.  Have better control of connection releases via the
 finalize() method in a session helper class that
 contains the one single connection.

I hope you meant finally clause rather than finalize() method.  A 
finalize() method is only called when an object is garbage collected, which may 
not happen for a long, long time, if ever.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

if ever.??? Is that really the case?  My personal
experience with Tomcat is that it does indeed have
memory leak problems.  In theory, shouldn't all
objects created in a web user session eventually be
garbage collected after the session ends?

I in fact did mean the finalize() method.  Is that the
main reason not to encapsulate close() methodology
there because of slow garbage collection?  


--- Caldarale, Charles R
[EMAIL PROTECTED] wrote:
 On Thu, Mar 10, 2005 at 10:31:41AM -0800, Mark
 Winslow wrote:
  
  2.  Have better control of connection releases via
 the
  finalize() method in a session helper class that
  contains the one single connection.
 
 I hope you meant finally clause rather than
 finalize() method.  A finalize() method is only
 called when an object is garbage collected, which
 may not happen for a long, long time, if ever.
 
  - Chuck
 
 
 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR
 OTHERWISE PROPRIETARY MATERIAL and is thus for use
 only by the intended recipient. If you received this
 in error, please contact the sender and delete the
 e-mail and its attachments from all computers.
 

-
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 



__ 
Do you Yahoo!? 
Yahoo! Sports - Sign up for Fantasy Baseball. 
http://baseball.fantasysports.yahoo.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

 From: Mark Winslow [mailto:[EMAIL PROTECTED]
 Subject: RE: Connection pooling verse one connection per session

 if ever.??? Is that really the case?  My personal
 experience with Tomcat is that it does indeed have
 memory leak problems.

Nearly all the memory leaks I've seen have been in the apps, frequently related 
to use of static variables to hold references to various session- or 
request-related items.  The few that have actually been a Tomcat problem seem 
to get fixed fairly quickly.

 In theory, shouldn't all objects created in a web user session 
 eventually be garbage collected after the session ends?

The GC algorithms do not guarantee that any specific object will be collected.  
If minor (young generation) GCs are sufficient to keep the JVM running, a full 
(tenured generation) GC need not be performed.  Objects in the tenured 
generation may never be collected and their finalize() methods may then never 
be called - the JVM may terminate first.

 I in fact did mean the finalize() method.  Is that the
 main reason not to encapsulate close() methodology
 there because of slow garbage collection?  

I don't know that I'd characterize it as slow; the current GC algorithms try 
to do as little work as possible, so it may be a long time before the desired 
object gets collected.  Since the point at which a finalize() method is called 
is so indeterminate, its usefulness is rather limited.  (Any class with a 
finalizer method is also somewhat inefficient, since it disrupts GC - each such 
object must be collected twice - and it slows down object allocation, since 
each finalizable object has to be registered.)

The try {}, catch {}, finally {} sequence is much more robust.

 - Chuck

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection pooling verse one connection per session

2005-03-10 Thread QM


On Thu, Mar 10, 2005 at 01:52:02PM -0800, Mark Winslow wrote:
: I'm still not entirely sure about this issue.  The
: close/=null + finally blocks make for pretty ugly and
: error prone code if you ask me.

Well, certainly no one's forcing you to code that way.  It's just a
fairly standard practice in Java webapps to pool DB connections and to
use try/catch/finally blocks where appropriate. ;)


: Why doesn't the connection pool encapsulate closing
: anyway?

It seems you're missing the point of the pool.  Pooled connections
remain open (logged in to the remote DB).  The close() method on the
Connection wrapper object puts the (underlying) Connection object back
in the pool so others can use it.



: Can't it encapsulate closing into the
: finalize() methods?

Maybe it does; but there's no guarantee finalizers will be called.
Besides, do you want to wait for gc to run to free up connections?


: Are there ordering issues for
: closing ResultSets, Statements, and Connections?

This is in the docs...  I *think* closing a Connection closes all
underlying Statement and ResultSet objects, but it's good form to just
close them when you're done with them.


: Is infrequent garbage collection an issue?

If you're waiting for finalizers to do your cleanup work for you, yes.  


: I'm asking about encapsulating into the finalize()
: methods because I don't like the asthetics of all the
: close/=null + finally statements.

Again, your call.


-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

I don't know.  I have one pure Tomcat (no Apache)
server that all it does is serve about 300,000 static
files per day.  The memory usage grows and grows
unexplicably.  I run a cron job that restarts it
everyday, which I had to started running with version
5.0.something or else it would eventually run out of
memory and crash.  I haven't seen what not restarting
will do on 5.5 and the latest version of Java/Linux. 
I guess I'll try and see.

I'm going to switch to using connection pools
regardless.  I really just had some questions about
the standard way of releasing them and gc issues
regarding them which have been answered by the nice
people on this list.

Thanks.


 
 Nearly all the memory leaks I've seen have been in
 the apps, frequently related to use of static
 variables to hold references to various session- or
 request-related items.  The few that have actually
 been a Tomcat problem seem to get fixed fairly
 quickly.
 
 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

Sorry, just had one other question about the use of
static variables.  Can this really be a problem?  I
thought that a static variable only gets a single copy
per JVM/Context.  For instance the use of static
variables to define formats shouls save on memory
usage shouldn't it?

public class Helper
{

public static final DecimalFormat dFormat1 = new
DecimalFormat(00);

public static final DecimalFormat dFormat2 = new
DecimalFormat(#,##0.00);

public static final SimpleDateFormat df1 = new
SimpleDateFormat(HH:mm);

public static final SimpleDateFormat df2 = new
SimpleDateFormat(EEE, d MMM, );

}

 the apps, frequently related to use of static
 variables to hold references to various session- or
 



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

 From: Mark Winslow [mailto:[EMAIL PROTECTED]
 Subject: RE: Connection pooling verse one connection per session

 The memory usage grows and grows unexplicably.

Modern JVMs also try to avoid doing GC if they can.  So, if you've given the 
JVM a large amount of memory, it will use it all before attempting a GC.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection pooling verse one connection per session

 From: Mark Winslow [mailto:[EMAIL PROTECTED]
 Subject: RE: Connection pooling verse one connection per session

 Sorry, just had one other question about the use of
 static variables.  Can this really be a problem?  I
 thought that a static variable only gets a single copy
 per JVM/Context.  For instance the use of static
 variables to define formats shouls save on memory
 usage shouldn't it?

I didn't mean to imply earlier that all static variable usage was bad, just 
that it can be easily abused in a fashion that leads to memory leaks.  The 
usages you've outlined seem quite appropriate.

 - Chuck

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cluster and Connection Pooling problem

2005-02-21 Thread Peter Johnson

Define the connection pool in either META-INF/context.xml (if using a 
WAR) or ${catalina_home}/conf/engine/host/app.xml

And the link by the usual resource ref in the web.xml
Remember that the JDBC drivers need to be in common/lib
PJ
Sumpter, Chuck wrote:
Environment =  Tomcat 5.5.7,  Java 1.5_01, IIS (win2k) using the isapi
redirector. 


Problem:  


Using the scenario outlined by Graham King
(http://www.javaworld.com/javaworld/jw-12-2004/jw-1220-tomcat.html ), a
simple cluster is easily configured.  However, when attempting to deploy
our application, I run into a wall attempting to get things in the
proper order regarding the connection pooling needed by the application.
The application's error log indicates that the connection pooling parms
are not really being read in the server.xml. 


What is the conflict?  Anyone else encountered this?  I hesitate to
supply xml in this forum if someone else has encountered this problem 


TIA 


Chuck 

 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Cluster and Connection Pooling problem

2005-02-18 Thread Sumpter, Chuck

Environment =  Tomcat 5.5.7,  Java 1.5_01, IIS (win2k) using the isapi
redirector. 

 

Problem:  

 

Using the scenario outlined by Graham King
(http://www.javaworld.com/javaworld/jw-12-2004/jw-1220-tomcat.html ), a
simple cluster is easily configured.  However, when attempting to deploy
our application, I run into a wall attempting to get things in the
proper order regarding the connection pooling needed by the application.
The application's error log indicates that the connection pooling parms
are not really being read in the server.xml. 

 

What is the conflict?  Anyone else encountered this?  I hesitate to
supply xml in this forum if someone else has encountered this problem 

 

TIA 

 

Chuck

Tomcat 5 - Datasource Connection Pooling

2005-01-24 Thread Manisha Sathe

Finally after long struggle I could get the datasource things running. 
 
The things are working when i specified all into GlobalResources and 
GlobalContext inside server.xml 
 
My server.xml is something like below..
 
-
GlobalNamingResources
Resource auth=Container name=mspool type=javax.sql.DataSource/
ResourceParams name=mspool
  parameter
nameurl/name  
valuejdbc:microsoft:sqlserver://localhost:1433;DatabaseName=sbcs/value
  /parameter
  parameter
namemaxIdle/name
value30/value
  /parameter
  parameter
namemaxActive/name
value100/value
  /parameter
  parameter
namedriverClassName/name
valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value
  /parameter
  parameter
namemaxWait/name
value1/value
  /parameter
  parameter
nameusername/name
valuemanisha/value
  /parameter
  parameter
namefactory/name
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
  /parameter
  parameter
nameselectMethod/name
valuecursor/value
  /parameter
  parameter
namepassword/name
valuemanisha/value
  /parameter
  parameter
nameremoveAbandoned/name
valuetrue/value
  /parameter
  parameter
 nameremoveAbandonedTimeout/name
 value60/value
   /parameter
   parameter
  namelogAbandoned/name
  valuetrue/value
   /parameter
/ResourceParams
  /GlobalNamingResources
...

  Host appBase=webapps name=localhost
DefaultContext 
className=org.apache.catalina.core.StandardDefaultContext
  ResourceLink global=mspool name=mspool 
type=javax.sql.DataSource/
/DefaultContext
Logger className=org.apache.catalina.logger.FileLogger
 directory=logs  prefix=localhost_log. 
suffix=.txt
timestamp=true/
  /Host  

 
I did not change anything inside Web.xml as everything is inside 
Global.
 
But i do not want it inside global naming resources / default context - 
but i want it only specific to my web application. i also understand 
that Context - should not be used for TomCat5.0 - but need to put 
inside /META-INF/context.xml.
 
1)My problem is my working directory is different. I use ant to create 
war file and then i manually stop the server - delete existing war file 
/ existing directory (This is due to some Win TomCat problem .??..). 
Then i deploy it using TomCat Manager. It automatically creates META-INF 
file for me, i do not have META-INF inside my working directory. So 
where i can put my context.xml ?
 
2) What shall i put inside context.xml and what shall i put inside 
server.xml / web/xml ?
 
I tried many different ways but when i use context and as there is no 
such application (because i delete and re-deploy it) - tomcat server 
does not run my application. 
 
Pls guide me
 
regards
Manisha


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: Tomcat 5 - Datasource Connection Pooling

2005-01-24 Thread Trond G. Ziarkowski

Hi!
1)My problem is my working directory is different. I use ant to create 
war file and then i manually stop the server - delete existing war file 
/ existing directory (This is due to some Win TomCat problem .??..). 
Then i deploy it using TomCat Manager. It automatically creates META-INF 
file for me, i do not have META-INF inside my working directory. So 
where i can put my context.xml ?
 

You have already answered this yourself, META-INF/ directory of your war 
file.
The only way to avoid the META-INF directory is to not use a war file, 
as a war file simply is a jar file, and the META-INF is part of the jar 
file specification.

2) What shall i put inside context.xml and what shall i put inside 
server.xml / web/xml ?
 

The example pages: 
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jndi-datasource-examples-howto.html 
tells you exactly what to put in each file. You just have to read them 
one more time and keep focused.
I'll give you some hints as well:
- Leave server.xml the way it was before you started tampering with it.
- Copy CATALINA_HOME/conf/enginename/servername/yourapp.xml, to your 
context.xml file, and add your resource specification inside the 
context as in the examples. Then include context.xml in your war file 
in the META-INF dir. Your app must be running for the yourapp.xml file 
to exist as it is deleted when you undeploy your app.
- In web.xml you need to add a resource-ref as you can see from the 
examples

Good luck
Trond
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Connection Pooling with Tomcat 4.1 and SQL Server 2000

2005-01-06 Thread Friedrich Gonzalez

Everything you did with the driver,server.xml,web.xml is ok.
But it sounds like your driver of sql server 2000 doesnt support 
connection pooling ...
did you tried to connect without the connection pool?
i also recommend going to tomcat 5... i had a couple of issues with 
connection pooling in tomcat 4 with db2 so i went to tomcat 5.
now everything is just better.

Johnson, Jay escribió:
I am trying to establish a connection pool in Tomcat 4.1 to SQL Server
2000.  Looking at the SQL Server trace utility, it appears Tomcat
connects with the correct username/password and then the following
exception is thrown:

java.lang.UnsupportedOperationException at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSourc
e.java:161).
I have taken the following steps:
1)Moved the driver jar files to /common/lib/
2)Modified the Server.xml file
3)Modified the web.xml file of the application
Here is my Server.xml entry:
DefaultContext
Resource name=jdbc/test auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/test
parameter
namedriverClassName/name
valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value
/parameter
parameter
nameurl/name
valuejdbc:microsoft:sqlserver://localhost:1433/value
/parameter
parameter
nameusername/name
valuejay/value
/parameter
parameter
namepassword/name
valuejay/value
/parameter
parameter
namemaxActive/name
value20/value
/parameter
parameter
namemaxIdle/name
value10/value
/parameter
parameter
namemaxWait/name
value100/value
/parameter
/ResourceParams
/DefaultContext
Here is my entry in the web.xml file:
resource-ref
descriptionDB Connection/description
res-ref-namejdbc/test/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth 
/resource-ref

Are any additional entries needed?  Any help would be greatly
appreciated!

Thanks,
Jay Johnson
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Connection Pooling with Tomcat 4.1 and SQL Server 2000

2005-01-06 Thread Johnson, Jay

I can connect using my current driver without connection pooling.  You may be 
correct; the driver may not support it.  I'm using Microsoft's standard type 4 
driver.  I'll try using Tomcat 5 also and see if it makes a difference.  I'll 
also see if I can find another driver.  Thanks for help!

-Original Message-
From: Friedrich Gonzalez [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 06, 2005 6:10 AM
To: Tomcat Users List
Subject: Re: Connection Pooling with Tomcat 4.1 and SQL Server 2000

Everything you did with the driver,server.xml,web.xml is ok.
But it sounds like your driver of sql server 2000 doesnt support 
connection pooling ...
did you tried to connect without the connection pool?
i also recommend going to tomcat 5... i had a couple of issues with 
connection pooling in tomcat 4 with db2 so i went to tomcat 5.
now everything is just better.

Johnson, Jay escribió:

I am trying to establish a connection pool in Tomcat 4.1 to SQL Server
2000.  Looking at the SQL Server trace utility, it appears Tomcat
connects with the correct username/password and then the following
exception is thrown:

java.lang.UnsupportedOperationException at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSourc
e.java:161).

I have taken the following steps:

1)Moved the driver jar files to /common/lib/
2)Modified the Server.xml file
3)Modified the web.xml file of the application

Here is my Server.xml entry:

DefaultContext
Resource name=jdbc/test auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/test
parameter
namedriverClassName/name
valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value
/parameter
parameter
nameurl/name
valuejdbc:microsoft:sqlserver://localhost:1433/value
/parameter
parameter
nameusername/name
valuejay/value
/parameter
parameter
namepassword/name
valuejay/value
/parameter
parameter
namemaxActive/name
value20/value
/parameter
parameter
namemaxIdle/name
value10/value
/parameter
parameter
namemaxWait/name
value100/value
/parameter
/ResourceParams
/DefaultContext

Here is my entry in the web.xml file:

resource-ref
descriptionDB Connection/description
res-ref-namejdbc/test/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth 
/resource-ref

Are any additional entries needed?  Any help would be greatly
appreciated!

Thanks,

Jay Johnson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Connection Pooling with Tomcat 4.1 and SQL Server 2000

2005-01-05 Thread Johnson, Jay

I am trying to establish a connection pool in Tomcat 4.1 to SQL Server
2000.  Looking at the SQL Server trace utility, it appears Tomcat
connects with the correct username/password and then the following
exception is thrown:

 

java.lang.UnsupportedOperationException at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSourc
e.java:161).
 
I have taken the following steps:
 
1)Moved the driver jar files to /common/lib/
2)Modified the Server.xml file
3)Modified the web.xml file of the application
 
Here is my Server.xml entry:
 
DefaultContext
Resource name=jdbc/test auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/test
parameter
namedriverClassName/name
valuecom.microsoft.jdbc.sqlserver.SQLServerDriver/value
/parameter
parameter
nameurl/name
valuejdbc:microsoft:sqlserver://localhost:1433/value
/parameter
parameter
nameusername/name
valuejay/value
/parameter
parameter
namepassword/name
valuejay/value
/parameter
parameter
namemaxActive/name
value20/value
/parameter
parameter
namemaxIdle/name
value10/value
/parameter
parameter
namemaxWait/name
value100/value
/parameter
/ResourceParams
/DefaultContext
 
Here is my entry in the web.xml file:
 
resource-ref
descriptionDB Connection/description
res-ref-namejdbc/test/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth 
/resource-ref
 
Are any additional entries needed?  Any help would be greatly
appreciated!

 

Thanks,

Jay Johnson

tomcat problem related connection pooling help needed

2004-12-19 Thread Krishnakant Mane

hello Jan and other friends,
I read the mail that was sent as a reply for my
problem.
thanks jan for ur valuable help.
I must mention that I am new to the jdbc stuff.  so I
could not figure out the connection pooling issue.  I
understand that with pooling I can have live objects
of say connection objects that I can use as a pool and
that tomcat can send them when needed.
but I don't exactly know how to do it please guide me
abt jdbc connection pooling.  I know that it is out of
topic on this list, but to understand jdbc pooling and
my problem related to tomcat, I must first understand
in short how pooling in jdbc works.
plese help me on these issues.
thanks
Krishnakant.



___ 
Win a castle for NYE with your mates and Yahoo! Messenger 
http://uk.messenger.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: tomcat problem related connection pooling help needed

2004-12-19 Thread Jan Behrens

ok, i will share what little knowledge i have...

when you normaly open a database connection, you get a connection object
that represents a database connection, you allways get a new connection and
have to ensure that this is definetly closed after usage. there a quite a
few drawbacks to this as you _must_ close the connection and in that the
number of java connection objects have to correspond to those maximal
available from your dbms (e.g. mysql). 

my first webapp at university was build like that and worked fine till i got
load on the system - then it crashed ;)

a connection pool helps you in avoiding mentioned problems. it basically is
a pool (funny that :) managed by a pool provider that consist of a limited
number of actual connection objects. these get created (and in specific
cases even destroyed/closed) by the pool provider. all you have to do is
configure it according to your specifications and then changed your db code
to request connections from the pool.

tomcat, beeing the great server it is, comes with a pool provider that you
could use to start with. i am not sure whether it is recommended for
production so you should check that before going live with your system. you
usually will set up a connection pool in combination with a jndi ressource
that provides everything needed for your app. 

first created the mentioned jndi by editing your applications xml file under

{TomcatInstallDir}\conf\Catalina\{servername}\myApplicationName.xml

you will need to insert a new ressource within the context-tag. the
following should serve as a general guideline, you will have to change
names, paths etc according to your setup of course :)

?xml version='1.0' encoding='utf-8'?
Context ... 
...
  Resource auth=Container name=jdbc/yourDatasourceName
type=javax.sql.DataSource/
  ResourceParams name=jdbc/yourDatasourceName
parameter
  nameurl/name
  valuejdbc:mysql://localhost:3306/daxcolog?autoReconnect=true/value
/parameter
parameter
  namemaxIdle/name
  value15/value
/parameter
parameter
  namemaxActive/name
  value50/value
/parameter
parameter
  namedriverClassName/name
  valuecom.mysql.jdbc.Driver/value
/parameter
parameter
  namemaxWait/name
  value1/value
/parameter
parameter
  nameremoveAbandoned/name
  valuetrue/value
/parameter
parameter
  nameusername/name
  valuedbUsername/value
/parameter
parameter
  namefactory/name
  valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
  nameremoveAbandonedTimeout/name
  value60/value
/parameter
parameter
  namepassword/name
  valuedbPassword/value
/parameter
  /ResourceParams
/Context

the following two methods illustrate how to retrieve the session from the
context afterwards. NOTE: these are quite old as i have been using hibernate
for quite some time now, so use them as a general guideline only!

private Connection connect() {
  Connection conn = null;

try {
Context ctx = new InitialContext();

if (ctx == null) {
throw new Exception(
BaseTable.connect() -- Could not get Database
Context);
}

DataSource ds = (DataSource)
ctx.lookup(java:comp/env/jdbc/yourDatasourceName);

if (ds != null) {
conn = ds.getConnection();
}
} catch (Exception e) {
logger.error( Connection error! , e);
}

return conn;
}

private void disconnect(Connection conn) {
try {
java.sql.SQLWarning sqlw = conn.getWarnings();

while (sqlw != null) {
logger.error( SQL Warnings:  + 
   sqlw);
sqlw = sqlw.getNextWarning();
}

conn.close();
} catch (Exception e) {
logger.error( Error closing connection , e);
}

conn = null;
}

there are several good tutorials on this topic as well (just google or look
at either the tomcat or mysql driver manual) and i would highly recommend
looking into them, especially to ensure that you are closing every statement
and connection and that connections are correctly returned to the pool...

hth, jan

 -Original Message-
 From: Krishnakant Mane [mailto:[EMAIL PROTECTED] 
 Sent: Sunday, December 19, 2004 2:17 PM
 To: [EMAIL PROTECTED]
 Subject: tomcat problem related connection pooling help needed
 
 
 hello Jan and other friends,
 I read the mail that was sent as a reply for my
 problem.
 thanks jan for ur valuable help.
 I must mention that I am new to the jdbc stuff.  so I
 could not figure out the connection pooling issue.  I 
 understand that with pooling I can have live objects of say 
 connection objects that I can use as a pool and that tomcat 
 can send them when needed. but I don't exactly know how

Re: connection pooling

2004-12-17 Thread Didier McGillis

thats what I hope this is, the guy who was before me wasnt that great at 
anything other then coding swing apps, so tomcat the server and database are 
a mess.

From: Filip Hanik - Dev [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: connection pooling
Date: Thu, 16 Dec 2004 16:13:03 -0600
depends on what connection pool you use. but in almost all causes, its a 
pretty trivial thing (unless your code is funky of course)
in our system, all we did was to switch the driver name (to the pooled 
driver), and it would pick up our connection pool.
so it was a one line change.

Filip
- Original Message -
From: Didier McGillis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 3:49 PM
Subject: connection pooling
I'm about to the point where I'm going to switch to db connection pooling.
however before I undertake this seemly easy task I have a question, which
will make this a huge project or a simple one.
The current site uses typical MySQL connection, where a connection is 
opened
and so on, if I do connection pooling will I have to go in and do mass code
changes?  aka will I have to rewrite any servlets or jsps that make 
database
calls.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: connection pooling

2004-12-16 Thread Filip Hanik - Dev

depends on what connection pool you use. but in almost all causes, its a pretty 
trivial thing (unless your code is funky of course)
in our system, all we did was to switch the driver name (to the pooled driver), 
and it would pick up our connection pool.
so it was a one line change.

Filip

- Original Message - 
From: Didier McGillis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, December 16, 2004 3:49 PM
Subject: connection pooling


I'm about to the point where I'm going to switch to db connection pooling.  
however before I undertake this seemly easy task I have a question, which 
will make this a huge project or a simple one.

The current site uses typical MySQL connection, where a connection is opened 
and so on, if I do connection pooling will I have to go in and do mass code 
changes?  aka will I have to rewrite any servlets or jsps that make database 
calls.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

connection pooling

2004-12-16 Thread Didier McGillis

I'm about to the point where I'm going to switch to db connection pooling.  
however before I undertake this seemly easy task I have a question, which 
will make this a huge project or a simple one.

The current site uses typical MySQL connection, where a connection is opened 
and so on, if I do connection pooling will I have to go in and do mass code 
changes?  aka will I have to rewrite any servlets or jsps that make database 
calls.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat Connection Pooling

2004-11-29 Thread Cumbers

Hey
I have within my server.xml the following:
Resource name=jdbc/postgres auth=Container
  type=javax.sql.DataSource/
ResourceParams name=jdbc/postgres
  parameter
namefactory/name
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
  /parameter
  parameter
namedriverClassName/name
valueorg.postgresql.Driver/value
  /parameter
  parameter
nameurl/name
valuejdbc:postgresql://penguin.kent.ac.uk:5432/rms_dev/value
  /parameter
  parameter
nameusername/name
valuerms_dev/value
  /parameter
  parameter
namepassword/name
valueisi5gi/value
  /parameter
  parameter
namemaxActive/name
value20/value
  /parameter
  parameter
namemaxIdle/name
value10/value
  /parameter
  parameter
namemaxWait/name
value-1/value
  /parameter
/ResourceParams
And I also have the relevant ResourceLink information to get this 
working. And it does work within my web application.

However I want to ensure that this is actually a connection pool. I want 
to test to see how many connections are in the pool, is there a way? Or 
can someone tell me for sure if I have set connection pooling up?

Thanks
Rich
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat 4.1: Setting Up Connection Pooling, Adding Resource to server.xml

2004-11-26 Thread David Stevenson

The question relates to my home study of the Tomcat Server via the book
referenced below.

Added Context via Tomcat Administration page.
Added Resource, ResourceParams, and parameter tags by hand-editing
the server.xml file, and re-starting.

Reference: Ian McFarland, Peter Harrison, Mastering Tomcat Development,
Wiley Publishing, Inc., p. 283-284.

=

In Tomcat Administration Page:
Clicking on Data Sources, under Resources, under Context /tomcatbook,
under Host, gives the
following exception, perhaps indicating Tomcat 4.1 is not compatible
with this XML setup. Exception truncated for brevity's sake.

exception

org.apache.jasper.JasperException: Exception retrieving attribute
'driverClassName'
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

=

Changes to $CATALINA/HOME/server.xml (Context tag added by Tomcat
Administration page, 
inside Context tag manually added via text editor, as recommended by
referenced book):

  Context className=org.apache.catalina.core.StandardContext
cachingAllowed=true
charsetMapperClass=org.apache.catalina.util.CharsetMapper
cookies=true crossContext=false debug=0 docBase=tomcatbook
mapperClass=org.apache.catalina.core.StandardContextMapper
path=/tomcatbook privileged=false reloadable=true
swallowOutput=false useNaming=false
wrapperClass=org.apache.catalina.core.StandardWrapper
Resource name=jdbc/tomcatbook auth=Container
type=javax.sql.DataSource 
  ResourceParams name=jdbc/tomcatbook
parameter
  nameuser/name
  valuetomcatbook/value
/parameter
parameter
  namepassword/name
 
valuePasswordIntentionallyChangedToProtectMeFromTheGuilty/value
/parameter
parameter
  namedriverClassName/name
  valuecom.mysql.jdbc.Driver/value
/parameter
parameter
  nameurl/name
  valuejdbc:mysql://localhost.localdomain/tomcatbook/value
/parameter
  /ResourceParams
/Resource
  /Context
=
Should I create a New Data Source in the Tomcat Administration Tool?
Would the following values be correct?

PropertyValue
JNDI Name:  jdbc/tomcatbook

Data Source URL:jdbc:mysql://localhost.localdomain/tomcatbook

JDBC Driver Class:  com.mysql.jdbc.Driver

User Name:  tomcat  

Password:   PasswordIntentionallyChangedToProtectMeFromTheGuilty

Max. Active Connections:4

Max. Idle Connections:  2

Max. Wait for Connection:   5000

Validation Query:   ??? select login, password from user 



=
Server Information
Tomcat Version  Apache Tomcat/4.1.24-LE-jdk14
JVM Version 1.4.2-b28
JVM Vendor  Sun Microsystems Inc.
OS Name Linux   
OS Version  2.4.20-31.9
OS Architecture i386
=

Working Java code:

import java.sql.* ;

public class TestMySQL3
{
public static void main ( String [] args )
throws Exception
{
Class.forName(com.mysql.jdbc.Driver).newInstance();

Connection connection   = null ;
Statement statement = null ;
ResultSet resultSet = null ;
String query = select login, password from user ;

try
{

connection = DriverManager.getConnection (
jdbc:mysql://localhost/tomcatbook,
tomcat, 

PasswordIntentionallyChangedToProtectMeFromTheGuilty ) ;
statement = connection.createStatement () ;
resultSet = statement.executeQuery ( query ) ;
while ( resultSet.next () )
{
String login=
resultSet.getString ( 1 ) ;
String password =
resultSet.getString ( 2 ) ;
System.out.println ( login:  + login +
 password:  + password ) ;
}
}
finally
{
if ( resultSet != null )
resultSet.close () ;
if ( statement != null )
statement.close () ;
if (

Re: Tomcat 4.1: Setting Up Connection Pooling, Adding Resource to server.xml,

2004-11-26 Thread David Stevenson

I missed the following important information that was in the Tomcat
documentation, that wasn't in the book I was reading. I am currently
getting the following exception in my log file when executing a servlet
that obtains a DataSource using the JNDI InitialContext. I previously
thought it might be a class not defined exception because I didn't
supply the connection pooling .jar files as required by the
instructions.

2004-11-26 20:15:24 org.apache.catalina.INVOKER.ClientListPooledServlet:
ClientListPooledServlet.init:
javax.naming.NameNotFoundException: Name java:comp is not bound in this
Context
at
org.apache.naming.NamingContext.lookup(NamingContext.java:811)
at
org.apache.naming.NamingContext.lookup(NamingContext.java:194)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at ClientListPooledServlet.init(ClientListPooledServlet.java:25)

From ClientListPooledServlet.java. Line 25 is the one with the new
InitialContext () constructor call.

public void init ( ServletConfig config )
throws ServletException
{
super.init ( config ) ;
log ( ClientListPooledServlet.init entered ) ;
try
{
// Context initCtx = new InitialContext () ;
// Context envCtx = (Context) initCtx.lookup (
java:comp/env ) ;
// ds = (DataSource) envCtx.lookup (
jdbc/tomcatbook ) ;
ds = (DataSource) new InitialContext ().lookup (
java:comp/env/jdbc/tomcatbook ) ;
}
catch ( Exception e )
{
log ( ClientListPooledServlet.init:  +
e.getMessage () ) ;
log ( ClientListPooledServlet.init: , e ) ;
throw new UnavailableException ( e.getMessage ()
) ;
}
log ( ClientListPooledServlet.init exiting ) ;
}



DBCP uses the Jakarta-Commons Database Connection Pool. It relies on
number of Jakarta-Commons componenets:

* Jakarta-Commons DBCP 1.0
* Jakarta-Commons Collections 2.0
* Jakarta-Commons Pool 1.0

These jar files along with your the jar file for your JDBC driver should
be installed in $CATALINA_HOME/common/lib.

I don't know if these versions are close enough, or not.
If not, I can go through the Jakarta Archives looking for
closer versions.

[EMAIL PROTECTED] logs]$ ll -rt $CATALINA_HOME/common/lib
...
-rw-r--r--1 davidstevenson   175426 Nov 26 20:06
commons-collections-2.1.1.jar
-rw-r--r--1 davidstevenson42492 Nov 26 20:06
commons-pool-1.2.jar
-rw-r--r--1 davidstevenson   107631 Nov 26 20:08
commons-dbcp-1.2.1.jar

Based on the Tomcat Documentation, I revamped the server.xml
configuration (I haven't modified this yet to include the
instructions under Preventing dB connection pool leaks in
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-howto.html).

  Context className=org.apache.catalina.core.StandardContext
cachingAllowed=true
charsetMapperClass=org.apache.catalina.util.CharsetMapper
cookies=true
crossContext=false debug=9 docBase=tomcatbook
mapperClass=org.apache.catalina.core.StandardContextMapper
path=/tomcatbook privileged=false reloadable=true
swallowOutput=false
useNaming=false
wrapperClass=org.apache.catalina.core.StandardWrapper
displayName=Mastering Tomcat Development
 
Logger className=org.apache.catalina.logger.FileLogger
  prefix=localhost_tomcatbook_log. suffix=.txt
  timestamp=true/
Resource name=jdbc/tomcatbook auth=Container
type=javax.sql.DataSource 
  ResourceParams name=jdbc/tomcatbook
parameter
  namefactory/name
  valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
  namemaxActive/name
  value100/value
/parameter
parameter
  namemaxIdle/name
  value30/value
/parameter
parameter
  namemaxWait/name
  value1/value
/parameter
parameter
   nameusername/name
  valuetomcat/value
/parameter
parameter
   namepassword/name
  valueRealPasswordOmitted/value
/parameter
parameter
  namedriverClassName/name
  valuecom.mysql.jdbc.Driver/value
/parameter
parameter
  nameurl/name
 
valuejdbc:mysql://localhost/tomcatbook?autoReconnect=true/value
/parameter
  /ResourceParams
/Resource
  /Context




$ more $CATALINA_HOME/webapps/tomcatbook/WEB-INF/web.xml
...
resource-ref
description
This is a reference to the data source we use
to talk to the database configured in the
server.xml file.
/description
res-ref-namejdbc/tomcatbook/res-ref-name
res

Re: AW: connection pooling

2004-11-11 Thread Eric Wulff

What informix db version are you working with?  I do not know how to
get the serial value.  I use an informix driver that supports
connection pooling and I'm not familiar with the ifmxStatement. 
Depending on the informix version, I suggest utilizing a type 4
informix jdbc driver(search).  That may help although you may need to
change some code such as the ifmxStatement.  I'm in a bit over my head
on this one.

Eric


On Thu, 11 Nov 2004 12:04:28 +0100, Akacem Mohammed
[EMAIL PROTECTED] wrote:
 Hello Eric,
 
 thank you Eric it works now.
 
 but I have another probleme now:
 
 in my code I have the following statements:
 
 ifmxStatement informixStmt= (IfmxStatement)stmt; // I get 
 hier a ClassCastException
// serialvalue = ((IfmxStatement)stmt).getSerial();
  serialvalue = informixStmt.getSerial();
 
 actually I am porting my app from tomcat 4.1 jkd 1.3  to tomcat 5.0.28. jdk 
 1.4. I earlier used the com.bitmechanic.sql package und I had no casting 
 probleme on this statement. I looked in the ifmx.jar docs, the IfmxStatement 
 implement Statement.that means the implementation of dbcp und ifmx.jar driver 
 are not compatible.
 
 have you an idea how to get the serialvalue. I do write the serialvalue I get 
 from informix in a column in my table(it is somhow my increment.) or do you 
 use the pooled version of the informix driver?
 
 thanks for any hint
 
 Mohammed
 
 -Ursprüngliche Nachricht-
 Von: Eric Wulff [mailto:[EMAIL PROTECTED]
 Gesendet: Mittwoch, 10. November 2004 19:26
 An: [EMAIL PROTECTED]
 Betreff: AW: connection pooling
 
 Sorry, I sent this to the user list but didn't copy you directly.
 
 -- Forwarded message --
 From: Eric Wulff [EMAIL PROTECTED]
 Date: Tue, 9 Nov 2004 11:32:15 -0800
 Subject: Re: AW: connection pooling
 To: Tomcat Users List [EMAIL PROTECTED]
 
 Hi Mohammed, The resource-ref of your web.xml looks alright.  While
 the DefaultContext should work if you place it in the correct
 location(see notes below) within your server.xml, I doubt you want
 this to be your final solution.  My final fix was suggested by Steve
 and noted here...
 
 Copy the Context... (you need to change your DefaultContext tag to a
 Context tag) from your server.xml to a file all its own and name that
 file myapp.xml(in your case I guess that would be SteaDB.xml).  Then
 mv that file to $CATALINA_HOME/conf/Catalina/localhost/
 
 Restart your app or shutdown and startup Tomcat and you should be all set.
 
 Let me know how it goes.
 Eric
 
 Notes:
 - I'm not sure if DefaultContext or Context within your server.xml
 have any effect once you have a myapp.xml at
 $CATALINA_HOME/conf/Catalina/localhost/.  I still have a Context in my
 server.xml.
 
 - I don't think it matters but fyi, my Context only includes a
 Resource, and then Resource-Params as follows: username, password,
 driverClass, and url.
 
 - When working with the DefaultContext, location for that tag should
 be within the Engine...  tag having the Standalone attribute.  This
 likely needs to be un-commented, hence you will need to comment out
 the Engine...  tag with the Catlina attribute, which is likely just
 below in the server.xml.
 
 On Tue, 9 Nov 2004 14:25:41 +0100, Akacem Mohammed
 [EMAIL PROTECTED] wrote:
  Hello,
 
  I am stuck in the same Probleme as Erik. I did exactly what in the e-mails 
  suggested is with no success.
  I am runing TC 5.0.28 und try to get a connection to an informix database.
  I got the following Error Message:
 
   org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of 
  class '' for connect URL 'null'
 
  mycode :
 
  try {
  initCtx = new InitialContext();
  envCtx = (Context) initCtx.lookup(java:comp/env);
  ds = (DataSource) envCtx.lookup(jdbc/SteaDB);
  } catch (NamingException e) {
  // TODO Auto-generated catch block
 
  e.printStackTrace();
  }
  try {
conn=ds.getConnection();
  } catch (SQLException e2) {
  // TODO Auto-generated catch block
  e2.printStackTrace();
  }
 
  My Configuration is as follow:
 
  web.xml :
 
resource-ref
descriptionDB Connection to informix/description
res-ref-namejdbc/SteaDB/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
 
  server.xml :
 
  DefaultContext
Resource name=jdbc/SteaDB auth=Container 
  type=javax.sql.DataSource/
 
ResourceParams name=jdbc/SteaDB
  parameter
namefactory/name
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
  /parameter
 !-- Maximum time to wait for a dB connection to become available
   in ms, in this example 10 seconds. An Exception is thrown if
   this timeout is exceeded.  Set to -1 to wait indefinitely.
   --
  parameter

AW: connection pooling

2004-11-09 Thread Akacem Mohammed

Hello,

I am stuck in the same Probleme as Erik. I did exactly what in the e-mails 
suggested is with no success.
I am runing TC 5.0.28 und try to get a connection to an informix database.
I got the following Error Message: 

 org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class 
'' for connect URL 'null'


mycode :

try {
initCtx = new InitialContext();
envCtx = (Context) initCtx.lookup(java:comp/env);
ds = (DataSource) envCtx.lookup(jdbc/SteaDB);
} catch (NamingException e) {
// TODO Auto-generated catch block

e.printStackTrace();
}
try {
  conn=ds.getConnection();
} catch (SQLException e2) {
// TODO Auto-generated catch block
e2.printStackTrace(); 
}

 
 



My Configuration is as follow: 

web.xml :

  resource-ref
  descriptionDB Connection to informix/description
  res-ref-namejdbc/SteaDB/res-ref-name
  res-typejavax.sql.DataSource/res-type
  res-authContainer/res-auth
  /resource-ref

server.xml :

DefaultContext
  Resource name=jdbc/SteaDB auth=Container type=javax.sql.DataSource/

  ResourceParams name=jdbc/SteaDB
parameter
  namefactory/name
  valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
   !-- Maximum time to wait for a dB connection to become available
 in ms, in this example 10 seconds. An Exception is thrown if
 this timeout is exceeded.  Set to -1 to wait indefinitely.
 --
parameter
  namemaxWait/name
  value1/value
/parameter

!-- username and password for dB connections  --
parameter
 nameusername/name
 valueunknown/value
/parameter
parameter
 namepassword/name
 valueunknown/value
/parameter

!-- Class name for the informix treiber --
parameter
   namedriverClassName/name
   valuecom.informix.jdbc.IfxDriver/value
/parameter

parameter
  nameurl/name
  value

jdbc:informix-sqli://s0062033.vt.bb.de:300056/coadb:informixserver=coadbzentral
  /value
/parameter

   parameter
nameremoveAbandoned/name
 valuetrue/value
   /parameter
parameter
  nameremoveAbandonedTimeout/name
  value300/value !-- in second --
/parameter

   parameter
  namelogAbandoned/name
  valuetrue/value
/parameter

  /ResourceParams
/DefaultContext


thanks for any hint 

Mohammed

-Ursprüngliche Nachricht-
Von: Steve Kirk [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 9. November 2004 01:40
An: 'Eric Wulff'; 'Tomcat Users List'
Betreff: RE: connection pooling



Worth clarifyig what we are meaning by DBCP.  The DBCP I was referring to
was the specific implementation of connection pooling that is part of
Jakarta Commons: 
http://jakarta.apache.org/commons/dbcp/ 

There are other pooling implementations which are alternatives to Commons
DBCP.

Some DB drivers included pooling support as-is.  Others do not.  For those
that do not, you need to implement pooling by building code around the
standard driver.  You used to have to do this yourself, but now there is
DBCP to take care of this for you.  DBCP is a wrapper used around a
non-pooling DB driver.

So, hence my question, are you intending to use DBCP, or does your Informix
driver include pooling?

From the JNDI/JDBC guides it appears that you have the choice of using DBCP
or not (although there is one aspect of the docs that seem slightly unclear
on that, which I am going start another thread to clear up).  The configs
are similar.  Personally I have only got the DBCP approach to work, hence my
suggestion of using that, for which you need to include the factory
parameter.  What this does is basically tells TC to call DBCP rather than
your database driver when making a connection - DBCP then calls your DB
driver if and when it needs to.

I think I'm right in saying that if you don't explcitly use DBCP, and your
DB driver does not support pooling, you will end up with non-pooled
connections.  The webapp will still work but you will not have the
advantages of pooling.

In case it helps, here are my ResourceParams.  Note that I have both
factory and driverClassName:

ResourceParams name=jdbc/myDb
parameter
namefactory/name

valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
namedriverClassName/name
valuecom.mysql.jdbc.Driver/value
/parameter
parameter
nameusername/name
valueme/value
/parameter
parameter
namepassword/name
valuesecret

Re: AW: connection pooling

2004-11-09 Thread Nishant Deshpande

I've been dealing with similar issues recently. Basically your
reference in web.xml is not 'pointing' to the resource you defined in
server.xml for some reason, which is why if you examine the datasource
you get, you will see all the fields set to null (as indicated by the
error).

Try to create a context for your webapp in server.xml and put your
resource in there as a first step to debug.

If this doesn't work, check your server.xml is being read - i think
the log will tell you (?) and / or try with a simple server.xml to
eliminate any xml errors.


On Tue, 9 Nov 2004 14:25:41 +0100, Akacem Mohammed
[EMAIL PROTECTED] wrote:
 Hello,
 
 I am stuck in the same Probleme as Erik. I did exactly what in the e-mails 
 suggested is with no success.
 I am runing TC 5.0.28 und try to get a connection to an informix database.
 I got the following Error Message:
 
  org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of 
 class '' for connect URL 'null'
 
 mycode :
 
 try {
 initCtx = new InitialContext();
 envCtx = (Context) initCtx.lookup(java:comp/env);
 ds = (DataSource) envCtx.lookup(jdbc/SteaDB);
 } catch (NamingException e) {
 // TODO Auto-generated catch block
 
 e.printStackTrace();
 }
 try {
   conn=ds.getConnection();
 } catch (SQLException e2) {
 // TODO Auto-generated catch block
 e2.printStackTrace();
 }
 
 My Configuration is as follow:
 
 web.xml :
 
   resource-ref
   descriptionDB Connection to informix/description
   res-ref-namejdbc/SteaDB/res-ref-name
   res-typejavax.sql.DataSource/res-type
   res-authContainer/res-auth
   /resource-ref
 
 server.xml :
 
 DefaultContext
   Resource name=jdbc/SteaDB auth=Container type=javax.sql.DataSource/
 
   ResourceParams name=jdbc/SteaDB
 parameter
   namefactory/name
   valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
 /parameter
!-- Maximum time to wait for a dB connection to become available
  in ms, in this example 10 seconds. An Exception is thrown if
  this timeout is exceeded.  Set to -1 to wait indefinitely.
  --
 parameter
   namemaxWait/name
   value1/value
 /parameter
 
 !-- username and password for dB connections  --
 parameter
  nameusername/name
  valueunknown/value
 /parameter
 parameter
  namepassword/name
  valueunknown/value
 /parameter
 
 !-- Class name for the informix treiber --
 parameter
namedriverClassName/name
valuecom.informix.jdbc.IfxDriver/value
 /parameter
 
 parameter
   nameurl/name
   value
 
 jdbc:informix-sqli://s0062033.vt.bb.de:300056/coadb:informixserver=coadbzentral
   /value
 /parameter
 
parameter
 nameremoveAbandoned/name
  valuetrue/value
/parameter
 parameter
   nameremoveAbandonedTimeout/name
   value300/value !-- in second --
 /parameter
 
parameter
   namelogAbandoned/name
   valuetrue/value
 /parameter
 
   /ResourceParams
 /DefaultContext
 
 thanks for any hint
 
 Mohammed
 
 -Ursprüngliche Nachricht-
 Von: Steve Kirk [mailto:[EMAIL PROTECTED]
 Gesendet: Dienstag, 9. November 2004 01:40
 An: 'Eric Wulff'; 'Tomcat Users List'
 Betreff: RE: connection pooling
 
 Worth clarifyig what we are meaning by DBCP.  The DBCP I was referring to
 was the specific implementation of connection pooling that is part of
 Jakarta Commons:
 http://jakarta.apache.org/commons/dbcp/
 
 There are other pooling implementations which are alternatives to Commons
 DBCP.
 
 Some DB drivers included pooling support as-is.  Others do not.  For those
 that do not, you need to implement pooling by building code around the
 standard driver.  You used to have to do this yourself, but now there is
 DBCP to take care of this for you.  DBCP is a wrapper used around a
 non-pooling DB driver.
 
 So, hence my question, are you intending to use DBCP, or does your Informix
 driver include pooling?
 
 From the JNDI/JDBC guides it appears that you have the choice of using DBCP
 or not (although there is one aspect of the docs that seem slightly unclear
 on that, which I am going start another thread to clear up).  The configs
 are similar.  Personally I have only got the DBCP approach to work, hence my
 suggestion of using that, for which you need to include the factory
 parameter.  What this does is basically tells TC to call DBCP rather than
 your database driver when making a connection - DBCP then calls your DB
 driver if and when it needs to.
 
 I think I'm right in saying that if you don't explcitly use DBCP, and your
 DB driver does not support pooling, you will end up with non-pooled
 connections.  The webapp will still work but you will not have

Re: AW: connection pooling

2004-11-09 Thread Eric Wulff

Hi Mohammed, The resource-ref of your web.xml looks alright.  While
the DefaultContext should work if you place it in the correct
location(see notes below) within your server.xml, I doubt you want
this to be your final solution.  My final fix was suggested by Steve
and noted here...

Copy the Context... (you need to change your DefaultContext tag to a
Context tag) from your server.xml to a file all its own and name that
file myapp.xml(in your case I guess that would be SteaDB.xml).  Then
mv that file to $CATALINA_HOME/conf/Catalina/localhost/

Restart your app or shutdown and startup Tomcat and you should be all set.

Let me know how it goes.
Eric

Notes:
- I'm not sure if DefaultContext or Context within your server.xml
have any effect once you have a myapp.xml at
$CATALINA_HOME/conf/Catalina/localhost/.  I still have a Context in my
server.xml.

- I don't think it matters but fyi, my Context only includes a
Resource, and then Resource-Params as follows: username, password,
driverClass, and url.

- When working with the DefaultContext, location for that tag should
be within the Engine...  tag having the Standalone attribute.  This
likely needs to be un-commented, hence you will need to comment out
the Engine...  tag with the Catlina attribute, which is likely just
below in the server.xml.


On Tue, 9 Nov 2004 14:25:41 +0100, Akacem Mohammed
[EMAIL PROTECTED] wrote:
 Hello,
 
 I am stuck in the same Probleme as Erik. I did exactly what in the e-mails 
 suggested is with no success.
 I am runing TC 5.0.28 und try to get a connection to an informix database.
 I got the following Error Message:
 
  org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of 
 class '' for connect URL 'null'
 
 mycode :
 
 try {
 initCtx = new InitialContext();
 envCtx = (Context) initCtx.lookup(java:comp/env);
 ds = (DataSource) envCtx.lookup(jdbc/SteaDB);
 } catch (NamingException e) {
 // TODO Auto-generated catch block
 
 e.printStackTrace();
 }
 try {
   conn=ds.getConnection();
 } catch (SQLException e2) {
 // TODO Auto-generated catch block
 e2.printStackTrace();
 }
 
 My Configuration is as follow:
 
 web.xml :
 
   resource-ref
   descriptionDB Connection to informix/description
   res-ref-namejdbc/SteaDB/res-ref-name
   res-typejavax.sql.DataSource/res-type
   res-authContainer/res-auth
   /resource-ref
 
 server.xml :
 
 DefaultContext
   Resource name=jdbc/SteaDB auth=Container type=javax.sql.DataSource/
 
   ResourceParams name=jdbc/SteaDB
 parameter
   namefactory/name
   valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
 /parameter
!-- Maximum time to wait for a dB connection to become available
  in ms, in this example 10 seconds. An Exception is thrown if
  this timeout is exceeded.  Set to -1 to wait indefinitely.
  --
 parameter
   namemaxWait/name
   value1/value
 /parameter
 
 !-- username and password for dB connections  --
 parameter
  nameusername/name
  valueunknown/value
 /parameter
 parameter
  namepassword/name
  valueunknown/value
 /parameter
 
 !-- Class name for the informix treiber --
 parameter
namedriverClassName/name
valuecom.informix.jdbc.IfxDriver/value
 /parameter
 
 parameter
   nameurl/name
   value
 
 jdbc:informix-sqli://s0062033.vt.bb.de:300056/coadb:informixserver=coadbzentral
   /value
 /parameter
 
parameter
 nameremoveAbandoned/name
  valuetrue/value
/parameter
 parameter
   nameremoveAbandonedTimeout/name
   value300/value !-- in second --
 /parameter
 
parameter
   namelogAbandoned/name
   valuetrue/value
 /parameter
 
   /ResourceParams
 /DefaultContext
 
 thanks for any hint
 
 Mohammed
 
 -Ursprüngliche Nachricht-
 Von: Steve Kirk [mailto:[EMAIL PROTECTED]
 Gesendet: Dienstag, 9. November 2004 01:40
 An: 'Eric Wulff'; 'Tomcat Users List'
 Betreff: RE: connection pooling
 
 Worth clarifyig what we are meaning by DBCP.  The DBCP I was referring to
 was the specific implementation of connection pooling that is part of
 Jakarta Commons:
 http://jakarta.apache.org/commons/dbcp/
 
 There are other pooling implementations which are alternatives to Commons
 DBCP.
 
 Some DB drivers included pooling support as-is.  Others do not.  For those
 that do not, you need to implement pooling by building code around the
 standard driver.  You used to have to do this yourself, but now there is
 DBCP to take care of this for you.  DBCP is a wrapper used around a
 non-pooling DB driver.
 
 So, hence my question, are you intending to use DBCP, or does your Informix
 driver include pooling?
 
 From the JNDI/JDBC

Connection pooling under Tomcat 5.0.28 Probleme

2004-11-08 Thread Akacem Mohammed

Hello every body,

I have read in die archive the e-mail exchange  about configuring Datasource in 
Tomcat for connection pooling. ( I also read the Tomcat doc )

the jar file commons-collection- 3.1.jar, commons-dbcp-1.2.1.jar, 
commons-pool-1.2.jar und the database driver ifjdbc.jar are in the commons/lib 
directory.

I got the following Mersage Cannot create JDBC driver of class '' for connect 
URL 'null' ( someone on the list experienced the same thing with the same 
Message )

My Configuration is as follow: ( I try to access an informix database )

web.xml :

  resource-ref
  descriptionDB Connection to informix/description
  res-ref-namejdbc/SteaDB/res-ref-name
  res-typejavax.sql.DataSource/res-type
  res-authContainer/res-auth
  /resource-ref


Server.xml : 

DefaultContext
  Resource name=jdbc/SteaDB auth=Container type=javax.sql.DataSource/

  ResourceParams name=jdbc/SteaDB
parameter
  namefactory/name
  valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
   !-- Maximum time to wait for a dB connection to become available
 in ms, in this example 10 seconds. An Exception is thrown if
 this timeout is exceeded.  Set to -1 to wait indefinitely.
 --
parameter
  namemaxWait/name
  value1/value
/parameter

!-- username and password for dB connections  --
parameter
 nameusername/name
 valueusernamer/value
/parameter
parameter
 namepassword/name
 valuedfdfdf/value
/parameter

!-- Class name for the informix treiber --
parameter
   namedriverClassName/name
   valuecom.informix.jdbc.IfxDriver/value
/parameter

parameter
  nameurl/name
  value

jdbc:informix-sqli://s0062033.vt.bb.de:300056/coadb:informixserver=coadbzentral
  /value
/parameter

   parameter
nameremoveAbandoned/name
 valuetrue/value
   /parameter
parameter
  nameremoveAbandonedTimeout/name
  value300/value !-- in second --
/parameter

   parameter
  namelogAbandoned/name
  valuetrue/value
/parameter

  /ResourceParams
/DefaultContext

Thank you for your help

Mohammed


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: connection pooling

2004-11-08 Thread Steve Kirk


Worth clarifyig what we are meaning by DBCP.  The DBCP I was referring to
was the specific implementation of connection pooling that is part of
Jakarta Commons: 
http://jakarta.apache.org/commons/dbcp/ 

There are other pooling implementations which are alternatives to Commons
DBCP.

Some DB drivers included pooling support as-is.  Others do not.  For those
that do not, you need to implement pooling by building code around the
standard driver.  You used to have to do this yourself, but now there is
DBCP to take care of this for you.  DBCP is a wrapper used around a
non-pooling DB driver.

So, hence my question, are you intending to use DBCP, or does your Informix
driver include pooling?

From the JNDI/JDBC guides it appears that you have the choice of using DBCP
or not (although there is one aspect of the docs that seem slightly unclear
on that, which I am going start another thread to clear up).  The configs
are similar.  Personally I have only got the DBCP approach to work, hence my
suggestion of using that, for which you need to include the factory
parameter.  What this does is basically tells TC to call DBCP rather than
your database driver when making a connection - DBCP then calls your DB
driver if and when it needs to.

I think I'm right in saying that if you don't explcitly use DBCP, and your
DB driver does not support pooling, you will end up with non-pooled
connections.  The webapp will still work but you will not have the
advantages of pooling.

In case it helps, here are my ResourceParams.  Note that I have both
factory and driverClassName:

ResourceParams name=jdbc/myDb
parameter
namefactory/name

valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter
parameter
namedriverClassName/name
valuecom.mysql.jdbc.Driver/value
/parameter
parameter
nameusername/name
valueme/value
/parameter
parameter
namepassword/name
valuesecret/value
/parameter
parameter
 nameurl/name
 valuejdbc:mysql://localhost:3306/myDb/value
/parameter
/ResourceParams


 -Original Message-
 From: Eric Wulff [mailto:[EMAIL PROTECTED] 
 Sent: Friday 05 November 2004 18:34
 To: Steve Kirk
 Cc: Tomcat Users List
 Subject: Re: connection pooling
 
 
 Steve, I am trying to use DBCP(hence the subject of the thread) and I
 believe I have a driver that supports it.  Especially considering that
 the connection works when I wrap my data resource in a DefaultContext
 tag inside a stand alone Engine tag(server.xml), instead of inside a
 Context tag(how all instructions I've followed so far suggest).
 
 This means my driver support DBCP, correct?
 
 The only source code I imagine would help is the code I use to gain
 connection...
 
 Context initialContext = new InitialContext();
 Context context = (Context) initialContext.lookup(java:comp/env);
 DataSource dataSource = (DataSource) context.lookup(jdbc/wms);
 connection = dataSource.getConnection();
 
 I have seen no mention of this factory class parameter you speak of. 
 I'm using TC 5.0.28.  I'll try it.
 
 thx much for your help
 Eric
 
 
 On Fri, 5 Nov 2004 13:30:35 -, Steve Kirk
 [EMAIL PROTECTED] wrote:
  Eric - you are correct,  you do not need both 
 resource-ref and Resource
  (although I've found that having both does not cause a problem).
  
  Back to your problem.
  
  The error message indicates that TC cannot find the Resource.
  
  I'm not sure if you are trying to use DBCP or not (in other 
 words, does the
  informix driver support pooling on its own, or do you in 
 fact need DBCP or
  some other implementation wrapped around it)?  You have
  res-typejavax.sql.DataSource/res-type but do not list 
 the factory class
  under your Resource, e.g. :
  parameter
  namefactory/name
  
 valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
  /parameter
  
  I have not seen any Java source code on this thread, maybe 
 you posted it
  before I started reading it.
  
  Thinking slightly laterally I'll pass on something I 
 learned from Yoav
  recently on this list you don't need to use 
 container-managed resources
  to do connection pooling.  In other words you don't need to 
 set any Resource
  or Context to get it to work.
  
  
  
   -Original Message-
   From: Eric Wulff [mailto:[EMAIL PROTECTED]
   Sent: Friday 05 November 2004 05:57
   To: Tomcat Users List; Atishay Kumar
   Subject: Re: connection pooling
  
  
   Thx for your input but, as mentioned in my previous message, I've
   tried this and it does not work.  Also, considering my web.xml I
   shouldn't need this, correct?  I have a resource-ref in 
 my web.xml.
  
   Eric

Re: connection pooling

2004-11-08 Thread Eric Wulff

Well, my informix driver does support connection pooling as-is so I do
not need to use a Jakarta Commons DBCP wrapper in order to take
advantage of database connection pooling.  Thx for clarifying and for
sharing your ResourceParams.  I need to study this issue some more in
general since I only have a surface understanding of what connection
pooling really is and what it's advantages are.  For now, my app is
successfully utilizing connection pooling, as far as I can tell.  My
problem, which initiated this thread, has been solved by putting a
myapp.xml with the necessary context in my
$CATALINA_HOME/conf/Catalina/localhost/ directory.

thx
Eric


On Tue, 9 Nov 2004 00:40:23 -, Steve Kirk
[EMAIL PROTECTED] wrote:
 
 Worth clarifyig what we are meaning by DBCP.  The DBCP I was referring to
 was the specific implementation of connection pooling that is part of
 Jakarta Commons:
 http://jakarta.apache.org/commons/dbcp/
 
 There are other pooling implementations which are alternatives to Commons
 DBCP.
 
 Some DB drivers included pooling support as-is.  Others do not.  For those
 that do not, you need to implement pooling by building code around the
 standard driver.  You used to have to do this yourself, but now there is
 DBCP to take care of this for you.  DBCP is a wrapper used around a
 non-pooling DB driver.
 
 So, hence my question, are you intending to use DBCP, or does your Informix
 driver include pooling?
 
 From the JNDI/JDBC guides it appears that you have the choice of using DBCP
 or not (although there is one aspect of the docs that seem slightly unclear
 on that, which I am going start another thread to clear up).  The configs
 are similar.  Personally I have only got the DBCP approach to work, hence my
 suggestion of using that, for which you need to include the factory
 parameter.  What this does is basically tells TC to call DBCP rather than
 your database driver when making a connection - DBCP then calls your DB
 driver if and when it needs to.
 
 I think I'm right in saying that if you don't explcitly use DBCP, and your
 DB driver does not support pooling, you will end up with non-pooled
 connections.  The webapp will still work but you will not have the
 advantages of pooling.
 
 In case it helps, here are my ResourceParams.  Note that I have both
 factory and driverClassName:
 
 ResourceParams name=jdbc/myDb
 parameter
 namefactory/name
 
 valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
 /parameter
 parameter
 namedriverClassName/name
 valuecom.mysql.jdbc.Driver/value
 /parameter
 parameter
 nameusername/name
 valueme/value
 /parameter
 parameter
 namepassword/name
 valuesecret/value
 /parameter
 parameter
  nameurl/name
  valuejdbc:mysql://localhost:3306/myDb/value
 /parameter
 /ResourceParams
 
 
 
 
  -Original Message-
  From: Eric Wulff [mailto:[EMAIL PROTECTED]
  Sent: Friday 05 November 2004 18:34
  To: Steve Kirk
  Cc: Tomcat Users List
  Subject: Re: connection pooling
 
 
  Steve, I am trying to use DBCP(hence the subject of the thread) and I
  believe I have a driver that supports it.  Especially considering that
  the connection works when I wrap my data resource in a DefaultContext
  tag inside a stand alone Engine tag(server.xml), instead of inside a
  Context tag(how all instructions I've followed so far suggest).
 
  This means my driver support DBCP, correct?
 
  The only source code I imagine would help is the code I use to gain
  connection...
 
  Context initialContext = new InitialContext();
  Context context = (Context) initialContext.lookup(java:comp/env);
  DataSource dataSource = (DataSource) context.lookup(jdbc/wms);
  connection = dataSource.getConnection();
 
  I have seen no mention of this factory class parameter you speak of.
  I'm using TC 5.0.28.  I'll try it.
 
  thx much for your help
  Eric
 
 
  On Fri, 5 Nov 2004 13:30:35 -, Steve Kirk
  [EMAIL PROTECTED] wrote:
   Eric - you are correct,  you do not need both
  resource-ref and Resource
   (although I've found that having both does not cause a problem).
  
   Back to your problem.
  
   The error message indicates that TC cannot find the Resource.
  
   I'm not sure if you are trying to use DBCP or not (in other
  words, does the
   informix driver support pooling on its own, or do you in
  fact need DBCP or
   some other implementation wrapped around it)?  You have
   res-typejavax.sql.DataSource/res-type but do not list
  the factory class
   under your Resource, e.g. :
   parameter
   namefactory/name
  
  valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
   /parameter

Re: AW: {an alternative}Re: connection pooling

2004-11-06 Thread Ben Souther

 What escapes me is, why is this not more obviously documented? 
 Perhaps it's in the Tomcat docs but I mostly abandoned those some time
 ago as they are so amazingly detailed and lengthy that unless you want
 to become a TC guru, which I am inspired to try and be more like,
 there is simply too much info.
 
How can you post a paragraph like that and expect to be taken seriously?
In one breath, you complain about something not being documented, then 
state that you don't read the documentation because it's too detailed?

How can you know what is or isn't obviously documented if you don't read
the documentation?














-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: {an alternative}Re: connection pooling

2004-11-06 Thread Atishay Kumar

 in CATALINA_HOME/commons/lib
 
  Eric
 
  On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
  [EMAIL PROTECTED] wrote:
   No, you don't need that many params. I think your problem might be the
 
 
   driver. Where did you drop off your informix jdbc jar?
  
  
   -Original Message-
   From: Eric Wulff [mailto:[EMAIL PROTECTED]
   Sent: October 7, 2004 5:56 PM
   To: Tomcat Users List
   Subject: Re: connection pooling
  
   Yes, I have added Resource name=... .  Now different errors are 
   reported
   via stack trace as I posted in response to Atishay's suggestion that I 
   add
   this.  I'll try adding your suggestions and see what happens.  Also, you
   suggest adding many parameters.  Are they necessary for simply making a
   connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left 
   all
  
   --
   :)
   Atishay Kumar
   Btech, SEM VII
   DA-IICT
   Gandhinagar - 382009
   India
   ph: +91 9825383948
   /
* Learn the rules as you would need them to break them properly *
/
  
 
 


-- 
:)
Atishay Kumar
Btech, SEM VII
DA-IICT
Gandhinagar - 382009
India
ph: +91 9825383948
/
 * Learn the rules as you would need them to break them properly *
 /

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: connection pooling

2004-11-06 Thread V D

How about try to move your application (wms) out of the webapps 
directory, let's say: c:\wms

Then in the server.xml, try to change docBase in the context:
docBase=c:\wms
Now, see if your application works or give a different error.  Remember to drop the 
jdbc library into the common/lib folder.

Eric Wulff wrote:
Hi all, I'm returning to a problem I couldn't solve the first time,
about two months ago, and still can't seem to figure out.  I can't get
a db connection using connection pools.  I get the exception listed
below, same as so many have previously, but nothing I've found seems
to works.  Below are my specs.  Anyone with concrete advise/direction
on how to get
this working?
Also, I noticed in many solutions the suggestion was made to edit the
myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/. 
However, there is no myapp.xml in that directory on my server. Just 2
.xml's related to other applications and a manager.xml which I'm not
sure what it's related to.

OS: FC2
Tomcat 5.0.28
exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
JDBC driver class '' for connect URL 'null'
WEB-INF web xml: code inserted AFTER all servlet mappings...
resource-ref
res-ref-namejdbc/wms/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
server xml(tried this with and without a Resource name)...
Context path=/wms docBase=wms debug=0 reloadable=true
   ResourceParams name=jdbc/wms
 parameter
   nameusername/name
   valuewhatever/value
 /parameter
 parameter
   namepassword/name
   valuewhatever/value
 /parameter
 parameter
   namedriverClassName/name
   valuecom.informix.jdbc.IfxDriver/value
 /parameter
  parameter
nameurl/name

valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
/parameter
   /ResourceParams
 /Context
I have the following jars in my CATALINA_HONE/common/lib and I also
tried putting the db driver and commons-collections, dbcp, and pool in
my WEB-INF/lib with no success.  They are all mode 644.
ant.jar
ant-launcher.jar
commons-collections-3.1.jar
commons-dbcp-1.2.1.jar
commons-el.jar
commons-pool-1.2.jar
ifxjdbc.jar (the necessary informix driver)
jar.txt
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
mysql-connector-java-3.0.15-ga-bin.jar
naming-common.jar
naming-factory.jar
naming-java.jar
naming-resources.jar
servlet-api.jar

On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
[EMAIL PROTECTED] wrote:
 

hi,
i am not sure but you may try downloading latest jar files for
following froom tomcat site and try them out. copy the old jar files
somewhere else and try using the latest jar files.
1) Commons Collections
2)Commons DBCP
3)Commons Pool

On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
   

Except that the driver works for connecting if I'm not utilizing a
connection pool, i.e., I am able to connect to the db and manipulate
data via DriverManager.getConnection(url, db, pwd).
The driver is located in CATALINA_HOME/commons/lib
Eric
On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
[EMAIL PROTECTED] wrote:
 

No, you don't need that many params. I think your problem might be the
   

 

driver. Where did you drop off your informix jdbc jar?
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: October 7, 2004 5:56 PM
To: Tomcat Users List
Subject: Re: connection pooling
Yes, I have added Resource name=... .  Now different errors are reported
via stack trace as I posted in response to Atishay's suggestion that I add
this.  I'll try adding your suggestions and see what happens.  Also, you
suggest adding many parameters.  Are they necessary for simply making a
connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left all
your suggestions out.
Including the Resource tag, but that seems critical for connection.
Eric
On Thu, 7 Oct 2004 17:14:27 -0400, Phillip Qin [EMAIL PROTECTED]
wrote:
   

1. web.xml: OK
2. context.xml on context of server.xml:
   Resource name=jdbc/test_connect auth=Container
type=javax.sql.DataSource/ = have you added this?
   ResourceParams name=jdbc/test_connect
   parameter
   namedriverClassName/name
   valueyour.jdbc.driver/value
   /parameter
   parameter
   nameurl/name
   valueyour.jdbc.url/value
   /parameter
   parameter
   nameusername/name
   valueyouruser/value
   /parameter
   parameter
   namepassword/name
   valueyourpass/value
   /parameter
   parameter
   namemaxActive/name
   value20/value
   /parameter
   parameter
   namemaxIdle/name
   value10/value
   /parameter
   parameter
   nameminIdle/name
   value10/value

RE: connection pooling

2004-11-05 Thread Steve Kirk

Eric - you are correct,  you do not need both resource-ref and Resource
(although I've found that having both does not cause a problem).

Back to your problem.

The error message indicates that TC cannot find the Resource.

I'm not sure if you are trying to use DBCP or not (in other words, does the
informix driver support pooling on its own, or do you in fact need DBCP or
some other implementation wrapped around it)?  You have
res-typejavax.sql.DataSource/res-type but do not list the factory class
under your Resource, e.g. :
parameter
namefactory/name
valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
/parameter

I have not seen any Java source code on this thread, maybe you posted it
before I started reading it.

Thinking slightly laterally I'll pass on something I learned from Yoav
recently on this list you don't need to use container-managed resources
to do connection pooling.  In other words you don't need to set any Resource
or Context to get it to work.

 -Original Message-
 From: Eric Wulff [mailto:[EMAIL PROTECTED] 
 Sent: Friday 05 November 2004 05:57
 To: Tomcat Users List; Atishay Kumar
 Subject: Re: connection pooling
 
 
 Thx for your input but, as mentioned in my previous message, I've
 tried this and it does not work.  Also, considering my web.xml I
 shouldn't need this, correct?  I have a resource-ref in my web.xml.
 
 Eric
 
 
 On Fri, 5 Nov 2004 11:01:05 +0530, Atishay Kumar
 [EMAIL PROTECTED] wrote:
  
  Pls do the following change after context.. and u are on!!
  cheers
  
  
  On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff 
 [EMAIL PROTECTED] wrote:
   Hi all, I'm returning to a problem I couldn't solve the 
 first time,
   about two months ago, and still can't seem to figure out. 
  I can't get
   a db connection using connection pools.  I get the 
 exception listed
   below, same as so many have previously, but nothing I've 
 found seems
   to works.  Below are my specs.  Anyone with concrete 
 advise/direction
   on how to get
   this working?
  
   Also, I noticed in many solutions the suggestion was made 
 to edit the
   myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
   However, there is no myapp.xml in that directory on my 
 server. Just 2
   .xml's related to other applications and a manager.xml 
 which I'm not
   sure what it's related to.
  
   OS: FC2
   Tomcat 5.0.28
  
   exception: org.apache.commons.dbcp.SWLNestedException: 
 Cannot create
   JDBC driver class '' for connect URL 'null'
  
   WEB-INF web xml: code inserted AFTER all servlet mappings...
   resource-ref
   res-ref-namejdbc/wms/res-ref-name
   res-typejavax.sql.DataSource/res-type
   res-authContainer/res-auth
   /resource-ref
  
   server xml(tried this with and without a Resource name)...
   Context path=/wms docBase=wms debug=0 reloadable=true
  
  Resource name=jdbc/wms auth=Container 
 type=javax.sql.DataSource/
  
  
  
   ResourceParams name=jdbc/wms
 parameter
   nameusername/name
   valuewhatever/value
 /parameter
 parameter
   namepassword/name
   valuewhatever/value
 /parameter
 parameter
   namedriverClassName/name
   valuecom.informix.jdbc.IfxDriver/value
 /parameter
 parameter
   nameurl/name
   
 valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORM
 IXSERVER=serverName/value
   /parameter
   /ResourceParams
 /Context
  
   I have the following jars in my 
 CATALINA_HONE/common/lib and I also
   tried putting the db driver and commons-collections, 
 dbcp, and pool in
   my WEB-INF/lib with no success.  They are all mode 644.
  
   ant.jar
   ant-launcher.jar
   commons-collections-3.1.jar
   commons-dbcp-1.2.1.jar
   commons-el.jar
   commons-pool-1.2.jar
   ifxjdbc.jar (the necessary informix driver)
   jar.txt
   jasper-compiler.jar
   jasper-runtime.jar
   jsp-api.jar
   mysql-connector-java-3.0.15-ga-bin.jar
   naming-common.jar
   naming-factory.jar
   naming-java.jar
   naming-resources.jar
   servlet-api.jar
  
   On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
   [EMAIL PROTECTED] wrote:
hi,
 i am not sure but you may try downloading latest jar files for
following froom tomcat site and try them out. copy the 
 old jar files
somewhere else and try using the latest jar files.
1) Commons Collections
2)Commons DBCP
3)Commons Pool
   
   
   
   
On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff 
 [EMAIL PROTECTED] wrote:
 Except that the driver works for connecting if I'm 
 not utilizing a
 connection pool, i.e., I am able to connect to the db 
 and manipulate
 data via DriverManager.getConnection(url, db, pwd).

 The driver is located in CATALINA_HOME/commons/lib

 Eric

 On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
 [EMAIL PROTECTED] wrote

RE: connection pooling

2004-11-05 Thread Shapira, Yoav


Hi,

Eric - you are correct,  you do not need both resource-ref and
Resource

That's only because we try to accommodate less able
developers/administrators.  You DO need resource-ref if you want your
app to be compliant with the Servlet Specification and portable to other
containers.

Yoav Shapira http://www.yoavshapira.com



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: connection pooling

2004-11-05 Thread Steve Kirk


Ah yes I agree, but that's not quite what I was saying.  Eric, sorry if that
was misleading.

Eric has a resource-ref already. I meant that if you have resource-ref
you do not need Resource as well in TC, because this is what the TC docs
say, and the Resource tag is a TC invention rather than something
required by the servlet spec.

I think Yoav is saying that in fact TC allows you to be slightly loose by
omitting the resource-ref as long as you have the Resource, even though
strictly speaking you are not spec-compliant if you do this.

 -Original Message-
 From: Shapira, Yoav [mailto:[EMAIL PROTECTED] 
 Sent: Friday 05 November 2004 13:32
 To: Tomcat Users List
 Subject: RE: connection pooling
 
 
 
 Hi,
 
 Eric - you are correct,  you do not need both resource-ref and
 Resource
 
 That's only because we try to accommodate less able
 developers/administrators.  You DO need resource-ref if you 
 want your
 app to be compliant with the Servlet Specification and 
 portable to other
 containers.
 
 Yoav Shapira http://www.yoavshapira.com
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: {an alternative}Re: connection pooling

2004-11-05 Thread Steve Kirk

Eric said:
 Also, I noticed in many solutions the suggestion was made to edit the
 myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/. 
 However, there is no myapp.xml in that directory on my server. Just 2
 .xml's related to other applications and a manager.xml which I'm not
 sure what it's related to.

when you deploy a mywebapp from a warfile that includes a
META-INF/context.xml, TC copies that file to
conf/Catalina/localhost/mywebapp.xml.  having said that there appear to be
situations where TC does and does not copy that file.  all I can say is that
it works for me (5.0.28).

Or, you can create that file yourself.

whichever way it's created, its contents are taken as though they were
inserted as a context under the Catalina/localhost host in server.xml.  this
is the preferred way to config a context since v5.x (rather than putting it
in server.xml).

manager.xml is for the manager webapp.

 -Original Message-
 From: Nick Pellow [mailto:[EMAIL PROTECTED] 
 Sent: Friday 05 November 2004 07:40
 To: Tomcat Users List
 Subject: AW: {an alternative}Re: connection pooling
 
 
 HI Eric,
 
 
 I have seen the same error your are getting. I am using tomcat 5.0.28.
 Make sure that you have removed the expanded war directories, from
 webapps and ${CATALINA_HOME}/work before restarting.
 
 Also look inside
 those other context.xmls inside 
 ${CATALINA_HOME}/conf/Catalina/localhost
 and make sure that they do not define a context with path=/wms.
 
 Cheers,
 nick.
 
 -Ursprungliche Nachricht-
 Von: Eric Wulff [mailto:[EMAIL PROTECTED]
 Gesendet: Freitag, 5. November 2004 07:35
 An: Atishay Kumar
 Cc: Tomcat Users List
 Betreff: Re: {an alternative}Re: connection pooling
 
 
 Atishay, the DefaultContext does work once I comment out the other
 Engine element.  You mentioned that means something is wrong with my
 Context?  So what next?
 
 many thx
 Eric
 
 
 On Thu, 4 Nov 2004 22:21:57 -0800, Eric Wulff 
 [EMAIL PROTECTED] wrote:
  This did not work.  In looking for the Engine element you 
 speak of I
  didn't find it exactly.  I did find it with it with an 
 extra attribute
  Engine name=Standalone... jvmRoute=jvm1.  Furthermore, this
  element was nested within the Service element and there 
 is another
  Engine name=Catalina... element.  I tried with and without the
  jvmRoute element.  No success.  Same exception.
 
  Eric
 
  On Fri, 5 Nov 2004 11:20:26 +0530, Atishay Kumar
 
 
  [EMAIL PROTECTED] wrote:
   If adding Resouce name .../ did not work..then try 
 following
  
   On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff 
 [EMAIL PROTECTED] wrote:
Hi all, I'm returning to a problem I couldn't solve 
 the first time,
about two months ago, and still can't seem to figure out.  I
 can't get
a db connection using connection pools.  I get the 
 exception listed
below, same as so many have previously, but nothing 
 I've found seems
to works.  Below are my specs.  Anyone with concrete 
 advise/direction
on how to get
this working?
   
Also, I noticed in many solutions the suggestion was 
 made to edit the
myapp.xml file located at 
 CATALINA_HOME/conf/Catalina/localhost/.
However, there is no myapp.xml in that directory on my 
 server. Just 2
.xml's related to other applications and a manager.xml 
 which I'm not
sure what it's related to.
   
OS: FC2
Tomcat 5.0.28
   
exception: org.apache.commons.dbcp.SWLNestedException: 
 Cannot create
JDBC driver class '' for connect URL 'null'
   
WEB-INF web xml: code inserted AFTER all servlet mappings...
   the following shld be  in
   web-app
resource-ref
   descriptionMy Datasource/description
res-ref-namejdbc/wms/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
   /web-app !-- I am sure u have this right--
   
server xml(tried this with and without a Resource name)...
   The following shld be under
   Engine name=Standalone defaultHost=localhost debug=0
  
   REplace
Context path=/wms docBase=wms debug=0 reloadable=true
   with
   DefaultContext
   Resource name=jdbc/wms auth=Container
 type=javax.sql.DataSource/
ResourceParams name=jdbc/wms
  parameter
nameusername/name
valuewhatever/value
  /parameter
  parameter
namepassword/name
valuewhatever/value
  /parameter
  parameter
namedriverClassName/name
valuecom.informix.jdbc.IfxDriver/value
  /parameter
  parameter
nameurl/name
   
 valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSER
 VER=serverName/value
/parameter
/ResourceParams
   replace
  /Context
   with
   /DefaultContext
   !--
   If this works them there is something wrong with your context. we
   shall figure that out later but first

Re: AW: {an alternative}Re: connection pooling

2004-11-05 Thread sven morales

   I thought I have read back in this same thread that
he had two Engine under a Service ?  Only one
Engine is allowed per Service to fix one problem. 

--- Nick Pellow [EMAIL PROTECTED] wrote:

 HI Eric,
 
 
 I have seen the same error your are getting. I am
 using tomcat 5.0.28.
 Make sure that you have removed the expanded war
 directories, from
 webapps and ${CATALINA_HOME}/work before
 restarting.
 
 Also look inside
 those other context.xmls inside
 ${CATALINA_HOME}/conf/Catalina/localhost
 and make sure that they do not define a context with
 path=/wms.
 
 Cheers,
 nick.
 
 -Ursprungliche Nachricht-
 Von: Eric Wulff [mailto:[EMAIL PROTECTED]
 Gesendet: Freitag, 5. November 2004 07:35
 An: Atishay Kumar
 Cc: Tomcat Users List
 Betreff: Re: {an alternative}Re: connection pooling
 
 
 Atishay, the DefaultContext does work once I
 comment out the other
 Engine element.  You mentioned that means something
 is wrong with my
 Context?  So what next?
 
 many thx
 Eric
 
 
 On Thu, 4 Nov 2004 22:21:57 -0800, Eric Wulff
 [EMAIL PROTECTED] wrote:
  This did not work.  In looking for the Engine
 element you speak of I
  didn't find it exactly.  I did find it with it
 with an extra attribute
  Engine name=Standalone... jvmRoute=jvm1. 
 Furthermore, this
  element was nested within the Service element
 and there is another
  Engine name=Catalina... element.  I tried
 with and without the
  jvmRoute element.  No success.  Same exception.
 
  Eric
 
  On Fri, 5 Nov 2004 11:20:26 +0530, Atishay Kumar
 
 
  [EMAIL PROTECTED] wrote:
   If adding Resouce name .../ did not
 work..then try following
  
   On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff
 [EMAIL PROTECTED] wrote:
Hi all, I'm returning to a problem I couldn't
 solve the first time,
about two months ago, and still can't seem to
 figure out.  I
 can't get
a db connection using connection pools.  I
 get the exception listed
below, same as so many have previously, but
 nothing I've found seems
to works.  Below are my specs.  Anyone with
 concrete advise/direction
on how to get
this working?
   
Also, I noticed in many solutions the
 suggestion was made to edit the
myapp.xml file located at
 CATALINA_HOME/conf/Catalina/localhost/.
However, there is no myapp.xml in that
 directory on my server. Just 2
.xml's related to other applications and a
 manager.xml which I'm not
sure what it's related to.
   
OS: FC2
Tomcat 5.0.28
   
exception:
 org.apache.commons.dbcp.SWLNestedException: Cannot
 create
JDBC driver class '' for connect URL 'null'
   
WEB-INF web xml: code inserted AFTER all
 servlet mappings...
   the following shld be  in
   web-app
resource-ref
   descriptionMy Datasource/description
   
 res-ref-namejdbc/wms/res-ref-name
   
 res-typejavax.sql.DataSource/res-type
   
 res-authContainer/res-auth
/resource-ref
   /web-app !-- I am sure u have this right--
   
server xml(tried this with and without a
 Resource name)...
   The following shld be under
   Engine name=Standalone
 defaultHost=localhost debug=0
  
   REplace
Context path=/wms docBase=wms debug=0
 reloadable=true
   with
   DefaultContext
   Resource name=jdbc/wms auth=Container
 type=javax.sql.DataSource/
ResourceParams name=jdbc/wms
  parameter
nameusername/name
valuewhatever/value
  /parameter
  parameter
namepassword/name
valuewhatever/value
  /parameter
  parameter
namedriverClassName/name
   
 valuecom.informix.jdbc.IfxDriver/value
  /parameter
  parameter
nameurl/name
   

valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSER
 VER=serverName/value
/parameter
/ResourceParams
   replace
  /Context
   with
   /DefaultContext
   !--
   If this works them there is something wrong
 with your context. we
   shall figure that out later but first
 DefaultContext should work!!
   restart tommy after making changes.
   hope it works!!
   --
   
I have the following jars in my
 CATALINA_HONE/common/lib and I also
tried putting the db driver and
 commons-collections, dbcp,
 and pool in
my WEB-INF/lib with no success.  They are all
 mode 644.
   
ant.jar
ant-launcher.jar
commons-collections-3.1.jar
commons-dbcp-1.2.1.jar
commons-el.jar
commons-pool-1.2.jar
ifxjdbc.jar (the necessary informix driver)
jar.txt
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
mysql-connector-java-3.0.15-ga-bin.jar
naming-common.jar
naming-factory.jar
naming-java.jar
naming-resources.jar
servlet-api.jar
   
On Fri, 8 Oct 2004 11:45:59 +0530, Atishay
 Kumar
[EMAIL PROTECTED] wrote:
 hi,
  i am not sure but you may try downloading
 latest jar files for
 following froom tomcat site

Re: connection pooling

2004-11-05 Thread Eric Wulff

Steve, I am trying to use DBCP(hence the subject of the thread) and I
believe I have a driver that supports it.  Especially considering that
the connection works when I wrap my data resource in a DefaultContext
tag inside a stand alone Engine tag(server.xml), instead of inside a
Context tag(how all instructions I've followed so far suggest).

This means my driver support DBCP, correct?

The only source code I imagine would help is the code I use to gain
connection...

Context initialContext = new InitialContext();
Context context = (Context) initialContext.lookup(java:comp/env);
DataSource dataSource = (DataSource) context.lookup(jdbc/wms);
connection = dataSource.getConnection();

I have seen no mention of this factory class parameter you speak of. 
I'm using TC 5.0.28.  I'll try it.

thx much for your help
Eric


On Fri, 5 Nov 2004 13:30:35 -, Steve Kirk
[EMAIL PROTECTED] wrote:
 Eric - you are correct,  you do not need both resource-ref and Resource
 (although I've found that having both does not cause a problem).
 
 Back to your problem.
 
 The error message indicates that TC cannot find the Resource.
 
 I'm not sure if you are trying to use DBCP or not (in other words, does the
 informix driver support pooling on its own, or do you in fact need DBCP or
 some other implementation wrapped around it)?  You have
 res-typejavax.sql.DataSource/res-type but do not list the factory class
 under your Resource, e.g. :
 parameter
 namefactory/name
 valueorg.apache.commons.dbcp.BasicDataSourceFactory/value
 /parameter
 
 I have not seen any Java source code on this thread, maybe you posted it
 before I started reading it.
 
 Thinking slightly laterally I'll pass on something I learned from Yoav
 recently on this list you don't need to use container-managed resources
 to do connection pooling.  In other words you don't need to set any Resource
 or Context to get it to work.
 
 
 
  -Original Message-
  From: Eric Wulff [mailto:[EMAIL PROTECTED]
  Sent: Friday 05 November 2004 05:57
  To: Tomcat Users List; Atishay Kumar
  Subject: Re: connection pooling
 
 
  Thx for your input but, as mentioned in my previous message, I've
  tried this and it does not work.  Also, considering my web.xml I
  shouldn't need this, correct?  I have a resource-ref in my web.xml.
 
  Eric
 
 
  On Fri, 5 Nov 2004 11:01:05 +0530, Atishay Kumar
  [EMAIL PROTECTED] wrote:
  
   Pls do the following change after context.. and u are on!!
   cheers
  
  
   On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff
  [EMAIL PROTECTED] wrote:
Hi all, I'm returning to a problem I couldn't solve the
  first time,
about two months ago, and still can't seem to figure out.
   I can't get
a db connection using connection pools.  I get the
  exception listed
below, same as so many have previously, but nothing I've
  found seems
to works.  Below are my specs.  Anyone with concrete
  advise/direction
on how to get
this working?
   
Also, I noticed in many solutions the suggestion was made
  to edit the
myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
However, there is no myapp.xml in that directory on my
  server. Just 2
.xml's related to other applications and a manager.xml
  which I'm not
sure what it's related to.
   
OS: FC2
Tomcat 5.0.28
   
exception: org.apache.commons.dbcp.SWLNestedException:
  Cannot create
JDBC driver class '' for connect URL 'null'
   
WEB-INF web xml: code inserted AFTER all servlet mappings...
resource-ref
res-ref-namejdbc/wms/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
   
server xml(tried this with and without a Resource name)...
Context path=/wms docBase=wms debug=0 reloadable=true
  
   Resource name=jdbc/wms auth=Container
  type=javax.sql.DataSource/
  
  
  
ResourceParams name=jdbc/wms
  parameter
nameusername/name
valuewhatever/value
  /parameter
  parameter
namepassword/name
valuewhatever/value
  /parameter
  parameter
namedriverClassName/name
valuecom.informix.jdbc.IfxDriver/value
  /parameter
  parameter
nameurl/name
   
  valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORM
  IXSERVER=serverName/value
/parameter
/ResourceParams
  /Context
   
I have the following jars in my
  CATALINA_HONE/common/lib and I also
tried putting the db driver and commons-collections,
  dbcp, and pool in
my WEB-INF/lib with no success.  They are all mode 644.
   
ant.jar
ant-launcher.jar
commons-collections-3.1.jar
commons-dbcp-1.2.1.jar
commons-el.jar
commons-pool-1.2.jar
ifxjdbc.jar (the necessary informix driver)
jar.txt
jasper-compiler.jar

Re: AW: {an alternative}Re: connection pooling

2004-11-05 Thread Eric Wulff

OK - Got It!  Thank you all many times over for your time and help on
this connection pool thing.  It is surprisingly difficult to maintain
a stable environment if you're a curious beginner.  I clearly need to
get a grip on Tomcat's process BUT it also seems abundantly clear that
docs/how to's for simply getting started with connection pools are
less than optimal.  What exactly was my problem?  Still not sure and
trying to narrow it down.  In the hopes of helping anyone on this
list, here's what FINALLY worked for me?

Again, I'm running TC 5.0.28 on Linux FC2

1.   I went in and cleared out ALL my test web-apps, of which I wrote
about 6 different toys via tutorials and on my own.  While I don't
nearly understand the reasons for much of the TC directory structure,
I traversed the following directories and 'rm -r -f' all the webaps I
created and no longer wanted with the thinking that somehow they might
be in the way...

the obvious...
CATALINA_HOME/webaps/
the less obvious to me...
CATALINA_HOME/work/StandAlone/localhost
CATALINA_HOME/work/Catalina/localhost

2.  This, I'm guessing, is more likely the key but I didn't test
between doing all this.  I created a new file, myapp.xml, in...

CATALINA_HOME/conf/Catalina/localhost/

and simply copied the related Context/Context(see prior emails)
from the server.xml in...
CATALINA_HOME/conf/

to this file.

What escapes me is, why is this not more obviously documented? 
Perhaps it's in the Tomcat docs but I mostly abandoned those some time
ago as they are so amazingly detailed and lengthy that unless you want
to become a TC guru, which I am inspired to try and be more like,
there is simply too much info.

Okay, I'm off to continue figuring why TC keeps crashing on me. 
Hopefully something I did here solved that problem too.

thx again all,
Eric

 
On Fri, 5 Nov 2004 08:39:30 +0100, Nick Pellow
[EMAIL PROTECTED] wrote:
 HI Eric,
 
 I have seen the same error your are getting. I am using tomcat 5.0.28.
 Make sure that you have removed the expanded war directories, from
 webapps and ${CATALINA_HOME}/work before restarting.
 
 Also look inside
 those other context.xmls inside ${CATALINA_HOME}/conf/Catalina/localhost
 and make sure that they do not define a context with path=/wms.
 
 Cheers,
 nick.
 
 -Ursprungliche Nachricht-
 Von: Eric Wulff [mailto:[EMAIL PROTECTED]
 Gesendet: Freitag, 5. November 2004 07:35
 An: Atishay Kumar
 Cc: Tomcat Users List
 Betreff: Re: {an alternative}Re: connection pooling
 
 
 Atishay, the DefaultContext does work once I comment out the other
 Engine element.  You mentioned that means something is wrong with my
 Context?  So what next?
 
 many thx
 Eric
 
 
 On Thu, 4 Nov 2004 22:21:57 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
  This did not work.  In looking for the Engine element you speak of I
  didn't find it exactly.  I did find it with it with an extra attribute
  Engine name=Standalone... jvmRoute=jvm1.  Furthermore, this
  element was nested within the Service element and there is another
  Engine name=Catalina... element.  I tried with and without the
  jvmRoute element.  No success.  Same exception.
 
  Eric
 
  On Fri, 5 Nov 2004 11:20:26 +0530, Atishay Kumar
 
 
  [EMAIL PROTECTED] wrote:
   If adding Resouce name .../ did not work..then try following
  
   On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
Hi all, I'm returning to a problem I couldn't solve the first time,
about two months ago, and still can't seem to figure out.  I
 can't get
a db connection using connection pools.  I get the exception listed
below, same as so many have previously, but nothing I've found seems
to works.  Below are my specs.  Anyone with concrete advise/direction
on how to get
this working?
   
Also, I noticed in many solutions the suggestion was made to edit the
myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
However, there is no myapp.xml in that directory on my server. Just 2
.xml's related to other applications and a manager.xml which I'm not
sure what it's related to.
   
OS: FC2
Tomcat 5.0.28
   
exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
JDBC driver class '' for connect URL 'null'
   
WEB-INF web xml: code inserted AFTER all servlet mappings...
   the following shld be  in
   web-app
resource-ref
   descriptionMy Datasource/description
res-ref-namejdbc/wms/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref
   /web-app !-- I am sure u have this right--
   
server xml(tried this with and without a Resource name)...
   The following shld be under
   Engine name=Standalone defaultHost=localhost debug=0
  
   REplace
Context path=/wms docBase=wms debug=0 reloadable=true
   with
   DefaultContext
   Resource name=jdbc/wms auth=Container
 type=javax.sql.DataSource

Re: connection pooling

Hi all, I'm returning to a problem I couldn't solve the first time,
about two months ago, and still can't seem to figure out.  I can't get
a db connection using connection pools.  I get the exception listed
below, same as so many have previously, but nothing I've found seems
to works.  Below are my specs.  Anyone with concrete advise/direction
on how to get
this working?

Also, I noticed in many solutions the suggestion was made to edit the
myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/. 
However, there is no myapp.xml in that directory on my server. Just 2
.xml's related to other applications and a manager.xml which I'm not
sure what it's related to.

OS: FC2
Tomcat 5.0.28

exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
JDBC driver class '' for connect URL 'null'

WEB-INF web xml: code inserted AFTER all servlet mappings...
resource-ref
res-ref-namejdbc/wms/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
/resource-ref

server xml(tried this with and without a Resource name)...
Context path=/wms docBase=wms debug=0 reloadable=true
ResourceParams name=jdbc/wms
  parameter
nameusername/name
valuewhatever/value
  /parameter
  parameter
namepassword/name
valuewhatever/value
  /parameter
  parameter
namedriverClassName/name
valuecom.informix.jdbc.IfxDriver/value
  /parameter
  parameter
nameurl/name

valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
/parameter
/ResourceParams
  /Context

I have the following jars in my CATALINA_HONE/common/lib and I also
tried putting the db driver and commons-collections, dbcp, and pool in
my WEB-INF/lib with no success.  They are all mode 644.

ant.jar
ant-launcher.jar
commons-collections-3.1.jar
commons-dbcp-1.2.1.jar
commons-el.jar
commons-pool-1.2.jar
ifxjdbc.jar (the necessary informix driver)
jar.txt
jasper-compiler.jar
jasper-runtime.jar
jsp-api.jar
mysql-connector-java-3.0.15-ga-bin.jar
naming-common.jar
naming-factory.jar
naming-java.jar
naming-resources.jar
servlet-api.jar



On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
[EMAIL PROTECTED] wrote:
 hi,
  i am not sure but you may try downloading latest jar files for
 following froom tomcat site and try them out. copy the old jar files
 somewhere else and try using the latest jar files.
 1) Commons Collections
 2)Commons DBCP
 3)Commons Pool
 
 
 
 
 On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
  Except that the driver works for connecting if I'm not utilizing a
  connection pool, i.e., I am able to connect to the db and manipulate
  data via DriverManager.getConnection(url, db, pwd).
 
  The driver is located in CATALINA_HOME/commons/lib
 
  Eric
 
  On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
  [EMAIL PROTECTED] wrote:
   No, you don't need that many params. I think your problem might be the
 
 
   driver. Where did you drop off your informix jdbc jar?
  
  
   -Original Message-
   From: Eric Wulff [mailto:[EMAIL PROTECTED]
   Sent: October 7, 2004 5:56 PM
   To: Tomcat Users List
   Subject: Re: connection pooling
  
   Yes, I have added Resource name=... .  Now different errors are reported
   via stack trace as I posted in response to Atishay's suggestion that I add
   this.  I'll try adding your suggestions and see what happens.  Also, you
   suggest adding many parameters.  Are they necessary for simply making a
   connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left all
   your suggestions out.
   Including the Resource tag, but that seems critical for connection.
  
   Eric
  
   On Thu, 7 Oct 2004 17:14:27 -0400, Phillip Qin [EMAIL PROTECTED]
   wrote:
1. web.xml: OK
   
2. context.xml on context of server.xml:
   
Resource name=jdbc/test_connect auth=Container
type=javax.sql.DataSource/ = have you added this?
ResourceParams name=jdbc/test_connect
parameter
namedriverClassName/name
valueyour.jdbc.driver/value
/parameter
parameter
nameurl/name
valueyour.jdbc.url/value
/parameter
parameter
nameusername/name
valueyouruser/value
/parameter
parameter
namepassword/name
valueyourpass/value
/parameter
parameter
namemaxActive/name
value20/value
/parameter
parameter
namemaxIdle/name
value10/value
/parameter
parameter
nameminIdle/name
value10/value
/parameter
parameter

Re: connection pooling

2004-11-04 Thread Atishay Kumar

Pls do the following change after context.. and u are on!!
cheers
On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
 Hi all, I'm returning to a problem I couldn't solve the first time,
 about two months ago, and still can't seem to figure out.  I can't get
 a db connection using connection pools.  I get the exception listed
 below, same as so many have previously, but nothing I've found seems
 to works.  Below are my specs.  Anyone with concrete advise/direction
 on how to get
 this working?
 
 Also, I noticed in many solutions the suggestion was made to edit the
 myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
 However, there is no myapp.xml in that directory on my server. Just 2
 .xml's related to other applications and a manager.xml which I'm not
 sure what it's related to.
 
 OS: FC2
 Tomcat 5.0.28
 
 exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
 JDBC driver class '' for connect URL 'null'
 
 WEB-INF web xml: code inserted AFTER all servlet mappings...
 resource-ref
 res-ref-namejdbc/wms/res-ref-name
 res-typejavax.sql.DataSource/res-type
 res-authContainer/res-auth
 /resource-ref
 
 server xml(tried this with and without a Resource name)...
 Context path=/wms docBase=wms debug=0 reloadable=true

Resource name=jdbc/wms auth=Container type=javax.sql.DataSource/

 ResourceParams name=jdbc/wms
   parameter
 nameusername/name
 valuewhatever/value
   /parameter
   parameter
 namepassword/name
 valuewhatever/value
   /parameter
   parameter
 namedriverClassName/name
 valuecom.informix.jdbc.IfxDriver/value
   /parameter
   parameter
 nameurl/name
 
 valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
 /parameter
 /ResourceParams
   /Context
 
 I have the following jars in my CATALINA_HONE/common/lib and I also
 tried putting the db driver and commons-collections, dbcp, and pool in
 my WEB-INF/lib with no success.  They are all mode 644.
 
 ant.jar
 ant-launcher.jar
 commons-collections-3.1.jar
 commons-dbcp-1.2.1.jar
 commons-el.jar
 commons-pool-1.2.jar
 ifxjdbc.jar (the necessary informix driver)
 jar.txt
 jasper-compiler.jar
 jasper-runtime.jar
 jsp-api.jar
 mysql-connector-java-3.0.15-ga-bin.jar
 naming-common.jar
 naming-factory.jar
 naming-java.jar
 naming-resources.jar
 servlet-api.jar
 
 On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
 [EMAIL PROTECTED] wrote:
  hi,
   i am not sure but you may try downloading latest jar files for
  following froom tomcat site and try them out. copy the old jar files
  somewhere else and try using the latest jar files.
  1) Commons Collections
  2)Commons DBCP
  3)Commons Pool
 
 
 
 
  On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
   Except that the driver works for connecting if I'm not utilizing a
   connection pool, i.e., I am able to connect to the db and manipulate
   data via DriverManager.getConnection(url, db, pwd).
  
   The driver is located in CATALINA_HOME/commons/lib
  
   Eric
  
   On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
   [EMAIL PROTECTED] wrote:
No, you don't need that many params. I think your problem might be the
  
  
driver. Where did you drop off your informix jdbc jar?
   
   
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: October 7, 2004 5:56 PM
To: Tomcat Users List
Subject: Re: connection pooling
   
Yes, I have added Resource name=... .  Now different errors are reported
via stack trace as I posted in response to Atishay's suggestion that I add
this.  I'll try adding your suggestions and see what happens.  Also, you
suggest adding many parameters.  Are they necessary for simply making a
connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left all
your suggestions out.
Including the Resource tag, but that seems critical for connection.
   
Eric
   
On Thu, 7 Oct 2004 17:14:27 -0400, Phillip Qin [EMAIL PROTECTED]
wrote:
 1. web.xml: OK

 2. context.xml on context of server.xml:

 Resource name=jdbc/test_connect auth=Container
 type=javax.sql.DataSource/ = have you added this?
 ResourceParams name=jdbc/test_connect
 parameter
 namedriverClassName/name
 valueyour.jdbc.driver/value
 /parameter
 parameter
 nameurl/name
 valueyour.jdbc.url/value
 /parameter
 parameter
 nameusername/name
 valueyouruser/value
 /parameter
 parameter
 namepassword/name
 valueyourpass/value
 /parameter
 parameter

{an alternative}Re: connection pooling

2004-11-04 Thread Atishay Kumar

If adding Resouce name .../ did not work..then try following

On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
 Hi all, I'm returning to a problem I couldn't solve the first time,
 about two months ago, and still can't seem to figure out.  I can't get
 a db connection using connection pools.  I get the exception listed
 below, same as so many have previously, but nothing I've found seems
 to works.  Below are my specs.  Anyone with concrete advise/direction
 on how to get
 this working?
 
 Also, I noticed in many solutions the suggestion was made to edit the
 myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
 However, there is no myapp.xml in that directory on my server. Just 2
 .xml's related to other applications and a manager.xml which I'm not
 sure what it's related to.
 
 OS: FC2
 Tomcat 5.0.28
 
 exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
 JDBC driver class '' for connect URL 'null'
 
 WEB-INF web xml: code inserted AFTER all servlet mappings...
the following shld be  in 
web-app
 resource-ref
descriptionMy Datasource/description
 res-ref-namejdbc/wms/res-ref-name
 res-typejavax.sql.DataSource/res-type
 res-authContainer/res-auth
 /resource-ref
/web-app !-- I am sure u have this right--
 
 server xml(tried this with and without a Resource name)...
The following shld be under 
Engine name=Standalone defaultHost=localhost debug=0

REplace
 Context path=/wms docBase=wms debug=0 reloadable=true
with
DefaultContext
Resource name=jdbc/wms auth=Container type=javax.sql.DataSource/
 ResourceParams name=jdbc/wms
   parameter
 nameusername/name
 valuewhatever/value
   /parameter
   parameter
 namepassword/name
 valuewhatever/value
   /parameter
   parameter
 namedriverClassName/name
 valuecom.informix.jdbc.IfxDriver/value
   /parameter
   parameter
 nameurl/name
 
 valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
 /parameter
 /ResourceParams
replace
   /Context
with
/DefaultContext
!--
If this works them there is something wrong with your context. we
shall figure that out later but first DefaultContext should work!!
restart tommy after making changes.
hope it works!!
--
 
 I have the following jars in my CATALINA_HONE/common/lib and I also
 tried putting the db driver and commons-collections, dbcp, and pool in
 my WEB-INF/lib with no success.  They are all mode 644.
 
 ant.jar
 ant-launcher.jar
 commons-collections-3.1.jar
 commons-dbcp-1.2.1.jar
 commons-el.jar
 commons-pool-1.2.jar
 ifxjdbc.jar (the necessary informix driver)
 jar.txt
 jasper-compiler.jar
 jasper-runtime.jar
 jsp-api.jar
 mysql-connector-java-3.0.15-ga-bin.jar
 naming-common.jar
 naming-factory.jar
 naming-java.jar
 naming-resources.jar
 servlet-api.jar
 
 On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
 [EMAIL PROTECTED] wrote:
  hi,
   i am not sure but you may try downloading latest jar files for
  following froom tomcat site and try them out. copy the old jar files
  somewhere else and try using the latest jar files.
  1) Commons Collections
  2)Commons DBCP
  3)Commons Pool
 
 
 
 
  On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
   Except that the driver works for connecting if I'm not utilizing a
   connection pool, i.e., I am able to connect to the db and manipulate
   data via DriverManager.getConnection(url, db, pwd).
  
   The driver is located in CATALINA_HOME/commons/lib
  
   Eric
  
   On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
   [EMAIL PROTECTED] wrote:
No, you don't need that many params. I think your problem might be the
  
  
driver. Where did you drop off your informix jdbc jar?
   
   
-Original Message-
From: Eric Wulff [mailto:[EMAIL PROTECTED]
Sent: October 7, 2004 5:56 PM
To: Tomcat Users List
Subject: Re: connection pooling
   
Yes, I have added Resource name=... .  Now different errors are reported
via stack trace as I posted in response to Atishay's suggestion that I add
this.  I'll try adding your suggestions and see what happens.  Also, you
suggest adding many parameters.  Are they necessary for simply making a
connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left all



-- 
:)
Atishay Kumar
Btech, SEM VII
DA-IICT
Gandhinagar - 382009
India
ph: +91 9825383948
/
 * Learn the rules as you would need them to break them properly *
 /

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: connection pooling

Thx for your input but, as mentioned in my previous message, I've
tried this and it does not work.  Also, considering my web.xml I
shouldn't need this, correct?  I have a resource-ref in my web.xml.

Eric


On Fri, 5 Nov 2004 11:01:05 +0530, Atishay Kumar
[EMAIL PROTECTED] wrote:
 
 Pls do the following change after context.. and u are on!!
 cheers
 
 
 On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
  Hi all, I'm returning to a problem I couldn't solve the first time,
  about two months ago, and still can't seem to figure out.  I can't get
  a db connection using connection pools.  I get the exception listed
  below, same as so many have previously, but nothing I've found seems
  to works.  Below are my specs.  Anyone with concrete advise/direction
  on how to get
  this working?
 
  Also, I noticed in many solutions the suggestion was made to edit the
  myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
  However, there is no myapp.xml in that directory on my server. Just 2
  .xml's related to other applications and a manager.xml which I'm not
  sure what it's related to.
 
  OS: FC2
  Tomcat 5.0.28
 
  exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
  JDBC driver class '' for connect URL 'null'
 
  WEB-INF web xml: code inserted AFTER all servlet mappings...
  resource-ref
  res-ref-namejdbc/wms/res-ref-name
  res-typejavax.sql.DataSource/res-type
  res-authContainer/res-auth
  /resource-ref
 
  server xml(tried this with and without a Resource name)...
  Context path=/wms docBase=wms debug=0 reloadable=true
 
 Resource name=jdbc/wms auth=Container type=javax.sql.DataSource/
 
 
 
  ResourceParams name=jdbc/wms
parameter
  nameusername/name
  valuewhatever/value
/parameter
parameter
  namepassword/name
  valuewhatever/value
/parameter
parameter
  namedriverClassName/name
  valuecom.informix.jdbc.IfxDriver/value
/parameter
parameter
  nameurl/name
  
  valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
  /parameter
  /ResourceParams
/Context
 
  I have the following jars in my CATALINA_HONE/common/lib and I also
  tried putting the db driver and commons-collections, dbcp, and pool in
  my WEB-INF/lib with no success.  They are all mode 644.
 
  ant.jar
  ant-launcher.jar
  commons-collections-3.1.jar
  commons-dbcp-1.2.1.jar
  commons-el.jar
  commons-pool-1.2.jar
  ifxjdbc.jar (the necessary informix driver)
  jar.txt
  jasper-compiler.jar
  jasper-runtime.jar
  jsp-api.jar
  mysql-connector-java-3.0.15-ga-bin.jar
  naming-common.jar
  naming-factory.jar
  naming-java.jar
  naming-resources.jar
  servlet-api.jar
 
  On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
  [EMAIL PROTECTED] wrote:
   hi,
i am not sure but you may try downloading latest jar files for
   following froom tomcat site and try them out. copy the old jar files
   somewhere else and try using the latest jar files.
   1) Commons Collections
   2)Commons DBCP
   3)Commons Pool
  
  
  
  
   On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
Except that the driver works for connecting if I'm not utilizing a
connection pool, i.e., I am able to connect to the db and manipulate
data via DriverManager.getConnection(url, db, pwd).
   
The driver is located in CATALINA_HOME/commons/lib
   
Eric
   
On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
[EMAIL PROTECTED] wrote:
 No, you don't need that many params. I think your problem might be the
   
   
 driver. Where did you drop off your informix jdbc jar?


 -Original Message-
 From: Eric Wulff [mailto:[EMAIL PROTECTED]
 Sent: October 7, 2004 5:56 PM
 To: Tomcat Users List
 Subject: Re: connection pooling

 Yes, I have added Resource name=... .  Now different errors are reported
 via stack trace as I posted in response to Atishay's suggestion that I add
 this.  I'll try adding your suggestions and see what happens.  Also, you
 suggest adding many parameters.  Are they necessary for simply making a
 connection?  If so, the tutorial I'm following, 'Tomcat Kick Start' left all
 your suggestions out.
 Including the Resource tag, but that seems critical for connection.

 Eric

 On Thu, 7 Oct 2004 17:14:27 -0400, Phillip Qin [EMAIL PROTECTED]
 wrote:
  1. web.xml: OK
 
  2. context.xml on context of server.xml:
 
  Resource name=jdbc/test_connect auth=Container
  type=javax.sql.DataSource/ = have you added this?
  ResourceParams name=jdbc/test_connect
  parameter
  namedriverClassName/name
  valueyour.jdbc.driver/value
  /parameter

Re: {an alternative}Re: connection pooling

This did not work.  In looking for the Engine element you speak of I
didn't find it exactly.  I did find it with it with an extra attribute
Engine name=Standalone... jvmRoute=jvm1.  Furthermore, this
element was nested within the Service element and there is another
Engine name=Catalina... element.  I tried with and without the
jvmRoute element.  No success.  Same exception.

Eric


On Fri, 5 Nov 2004 11:20:26 +0530, Atishay Kumar
[EMAIL PROTECTED] wrote:
 If adding Resouce name .../ did not work..then try following
 
 On Thu, 4 Nov 2004 19:46:30 -0800, Eric Wulff [EMAIL PROTECTED] wrote:
  Hi all, I'm returning to a problem I couldn't solve the first time,
  about two months ago, and still can't seem to figure out.  I can't get
  a db connection using connection pools.  I get the exception listed
  below, same as so many have previously, but nothing I've found seems
  to works.  Below are my specs.  Anyone with concrete advise/direction
  on how to get
  this working?
 
  Also, I noticed in many solutions the suggestion was made to edit the
  myapp.xml file located at CATALINA_HOME/conf/Catalina/localhost/.
  However, there is no myapp.xml in that directory on my server. Just 2
  .xml's related to other applications and a manager.xml which I'm not
  sure what it's related to.
 
  OS: FC2
  Tomcat 5.0.28
 
  exception: org.apache.commons.dbcp.SWLNestedException: Cannot create
  JDBC driver class '' for connect URL 'null'
 
  WEB-INF web xml: code inserted AFTER all servlet mappings...
 the following shld be  in
 web-app
  resource-ref
 descriptionMy Datasource/description
  res-ref-namejdbc/wms/res-ref-name
  res-typejavax.sql.DataSource/res-type
  res-authContainer/res-auth
  /resource-ref
 /web-app !-- I am sure u have this right--
 
  server xml(tried this with and without a Resource name)...
 The following shld be under
 Engine name=Standalone defaultHost=localhost debug=0
 
 REplace
  Context path=/wms docBase=wms debug=0 reloadable=true
 with
 DefaultContext
 Resource name=jdbc/wms auth=Container type=javax.sql.DataSource/
  ResourceParams name=jdbc/wms
parameter
  nameusername/name
  valuewhatever/value
/parameter
parameter
  namepassword/name
  valuewhatever/value
/parameter
parameter
  namedriverClassName/name
  valuecom.informix.jdbc.IfxDriver/value
/parameter
parameter
  nameurl/name
  
  valuejdbc:informix-sqli://foo.bar.com:somePort/dbName:INFORMIXSERVER=serverName/value
  /parameter
  /ResourceParams
 replace
/Context
 with
 /DefaultContext
 !--
 If this works them there is something wrong with your context. we
 shall figure that out later but first DefaultContext should work!!
 restart tommy after making changes.
 hope it works!!
 --
 
  I have the following jars in my CATALINA_HONE/common/lib and I also
  tried putting the db driver and commons-collections, dbcp, and pool in
  my WEB-INF/lib with no success.  They are all mode 644.
 
  ant.jar
  ant-launcher.jar
  commons-collections-3.1.jar
  commons-dbcp-1.2.1.jar
  commons-el.jar
  commons-pool-1.2.jar
  ifxjdbc.jar (the necessary informix driver)
  jar.txt
  jasper-compiler.jar
  jasper-runtime.jar
  jsp-api.jar
  mysql-connector-java-3.0.15-ga-bin.jar
  naming-common.jar
  naming-factory.jar
  naming-java.jar
  naming-resources.jar
  servlet-api.jar
 
  On Fri, 8 Oct 2004 11:45:59 +0530, Atishay Kumar
  [EMAIL PROTECTED] wrote:
   hi,
i am not sure but you may try downloading latest jar files for
   following froom tomcat site and try them out. copy the old jar files
   somewhere else and try using the latest jar files.
   1) Commons Collections
   2)Commons DBCP
   3)Commons Pool
  
  
  
  
   On Thu, 7 Oct 2004 15:29:40 -0700, Eric Wulff [EMAIL PROTECTED] wrote:
Except that the driver works for connecting if I'm not utilizing a
connection pool, i.e., I am able to connect to the db and manipulate
data via DriverManager.getConnection(url, db, pwd).
   
The driver is located in CATALINA_HOME/commons/lib
   
Eric
   
On Thu, 7 Oct 2004 18:22:45 -0400, Phillip Qin
[EMAIL PROTECTED] wrote:
 No, you don't need that many params. I think your problem might be the
   
   
 driver. Where did you drop off your informix jdbc jar?


 -Original Message-
 From: Eric Wulff [mailto:[EMAIL PROTECTED]
 Sent: October 7, 2004 5:56 PM
 To: Tomcat Users List
 Subject: Re: connection pooling

 Yes, I have added Resource name=... .  Now different errors are reported
 via stack trace as I posted in response to Atishay's suggestion that I add
 this.  I'll try adding your suggestions and see what happens.  Also, you
 suggest adding many parameters.  Are they necessary for simply making a
 connection?  If so, the tutorial I'm following, 'Tomcat

Re: {an alternative}Re: connection pooling