Bug 1011074 - Change value for address-full-policy from BLOCK to PAGE on the distributed configurations
Summary: Change value for address-full-policy from BLOCK to PAGE on the distributed co...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMS
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER4
: EAP 6.2.0
Assignee: Clebert Suconic
QA Contact: Miroslav Novak
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-23 15:02 UTC by Miroslav Novak
Modified: 2013-12-15 16:16 UTC (History)
7 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:16:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2135 0 Major Resolved Change distributed config on address settings to Page instead of Block 2015-06-23 11:21:45 UTC

Description Miroslav Novak 2013-09-23 15:02:33 UTC
Description of problem:
Change default value for address-full-policy from BLOCK to PAGE.

Comment 15 Clebert Suconic 2013-09-23 19:26:37 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

Comment 21 JBoss JIRA Server 2013-09-25 16:09:17 UTC
Clebert Suconic <clebert.suconic> updated the status of jira WFLY-2135 to Resolved

Comment 23 Miroslav Novak 2013-10-07 08:23:22 UTC
There is PAGE policy in all standalone and domain files/profiles.

Verified in EAP 6.2.0.ER4.

Comment 26 Scott Mumford 2013-11-19 04:01:37 UTC
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."


Note You need to log in before you can comment on or make changes to this bug.