[
https://issues.apache.org/jira/browse/DERBY-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali reassigned DERBY-4743:
-------------------------------------
Assignee: Mike Matrigali
> Attempt to access a DECLARE GLOBAL TEMPORARY TABLE after commit in an XA
> transaction in Network server fails.
> -------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4743
> URL: https://issues.apache.org/jira/browse/DERBY-4743
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0,
> 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
> Reporter: Mike Matrigali
> Assignee: Mike Matrigali
> Attachments: XATest.java
>
>
> Attempting to access a global temporary table after commit of an XA
> transaction in network server fails. Does anyone know if this is
> actually meant to work. After a commit of an XA transaction in network
> server do the connection keep the same transaction context for
> subsequent work? I will commit a change to the XATest.java junit test that
> shows this. Is it valid to attempt to use the connection after an
> XA end() and XA commit()?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
