[
https://issues.apache.org/jira/browse/DERBY-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718296#action_12718296
]
Mamta A. Satoor commented on DERBY-4180:
----------------------------------------
I talked to Kathey about this jira entry and she mentioned that the behavior
was noticed with the client as the 10.4 latest codeline( I was trying to use
the jar files for 10.4.2 release). Also, she mentioned that the test XA40Test
hangs when the junit suite is run so it will be better to comment out that test
and then run the junit suite.
I have updated my 10.4 codeline with the latest changes and build the jar files
after commenting XA40Test. I am using derbyTesting.jar and derbyclient.jar from
the 10.4 codeline and I am continuing to use the 10.5 jars(for the server side)
from http://db.apache.org/derby/releases/release-10.5.1.1.cgi
With that configuration, when I run the junit suite using the gui interface as
shown below, I run into out of memory errors
java -Xmx1024m junit.swingui.TestRunner -noloading
org.apache.derbyTesting.functionTests.suites.All
I tried the text interface as show below but it seems to be hanging somewhere.
The problem with text interface is there is no clue which test might be hanging.
java -Xmx256M -XX:MaxPermSize=128M junit.textui.TestRunner
org.apache.derbyTesting.functionTests.suites.All
I will go ahead and kill that text run and try to run the junit suite again
with the text interface to see if I can reproduce the problem. I am using ibm16
on Windows XP box.
> 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.
