db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1219) jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with client
Date Wed, 03 May 2006 19:42:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1219?page=all ]

Deepa Remesh updated DERBY-1219:
--------------------------------

    Attachment: client_stack_trace_050306.txt
                server_stack_trace_050306.txt

I talked to Kathey about this issue on IRC and she suggested trying this test outside the
harness. I could repro it outside the harness too and I am attaching the stack traces from
the client and the server (client_stack_trace_050306.txt, server_stack_trace_050306.txt) .
From the trace and from the debugging I did with a few print statements, I think this is what
is happening in the test:

* For getting a new connection, client sends EXCSAT and ACCSEC to the server. Then, client
waits for the response from the server for these commands. In all the test runs, I found the
hang always happens in this request from the client sent as part of getConnection method.


* At the server, it tries to read the data from the client and does not get any data in DDMReader.fill.
So the server thinks the client has disconnected and ends the connection thread. 

* Client does not get back any response as server has ended the connection thread. Thus the
client is blocked trying to read the input stream.

I have not yet figured out the reason for this miscommunication between server and client.
I would appreciate if someone can also go through the traces and confirm my analysis is correct.

> 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, 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


Mime
View raw message