[ http://issues.apache.org/jira/browse/DERBY-1219?page=all ]
Deepa Remesh updated DERBY-1219:
--------------------------------
Attachment: drda_traces_050206.zip
Thanks Bryan. I am glad that you are looking at this issue. Hopefully we can
narrow this down quickly with your DRDA expertise. I am attaching the client
and server DRDA traces that I had captured previously when I ran the test
inside the harness. You may find some traces which start with "DERBY-1219"
which I had added for some debugging. Please ignore these. If needed, I can try
to capture fresh traces and upload them.
I had let the test run for a long time. At the end of the test I killed network
server and this accounts for the last DisconnectException seen in
client_trace.txt_sds_1. To me, it looked like the client was hanging after
sending EXCSAT and ACCSEC whereas network server was idle.
> 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,
> server_stack_trace_050306.txt, 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
