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 17:05:09 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1219?page=comments#action_12402353 ] 

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

Thanks Bryan for helping to identify the cause of the hang. 

Since we now know what is causing the intermittent hang, I think we can break the issue as
follows: 

1) Open a separate code bug against network server component to solve the real hang problem
and link to the details in this test issue.

2) Enable the test to run with client by removing the code which shutdowns the system when
we run the test using client framework. This 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 disabled the following shutdown code using a boolean and ran the checkDataSource tests
with the client and did not get the hang so far:

          // DERBY -???? - link to new bug opened for 1) above
          private static boolean hangAfterSystemShutdown = TestUtil.isDerbyNetClientFramework();
                        .
                        .
                        .
          // Shutdown the system only if we are not running in client framework
          if(! hangAfterSystemShutdown) {
			try {
				TestUtil.getConnection("","shutdown=true");
			} catch (SQLException sqle) {
				JDBCDisplayUtil.ShowSQLException(System.out, sqle);
			}
		}

The test has some existing diffs because of some intermediate check-ins which changed the
messages/behaviour. I will look at these diffs and submit a patch to enable the checkDataSource
tests to run with client. I think it would be good to get the test running with client so
that we can keep the masters up to date and also be able to catch any regressions in this
area.

Please provide any comments/feedback.

> 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