db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6704) Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8
Date Fri, 15 Aug 2014 00:44:19 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dag H. Wanvik updated DERBY-6704:

    Attachment: derby-6704b.status

Uploading version b of this diagnostics patch. This version will also
try to get a jstack status of the hanging subprocess before killing it (only works on Unixen)
- hopefully this would work also on MacOs; it uses a little dirty reflection to access a private
PID field in the underlying Process class object befoer trying a jstack. For this to work,
the test must also run using a JDK, a JRE doesn't have a jstack. 

> Hang in AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest on Mac/jdk7,8
> -----------------------------------------------------------------------
>                 Key: DERBY-6704
>                 URL: https://issues.apache.org/jira/browse/DERBY-6704
>             Project: Derby
>          Issue Type: Bug
>            Reporter: Dag H. Wanvik
>         Attachments: derby-6704.diff, derby-6704b.diff, derby-6704b.status
> In our release tests for 10.11 we have seen this stack trace:
> {code}
>  org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.spawnProcess:JDBCDriversEmbeddedTest
2701.548 s
>  junit.framework.AssertionFailedError: Test process failed:Spawned org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCDriversEmbeddedTest
> ..
>  at org.apache.derbyTesting.functionTests.tests.jdbcapi.AutoloadTest.spawnProcess(AutoloadTest.java:256)
>  at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:118)
>  at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:440)
>  at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:457)
>  at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>  at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>  at junit.extensions.TestSetup.run(TestSetup.java:25)
> {code}
> presumably because the spawned process is killed by the test framework; it had been executing
for 2701 second, but we don't have much insight into what happened to the subprocess because
we don't collect its std our or std err.

This message was sent by Atlassian JIRA

View raw message