[
https://issues.apache.org/jira/browse/DERBY-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903077#comment-13903077
]
Knut Anders Hatlen commented on DERBY-6175:
-------------------------------------------
Hi Marco,
I think it's more likely that you're seeing DERBY-4160. The "No current
connection" exception is probably just a consequence of the connection getting
closed by the first exception. Unfortunately, none of the developers have been
able to reproduce the problem yet. If you have a test case that reliably
reproduces this bug, it would be great if you could post that on DERBY-4160.
Thanks.
> testComparisonAcrossPages failure -
> java.sql.SQLNonTransientConnectionException: No current connection.
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6175
> URL: https://issues.apache.org/jira/browse/DERBY-6175
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.1.4
> Reporter: Mamta A. Satoor
>
> Failure on 10.10.1.2(1466316) windows machine with IBM 1.7
> http://people.apache.org/~myrnavl/derby_test_results/v10_10/windows/testlog/ibm17/1466316-suites.All_diff.txt
> 1)
> testComparisonAcrossPages(org.apache.derbyTesting.functionTests.tests.lang.NullableUniqueConstraintTest)java.sql.SQLNonTransientConnectionException:
> No current connection.
> at
> org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.client.am.SqlException.getSQLException(Unknown
> Source)
> at org.apache.derby.client.am.PreparedStatement.setString(Unknown
> Source)
> at
> org.apache.derbyTesting.functionTests.tests.lang.NullableUniqueConstraintTest.testComparisonAcrossPages(NullableUniqueConstraintTest.java:393)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
> at
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:442)
> at
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:459)
> 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.SqlException: No current connection.
> at org.apache.derby.client.am.Statement.checkForClosedStatement(Unknown
> Source)
> at
> org.apache.derby.client.am.PreparedStatement.getColumnMetaDataX(Unknown
> Source)
> ... 46 more
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)