[
https://issues.apache.org/jira/browse/DERBY-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717564#action_12717564
]
Mamta A. Satoor commented on DERBY-4180:
----------------------------------------
I downloaded the jar files for 10.5.1.1 and 10.4.2 release. I used following to
setup the environment before running the junit test
cd \mydocs\realdocs\bugs\Derby4180*
sh
export
CLASSPATH="C:\p4clients\main\tools\java\junit.jar;derby10.5.1.1\derbynet.jar;derby10.5.1.1\derbytools.jar;derby10.4.2\derbyclient.jar;derby10.4.2\derbyTesting.jar;c:\p4clients\main\ibm16\lib;$CLASSPATH"
export PATH="c:\p4clients\main\ibm16\bin;$PATH"
As indicated by the classpath above, the server jar files come from 10.5.1.1
(ie derbynet.jar and derbytools.jar)
The client jar files come from 10.4.2 (ie derbyclient.jar and derbyTesting.jar)
With the environment above, when I run the problem junit test
XATransactionTest, I do not see any failures.
java -Xmx1024m junit.swingui.TestRunner -noloading
org.apache.derbyTesting.functionTests.tests.jdbcapi.XATransactionTest
I downloaded the jar files from
http://db.apache.org/derby/releases/release-10.4.2.0.cgi and
http://db.apache.org/derby/releases/release-10.5.1.1.cgi
Is this an intermittent failure and I need to run it multiple times to run into
it? Or is there anything wrong with my setup?
I did notice that the jira says the problem was found when the entire junit
suite was run. I will fire suites.All to see if the problem manifests itself.
> 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
>
> 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.
