[jboss-jira] [JBoss JIRA] (WFLY-343) lower messaging's min-large-message-size value in standalone-full.xml

[Jason Greene (JIRA)]

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

Jason Greene updated WFLY-343:
------------------------------

    Fix Version/s: 8.2.0.CR1
                       (was: 8.1.0.Final)


> lower messaging's min-large-message-size value in standalone-full.xml
> ---------------------------------------------------------------------
>
>                 Key: WFLY-343
>                 URL: https://issues.jboss.org/browse/WFLY-343
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>             Fix For: 8.2.0.CR1
>
>
> AS7's messaging subsystem defines 2 attributes:
> journal-file-size => 10MiB
> min-large-message-size => 100KiB
> However, for startup performance issue, the standalone-full.xml sets the journal-file-size at 1OOKiB. This leads to issues since it's the same value than the min-large-message-size.
> If we want to keep a low journal-file-size value in standalone-full.xml, the min-large-message-size must also bet set appropriately (eg 75KiB?)
> For production use, however, we should suggest to the users to remove the journal-file-size and min-large-message-size from standalone-full.xml to use the default values (resp. 10MiB & 100KiB)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)