[
https://issues.apache.org/jira/browse/DERBY-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4039:
----------------------------------
Derby Info: (was: [Patch Available])
Oops Attached patch to the wrong issue.
> On Z/OS xa/xaOffline1.sql fails with a different global xid
> -----------------------------------------------------------
>
> Key: DERBY-4039
> URL: https://issues.apache.org/jira/browse/DERBY-4039
> Project: Derby
> Issue Type: Bug
> Components: Test
> Environment: 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
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: derby-576_diff.txt
>
>
> xaOffline fails with Z/OS with a diff in the global xid.
> *** Start: xaOffline1 jdk1.6.0 derbyall:xa 2009-01-23 15:33:00 ***
> 148 del
> < (1,776f6d626174,776f6d626174)
> |APP
>
> |UserTransaction |ACTIVE |select
> global_xid, username, type, status, cast(sql_text as varchar(512)) sql_text
> from tran_table where global_xid is not null&
> 148a148
> > (1,a696948281a3,a696948281a3)
> > |APP
> >
> > |UserTransaction |ACTIVE
> > |select global_xid, username, type, status, cast(sql_text as varchar(512))
> > sql_text from tran_table where global_xid is not null&
> Test Failed.
> I think this is not a bug at first glance but rather just a different
> expected output for this platform.
> I am not totally sure though. I don't know what determines the global xid
> value
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
