You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2010/01/11 18:01:03 UTC
[jira] Resolved: (DERBY-4038) On Z/OS store/access.sql fails with
encryptionAES and encryptionDES
[ https://issues.apache.org/jira/browse/DERBY-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-4038.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.0.0
Issue & fix info: (was: [Patch Available])
commited the latest patch with revision 897938.
In the past, some of the steps in the access.sql test caused instability (i.e. intermittent errors), specifically in the area of the spacetable checks. The offending checks were removed (see revision 393896), but it's possible that the converted test has some of this. I think those should be handled in separate JIRA issues; the main problem of this issue has been corrected.
(I did run suites.All without errors on zseries with patched jars).
> On Z/OS store/access.sql fails with encryptionAES and encryptionDES
> -------------------------------------------------------------------
>
> Key: DERBY-4038
> URL: https://issues.apache.org/jira/browse/DERBY-4038
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.3.3.0
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz6460sr3-20081108_01(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390x-64 jvmmz6460-20081107_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_BHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> $ pwd
> Reporter: Kathey Marsden
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: access.diff, access.out, DERBY-4038.diff_1, DERBY-4038.diff_2, DERBY-4038.diff_3, DERBY-4038.diff_4, DERBY-4038.stat_4, runaccess.out
>
>
> On Z/OS access.sql fails for encryptionAES and encryptionDES. The diff is big but I can't quite make out what the problem is. Maybe just a change of query plans.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.