Sorry Chris I meant to address Mark in my previous mail.
Thanks,
Mohammed.
-Original Message-
From: Mohammed Bin Mahmood [mailto:moham...@sustainlane.com]
Sent: Wednesday, August 26, 2009 9:32 AM
To: 'Tomcat Users List'
Subject: RE: Problem closing datasource when used as JND
users@tomcat.apache.org/msg65149.html
Mohammed Bin Mahmood wrote:
> Hi Chris,
>
> You mentioned about the published filter that can close datasource. I
wonder
> if you have any idea about that.
> Is it provided by tomcat or some other
>
> Thanks,
> Mohammed.
> -Original
, 2009 7:48 PM
To: Tomcat Users List
Subject: Re: Problem closing datasource when used as JNDI resource
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohammed,
On 8/24/2009 12:49 AM, Mohammed Bin Mahmood wrote:
> Hi Chris,
>
>> 3. There is a published filter that can close the DataSo
11:25 PM
To: Tomcat Users List
Subject: Re: Problem closing datasource when used as JNDI resource
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohammed,
On 8/20/2009 9:44 AM, Mohammed Bin Mahmood wrote:
> But I still do not get my answer yet.
Yes, you do:
1. This is a problem with Tomcat. P
, Mohammed Bin Mahmood wrote:
> When tomcat takes care of creating maintaining datasource, then does it
not
> closes it when server is shut down?
According to Filip's comments on the first thread you mentioned, yes:
the connection pool is not explicitly closed.
> Do we have to close it o
Correction: missing DON'T
I looked into the code and I can only see that it destroys the Resource and
other references. But DON'T destroy or closes the datasource on a whole.
Thanks,
Mohammed.
-Original Message-----
From: Mohammed Bin Mahmood [mailto:moham...@sustainlane.
} catch (SQLException e) {
//Logging code
}
}
}
public void setDsName(String dsName) {
this.dsName = dsName;
}
}
--
Thanks,
Mohammed B
