[ http://issues.apache.org/jira/browse/DERBY-1219?page=all ]
Bryan Pendleton resolved DERBY-1219:
------------------------------------
Fix Version: 10.2.0.0
Resolution: Fixed
I committed patch derby-1219-enable-tests.diff to subversion as revision 406776:
http://svn.apache.org/viewcvs?rev=406776&view=rev
It will be nice to have this test running regularly in the client framework.
> 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 Client, Network Server
> 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
> Assignee: Deepa Remesh
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: client_stack_trace_050306.txt, derby-1219-enable-tests.diff,
> derby-1219-enable-tests.status, 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
