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] Commented: (DERBY-1219) jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with client
Date Mon, 15 May 2006 19:58:06 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1219?page=comments#action_12402400 ] 

Deepa Remesh commented on DERBY-1219:
-------------------------------------

The two categories of diffs seen  when running the checkDataSource test with client are: 

< DriverManager  <closedstmt>.execute() null - Invalid operation: statement closed
11a11
> DriverManager  <closedstmt>.execute() 08003 - No current connection

AND

< autocommitxastart expected 'ResultSet' already closed.
460a459
> autocommitxastart expected ResultSet not open.  Verify that autocommit is OFF.

These diffs are message changes done as part of DERBY-843/DERBY-842. However, in the case
of first diff, I see a difference in the behaviour of client and embedded driver.

In case of client driver, Statement.execute method first checks if the connection associated
with the statement is closed before it checks if the statement itself was closed or not. In
case of embedded driver, the check for statement closed is done before the check for connection
closed. I would like to clarify if the order of the checks matter and if it does which is
the correct behaviour.

> 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