[
https://issues.apache.org/jira/browse/DERBY-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5264:
-----------------------------------
Description:
See DERBY-4137 for details.
The fix has reduced the memory footprint, but in some rare (?) cases the bug
may still be observed. This is a function of transaction rate and timeout
value. Using a lower timeout value may help.
As opposed to Java SE 5.0 or higher, there is no similar workaround for J2SE
1.4.
was:
This issue simply documents that there are no plans to fix this issue on Java
1.4. The issue has been addressed on Java 5.0 and newer.
See DERBY-4137 for details.
Workaround: Switch from Java 1.4 to Java 5.0 or newer.
Issue & fix info: (was: [Workaround attached])
> OOM issue using XA with timeouts with Java 1.4
> ----------------------------------------------
>
> Key: DERBY-5264
> URL: https://issues.apache.org/jira/browse/DERBY-5264
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.5.3.0, 10.6.2.1, 10.7.1.1, 10.8.1.2, 10.9.0.0
> Reporter: Kristian Waagan
> Priority: Minor
>
> See DERBY-4137 for details.
> The fix has reduced the memory footprint, but in some rare (?) cases the bug
> may still be observed. This is a function of transaction rate and timeout
> value. Using a lower timeout value may help.
> As opposed to Java SE 5.0 or higher, there is no similar workaround for J2SE
> 1.4.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
