db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TomohitoNakayama" <tomon...@basil.ocn.ne.jp>
Subject Re: [jira] Commented: (DERBY-273) The derbynet/dataSourcePermissions_net.java test fails intermittently
Date Wed, 08 Jun 2005 10:02:14 GMT
Hello.

Thank you for your advise.

I have some unconfortable feeling around rollback ....

Kathey wrote:
> Database.close() should only throw an exception if the connection
> fails to close, not if the rollback fails.
Do you mean that fail of rollback is no problem, because undo will be done 
in recovery process.... ?

Well ... some more hacking in stacktrace would be needed for me.
I'm not yet sure the exact part in rollback where ShutdownException is 
happen.

Best regards.

/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- 
From: "Kathey Marsden" <kmarsdenderby@sbcglobal.net>
To: "Derby Development" <derby-dev@db.apache.org>
Sent: Wednesday, June 08, 2005 11:56 AM
Subject: Re: [jira] Commented: (DERBY-273) The 
derbynet/dataSourcePermissions_net.java test fails intermittently


> Tomohito Nakayama (JIRA) wrote:
>
>>I suspect there exists remaining previous thread concerning with that 
>>database , when
>>
> Yes, probably one connection shutdown the database intentionally , and
> then another had trouble doing  a rollback in Database.close(), that
> exception is  to be expected but we need to make sure the connection
> closes properly.
>
>>shutting down the database...
>>Then ShutdownException is thrown from previous working thread , I wonder.
>>
>>
>>
> More details
>
> SYMPTOM
>    - The  test shuts down the database intentionally with shudown=true.
>    - When a database has been  shutdown and connections terminate,  an
> exception may occur in Database.close() on rollback.         It depends
> on timing and  is not a problem. The trouble  is that if that an error
> occurs on rollback we never close
>        the connection and clean up properly.
>    - Network Server prints exceptions that occur when closing the
> connection  to the console, because failing to
>       close the connection  can cause a leak.
>    - Depending on timing you may or may not see the exception print to
> the console.
>
> POSSIBLE SOLUTION
>    Database.close() should only throw an exception if the connection
> fails to close, not if the rollback fails.
>     i.e. catch the rollback exception and proceed with conn.close()
>
> There is yet more detailed information in the Jira entry description of
> the problem.
>
> I hope this helps.
>
> Kathey
>
>
>>>The derbynet/dataSourcePermissions_net.java test fails intermittently
>>>---------------------------------------------------------------------
>>>
>>>         Key: DERBY-273
>>>         URL: http://issues.apache.org/jira/browse/DERBY-273
>>>     Project: Derby
>>>        Type: Bug
>>> Environment: 1.4.2 JVM (both Sun and IBM)
>>>    Reporter: Jack Klebanoff
>>>    Assignee: Tomohito Nakayama
>>>
>>>
>>
>>
>>
>>>The test fails in the derbyall/derbynetclientmats/derbynetmats suite 
>>>stack with the following diff:
>>>*** Start: dataSourcePermissions_net jdk1.4.2 DerbyNetClient 
>>>derbynetmats:derbynetmats 2005-05-11 04:24:11 ***
>>>17a18,19
>>>
>>>
>>>>org.apache.derby.iapi.services.context.ShutdownException:
>>>>agentThread[DRDAConnThread_2,5,derby.daemons]
>>>>
>>>>
>>>Test Failed.
>>>
>>>
>>
>>
>>
>
>
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 2005/06/07
>
> 



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 2005/06/07


Mime
View raw message