db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-1848) jdbcapi/SetQueryTimeoutTest.java fails on IBM wctme 5.7
Date Fri, 23 May 2008 18:55:56 GMT

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

Mamta A. Satoor commented on DERBY-1848:
----------------------------------------

Actually, it is not totally stand-alone test case. It is relying on a method declared inside
SetQueryTimeoutTest.java for a user-defined function. So, in order to run the standalone JDBC
program(DERBY_1848_Repro.java ), you need to have SetQueryTimeoutTest in your classpath. I
will work on removing that dependency from the standalone java program.

> jdbcapi/SetQueryTimeoutTest.java fails on IBM  wctme 5.7
> --------------------------------------------------------
>
>                 Key: DERBY-1848
>                 URL: https://issues.apache.org/jira/browse/DERBY-1848
>             Project: Derby
>          Issue Type: Test
>          Components: Regression Test Failure
>    Affects Versions: 10.2.2.1, 10.3.1.4, 10.5.0.0
>         Environment: Windows
>            Reporter: Rajesh Kartha
>            Assignee: Mamta A. Satoor
>         Attachments: DERBY_1848_Repro.java
>
>
> The following is the diff:
> *** Start: SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:05
***
> 7 del
> < Statement 1 completed
> 8 del
> < Statement 2 completed
> 9 del
> < Statement 3 completed
> 10 del
> < Testing timeout with an execute operation
> 11 del
> < Statements that should time out timed out, and statements that should complete completed
> 12 del
> < Testing setting a negative timeout value
> 13 del
> < Negative timeout value caused exception, as expected
> 14 del
> < Execute returned a ResultSet
> 15 del
> < Testing that Statement remembers timeout.
> 16 del
> < Testing that PreparedStatement remembers timeout.
> 17 del
> < Testing that CallableStatement remembers timeout.
> 18 del
> < Testing timeout with executeUpdate call.
> 19 del
> < Test SetQueryTimeoutTest PASSED
> 19a7,11
> > Test SetQueryTimeoutTest FAILED
> > org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest$TestFailedException:
Unexpected exception in 1: java.sql.SQLException: The statement has been cancelled or timed
out.
> > ERROR XCL52: The statement has been cancelled or timed out.
> > java.sql.SQLException: Invalid transaction state.
> > java.sql.SQLException: Invalid transaction state.
> Test Failed.
> *** End:   SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:26
***

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


Mime
View raw message