[DERBY-4743] Attempt to access a DECLARE GLOBAL TEMPORARY TABLE after commit in an XA transaction in Network server fails.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 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
• Fix Version/s: 10.7.1.1
• Component/s: JDBC
• Labels: derby_backport_reject_10_6
• Assignee: Mike Matrigali
• Reporter: Mike Matrigali
• Created: 14/Jul/10 02:45
• Updated: 17/Jun/13 09:19
• Resolved: 21/Jul/10 22:12

Description

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()?

Issue Links

• is blocked by: DERBY-4731 XA two phase commit with active GLOBAL TEMPORARY TABLE causes An internal error identified by RawStore module