Hello.
I think we may ignore error message in this case.
However, I feel worry about missing chance to see the problem that closure of
connection falls on shutting down database .....
Are there any other test for the situation that closure of connection falls on
shutting down database ?
Best regards.
/*
Tomohito Nakayama
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Naka
http://www5.ocn.ne.jp/~tomohito/TopPage.html
*/
----- Original Message -----
From: "David Van Couvering" <[EMAIL PROTECTED]>
To: "Derby Development" <[email protected]>
Sent: Tuesday, August 09, 2005 3:15 AM
Subject: Re: [jira] Commented: (DERBY-273) The
derbynet/dataSourcePermissions_net.java test fails intermittently
That's my humble opinion. I would prefer this to, say, adding a new
method to the Connection class to force a connection closed even if it's
in a connection pool.
David
Kathey Marsden wrote:
TomohitoNakayama wrote:
Hello.
I follows myself.
I thought connection pool worked behind DataSource interface.
Is it impossible ... ?
Well ... Expression (of English ) which can cause misunderstanding ....
I meant that I want to confirm that the DataSource object in the code
is a connection pool.
Thank you for explaining. I think I understand the problem now. You are
saying that internally the client is pooling the connection and reusing it,
even though this is just a regular DataSource and the caller has closed
the connection. Is that correct? I think you may be right. I agree
that the client shutting down the database is unusual.
So is the summary that we think the exception on rollback on the server
is ok in this case and we just don't want it to print in the test output?
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.1/64 - Release Date: 2005/08/04
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.338 / Virus Database: 267.10.5/67 - Release Date: 2005/08/09
