db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-6248) nightly regression test failure: testDerby966(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest)java.sql.SQLFeatureNotSupportedException: The DDM object 0x2408 is not supported. The connection has been terminated.
Date Fri, 27 Sep 2013 18:23:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780167#comment-13780167
] 

Kathey Marsden edited comment on DERBY-6248 at 9/27/13 6:22 PM:
----------------------------------------------------------------

I ran fifty times and did not see this failure on my Windows machine.

In the derby.log there are quite a few messages:

The XA transaction timed out and is going to be rolled back. The transaction Xid
 is (4660,7c00,6400).^M

but I don't see any exceptions in the log. 
>From the stack trace it would seem that we are trying to do an autocommit on connection
close and that autocommit fails. It could be that we are indeed getting that exception but
it is not getting logged.


I am guessing that if I put the rollback before the close() we might eliminate the intermittent
failure but that might be just masking a bug.
Things I don't understand ..
- What is the actual exception on commit? Are the transaction timeout's relevant or is something
else going on.
- Why does  SYNCCTL not handle the exception on commit properly and the give the DDM error?
- Why is the failure intermittent?  

Will attach the derby.log and error-stackttrace.out.




                
      was (Author: kmarsden):
    I ran fifty times and did not see this failure on my Windows machine.

In the derby.log there are quite a few messages:

The XA transaction timed out and is going to be rolled back. The transaction Xid
 is (4660,7c00,6400).^M

but I don't see any exceptions in the log. 
>From the stack trace it would seem that we are trying to do an autocommit on connection
close and that autocommit fails. It could be that we are indeed getting that exception but
it is not getting logged.


I am guessing that if I put the rollback before the close() we might eliminate the intermittent
failure but that might be just masking a bug.
Things I don't understand ..
- Why are we doing an autocommit on connection.close()?
- As we do commit, what is the actual exception on commit? Are the transaction timeout's relevant
or is something else going on.
- Why does  SYNCCTL not handle the exception on commit properly and the give the DDM error?
- Why is the failure intermittent?  

Will attach the derby.log and error-stackttrace.out.




                  
> nightly regression test failure: testDerby966(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest)java.sql.SQLFeatureNotSupportedException:
The DDM object 0x2408 is not supported.  The connection has been terminated.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6248
>                 URL: https://issues.apache.org/jira/browse/DERBY-6248
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.11.0.0
>            Reporter: Mike Matrigali
>         Attachments: derby.log, error-stacktrace.out
>
>
> intermittent nightly regression test failure in trunk, linux, ibm16
> only happened once in may on this machine environment.
> http://people.apache.org/~myrnavl/derby_test_results/main/linux/testlog/ibm16/1488444-suites.All_diff.txt
> There was 1 error:
> 1) testDerby966(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest)java.sql.SQLFeatureNotSupportedException:
The DDM object 0x2408 is not supported.  The connection has been terminated.
> 	at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
> 	at org.apache.derby.client.am.LogicalConnection.close(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATest.testDerby966(XATest.java:1079)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
> 	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:439)
> 	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:456)
> 	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)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	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)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	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)
> 	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)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Caused by: org.apache.derby.client.am.DisconnectException: The DDM object 0x2408 is not
supported.  The connection has been terminated.
> 	at org.apache.derby.client.net.NetConnectionReply.doObjnsprmSemantics(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseSYNCCTLError(Unknown Source)
> 	at org.apache.derby.client.net.NetXAConnectionReply.parseSYNCCTLreply(Unknown Source)
> 	at org.apache.derby.client.net.NetXAConnectionReply.readLocalXACommit(Unknown Source)
> 	at org.apache.derby.client.net.NetXAConnection.readLocalXACommit_(Unknown Source)
> 	at org.apache.derby.client.net.NetXAConnection.readCommit(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.readXACommit_(Unknown Source)
> 	at org.apache.derby.client.am.ClientConnection.readCommit(Unknown Source)
> 	at org.apache.derby.client.am.ClientConnection.readAutoCommit(Unknown Source)
> 	at org.apache.derby.client.am.ClientConnection.flowClose(Unknown Source)
> 	at org.apache.derby.client.am.ClientConnection.closeForReuse(Unknown Source)
> 	... 49 more
> FAILURES!!!
> Tests run: 17341,  Failures: 0,  Errors: 1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message