Usually you should return every connection to your Persistence
mechanism, you cannot close the connection, because if do that other process
won´t use it.
> --
> De: Jose Euclides da Silva Junior -
> DATAPREVRJ[SMTP:[EMAIL PROTECTED]
> Responder:Tomcat Users List
> Enviada:
You should close your pool connection because the pool doesn't close the
real connection.
this doc can help you :
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-examples-how
to.html#Random%20Connection%20Closed%20Exceptions
Arnaud
> -Message d'origine-
> De : Jose Euclide
Hi Jose,
the connection that you are served by your data source is a connection
wrapper where the close method will not really close the connection,
rather it will tell the connection pool that this connection is free and
can be put back in the pool.
HTH
Adam
PS I wouldn't flag your email as "u
DBCP wraps the connection object. When you call conn.close(); on the connection object
given to you by the DataSource.getConnection(); method, it just releases it back into
the pool, it dosen't actually close the connection.
-- Nathan Christiansen
Tahitian Noni International
http://www.tah
AM
To: [EMAIL PROTECTED]
Subject: Re: urgent help please
first thing is to check the log files , if it has something like:
loaded context /abcd
or not.if this context is loaded as per the log files then check the docBase
attribute of your context , whether it is pointing to correct phy
first thing is to check the log files , if it has something like:
loaded context /abcd
or not.if this context is loaded as per the log files then check the docBase
attribute of your context , whether it is pointing to correct physical directory
or not. and check for possible case-mismatch also.
P
