[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1137) Specifying Destination Paging Parameters in Megabytes

[Tim Fox (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Fox closed JBMESSAGING-1137.
--------------------------------

    Resolution: Done
      Assignee: Clebert Suconic  (was: Tim Fox)


> Specifying Destination Paging Parameters in Megabytes
> -----------------------------------------------------
>
>                 Key: JBMESSAGING-1137
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1137
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>          Components: Configuration and Management
>    Affects Versions: 1.4.0.SP1
>         Environment: JBoss-4.2.1-GA   -Xms1024m -Xmx1024m  ,  JBM-1.4.0-SP1,  Linux 2.6.22.1-41.fc7,i386
>            Reporter: Tyronne Wickramarathne
>            Assignee: Clebert Suconic
>            Priority: Minor
>             Fix For: 2.0.0 Beta
>
>
> a mechanism is required to configure the destination paging parameters, preferably in megabytes. IOW, the amount of memory to be used by the JBM for paging requires to be set in megabytes instead of specifying it by the number of messages. 
> at present, this is done via configuring the destination paging parameters by setting the number of messages for each destination (FullSize, PageSize, DownCacheSize) . but when you start receiving messages with varying sizes (1k, 10k 200k ), you can't have a control over the memory it requires to house those messages (message cache). with JBossMQ, you can configure the upper and lower limit values for the message cache. an approach is required to accommodate this feature in JBM.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira