Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1717116640.1244819647495.JavaMail.jira@brutus>
Date: Fri, 12 Jun 2009 08:14:07 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4180) SQLTransactionRollbackException in
 XATransactionTest when testing client/server compatibility
In-Reply-To: <1802014122.1240428407422.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden commented on DERBY-4180:
---------------------------------------

Sorry, I just noticed  testAllJDBCObjects at the bottom.  I think the real problem comes with 
testConnectionIsValid used 125 ms java.lang.Exception: DRDA_InvalidReplyTooShort
.S:Invalid reply from network server: Insufficient data and then testAllJDBCObjects cannot start the server.

So probably if you wanted to reproduce the circumstances you would need to run  a small suite with both ConnectionMethodsTest  and VerifySignatures.

Unfortunately DERBY-4053 can really affect any network server test I think it is not usually the test that hangs, but rather the next one that tries to bring up and ping the server.
 

> SQLTransactionRollbackException in XATransactionTest when testing client/server compatibility
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4180
>                 URL: https://issues.apache.org/jira/browse/DERBY-4180
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.5.1.1
>         Environment: Windows Vista 64, AMD Phenom II 940, Sun JDK 1.6.0_10, JUnit 3.8.2
>            Reporter: Suran Jayathilaka
>         Attachments: hangInfo061109.txt, javacore.20090611.094630.6388.0001.txt
>
>
> When running suites.All on a 10.4 client to 10.5 server configuration, the failure was observed.
> 10.5 Jars - From the db-derby-10.5.1.1-bin.zip  (RC2 - sane)
> ==============================================
> derby.jar
> derbytools.jar
> derbyLocale*.jar
> derbyrun.jar
> derbynet.jar
> 10.4 jars - (Built from the 10.4 branch - sane)
> ===================================
> derbyTesting.jar 
> derbyClient.jar 
> Stack Trace
> =========
> 5) testXATransactionTimeout(org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest)java.sql.SQLTransactionRollbackException: A lock could not be obtained within the time requested
> 	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedResultSet.closeOnTransactionError(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source)
> 	at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source)
> 	at org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest.testXATransactionTimeout(XATransactionTest.java:234)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:102)
> 	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: java.sql.SQLException: A lock could not be obtained within the time requested
> 	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> 	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown Source)
> 	... 39 more
> Caused by: ERROR 40XL1: A lock could not be obtained within the time requested
> 	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
> 	at org.apache.derby.impl.services.locks.ConcurrentLockSet.lockObject(Unknown Source)
> 	at org.apache.derby.impl.services.locks.ConcurrentLockSet.zeroDurationLockObject(Unknown Source)
> 	at org.apache.derby.impl.services.locks.AbstractPool.zeroDurationlockObject(Unknown Source)
> 	at org.apache.derby.impl.services.locks.ConcurrentPool.zeroDurationlockObject(Unknown Source)
> 	at org.apache.derby.impl.store.raw.xact.RowLocking2nohold.lockRecordForRead(Unknown Source)
> 	at org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.lockPositionForRead(Unknown Source)
> 	at org.apache.derby.impl.store.access.conglomerate.GenericScanController.fetchRows(Unknown Source)
> 	at org.apache.derby.impl.store.access.heap.HeapScan.fetchNextGroup(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.reloadArray(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.getNextRowCore(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getRowFromResultSet(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.ScalarAggregateResultSet.getNextRowCore(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown Source)
> 	at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.getNextRow(Unknown Source)
> 	... 32 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.