db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1143) derbynet/prepStmt.java fails with JCC2.6
Date Tue, 28 Mar 2006 20:46:50 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1143?page=all ]

Deepa Remesh updated DERBY-1143:
--------------------------------

    Attachment: derby-1143.diff

Attaching a patch 'derby-1143.diff' which reduces the number of batch elements in the test
derbynet/prepStmt.java so that it can run successfully with jcc2.6. 

I checked with the JCC folks who told me that JCC2.6 driver supports less than 32K batch elements.
When I ran the test, I found that maximum number supported is 32765. As mentioned by Bryan,
any number greater than 9000 will provoke the bug. So this number will still allow us to test
DERBY-428. 

With this patch, I have also run the test with client framework. This patch modifies only
one test file (derbynet/prepStmt.java). It would be good if someone can take a look at this
patch.

> derbynet/prepStmt.java fails with JCC2.6
> ----------------------------------------
>
>          Key: DERBY-1143
>          URL: http://issues.apache.org/jira/browse/DERBY-1143
>      Project: Derby
>         Type: Test
>   Components: Regression Test Failure
>     Versions: 10.2.0.0
>  Environment: JCC 2.6
>     Reporter: Deepa Remesh
>  Attachments: derby-1143.diff
>
> derbynet/prepStmt.java fails on Windows and Linux with Sun JDK 1.5 and JCC 2.6. 
> *** Start: prepStmt jdk1.5.0_02 DerbyNet derbynetmats:derbynetmats 2006-03-22 19:46:37
***
> 82 del
> < prepStmt Test Ends
> 82 add
> > com.ibm.db2.jcc.a.DisconnectException: More than 0x7FF chained requests not allowed.
 This error may be due to a batch that is greater than 32k.
> Test Failed.
> *** End:   prepStmt jdk1.5.0_02 DerbyNet derbynetmats:derbynetmats 2006-03-22 19:46:59
***
> The test passed for me with Sun JDK1.5, JCC 2.4 on Windows XP. The tinderbox runs do
not show this failure. It looks like this failure is occuring only with JCC2.6. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message