Bug 1011074
Summary: | Change value for address-full-policy from BLOCK to PAGE on the distributed configurations | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Miroslav Novak <mnovak> |
Component: | JMS | Assignee: | Clebert Suconic <csuconic> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Miroslav Novak <mnovak> |
Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | csuconic, dosoudil, jawilson, jdoyle, myarboro, pslavice, smumford |
Target Milestone: | ER4 | ||
Target Release: | EAP 6.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
In previous versions of JBoss EAP, the JMS configuration property address-full-policy was set to BLOCK in the product's configuration, meaning that once the maximum configured capacity for messages to a given address was reached, producers would be prevented from sending any further messages to that address.
This behaviour has been modified to conform more closely with customer expectations. The new default setting is PAGE, which pages messages recieved while the consumer is over the maximum capacity to disk. These messages will occupy disk space if they are not consumed.
This behaviour can be modified by setting the address-policy-full configuration back to BLOCK (or, additionally DROP or FAIL) if required.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-15 16:16:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miroslav Novak
2013-09-23 15:02:33 UTC
I'm changing the name of this issue since the default was already page before. This was just about changing that standalone-full, or any other XML file Clebert Suconic <clebert.suconic> updated the status of jira WFLY-2135 to Resolved There is PAGE policy in all standalone and domain files/profiles. Verified in EAP 6.2.0.ER4. Redrafted the supplied Doc Text for inclusion in the 6.2 Release Notes. Including the original content here for reference if needed: "Producing will block if you don't consume message over the current distributed configuration. Users have been considering this behavior counter intuitive as their producers are hanging whey they were expecting it to page. (some would think it as disk flush or other similar terms) The distributed file is now being change to PAGE Now over sent messages will just be paged. Be aware that you will use disk space if you don't consume messages. You may easily change it back to BLOCK if that's required." |