You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2011/06/22 10:00:49 UTC
[jira] [Created] (AMQ-3374) Long KahaDB transactions could lead to
OutOfMemory
Long KahaDB transactions could lead to OutOfMemory
--------------------------------------------------
Key: AMQ-3374
URL: https://issues.apache.org/jira/browse/AMQ-3374
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.5.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.6.0
Problem: all writes are kept in memory until the sync time, which for long transactions could be a problem.
Solution: define max transaction size and if threshold is reached keep the rest of the writes in a temp file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3374) Long KahaDB transactions could lead to
OutOfMemory
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-3374.
--------------------------------
Resolution: Fixed
This should now be fixed with svn revision 1138443
Default size of the transaction that will be kept in the memory is 10MB. This can be tuned with {{maxKahaDBTxSize}} system property (in bytes)
> Long KahaDB transactions could lead to OutOfMemory
> --------------------------------------------------
>
> Key: AMQ-3374
> URL: https://issues.apache.org/jira/browse/AMQ-3374
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> Problem: all writes are kept in memory until the sync time, which for long transactions could be a problem.
> Solution: define max transaction size and if threshold is reached keep the rest of the writes in a temp file
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3374) Long KahaDB transactions could lead
to OutOfMemory
Posted by "Dejan Bosanac (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176156#comment-13176156 ]
Dejan Bosanac commented on AMQ-3374:
------------------------------------
Additional fix in svn revision 1224890
Transaction size is actual number of pages we keep in memory.
> Long KahaDB transactions could lead to OutOfMemory
> --------------------------------------------------
>
> Key: AMQ-3374
> URL: https://issues.apache.org/jira/browse/AMQ-3374
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.6.0
>
>
> Problem: all writes are kept in memory until the sync time, which for long transactions could be a problem.
> Solution: define max transaction size and if threshold is reached keep the rest of the writes in a temp file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira