db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1219) jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with client
Date Mon, 15 May 2006 20:19:06 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1219?page=comments#action_12402409 ] 

Kathey Marsden commented on DERBY-1219:
---------------------------------------

Deepa said ...
>(The shutdown)  is the code which causes the intermediate hang and it seems this code
is not required >to check the scenarios meant to be covered by the test.  

I agree that the conditional  is a good solution for getting the test running with client,
but would like to clarify that I think the shutdown is a valuable part of the test because
we verify that the global transaction state is valid even aver the database has been shutdown
and restarted.  Once the hang has been resolved it would be good to reenable this part of
the test for client.






> jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with
client
> -----------------------------------------------------------------------------------------------
>
>          Key: DERBY-1219
>          URL: http://issues.apache.org/jira/browse/DERBY-1219
>      Project: Derby
>         Type: Test

>   Components: Network Server, Network Client
>     Versions: 10.2.0.0
>  Environment: More often on jdk 1.5 or jdk 1.6 but hangs on jdk 1.4.2 as well
>     Reporter: Kathey Marsden
>     Priority: Minor
>  Attachments: client_stack_trace_050306.txt, drda_traces_050206.zip, interrupt.diff,
no-sessions-for-closed-threads.diff, server_stack_trace_050306.txt, skipThreads.diff, testfiles_afterhang.zip,
traces_on_hang.txt
>
> The tests checkDataSource.java and checkDataSource30.java 
> hang intermittently especially with jdk 1.5.
> Attached is the test run output and traces when the server is started separately.
> 1) Enable checkDataSource30.java by taking it out of functionTests/suites/DerbyNetClient.exclude.
> 2) Run the test with client.
> java -Dij.exceptionTrace=true -Dkeepfiles=true -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest
jdbcapi/checkDataSource30.java
> Attachements:
>  testfiles_after_hang.zip - Test directory.
>  traces_on_hang.txt  - Server side traces obtained by starting the server separately
before running the test.
> I wish I had time to work on this right now as I would really like to see this valuable
test in the suite, but hopefully someone else will pick it up.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message