[
https://issues.apache.org/jira/browse/DERBY-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6549:
--------------------------------------
Attachment: XAShortReproD6549.java
XALongReproD6549.java
Attaching a long and short version based on the XATest.testDerby966 method. The
long one - XALongReproD6549 - has many more statements and preparedstatements,
and fails correspondingly more often - for me, about 4 out of 10 times.
XAShortReproD6549 has only one set of statements, but fails only in about 4 out
of 100 runs.
> intermittent response from network server with XA global/local transactions
> left open is: The DDM object 0x2408 is not supported. The connection has
> been terminated.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6549
> URL: https://issues.apache.org/jira/browse/DERBY-6549
> Project: Derby
> Issue Type: Bug
> Environment: windows (7, 2008), IBM jvm 1.6 SR15, 1.7 SR6
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: XALongReproD6549.java, XAShortReproD6549.java
>
>
> This error occassionally showed up in the XATest.testDerby966 before a
> rollback() was placed before the close().
> For some reason, Derby client received an extra, empty, SQLCARD (Codepoint
> 2408).
> This never happened with the Oracle JVMs, but has been reproduced with ibm
> 1.6 and 1.7 JVMs. Thus, it might be a JVM issue.
> However, it is not a JVM issue, and does not appear to be a gc issue or
> memory issue.
> Also, the frequency of the occurrences is higher with trunk (10.11) than with
> 10.10 or 10.9, thus, it is still possible there is a Derby component.
> See for more info regarding the original test failure DERBY-6248.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
