Back to bug 1011074

Who When What Removed Added
Miroslav Novak 2013-09-23 15:02:57 UTC CC csuconic
Clebert Suconic 2013-09-23 16:04:41 UTC Link ID JBoss Issue Tracker WFLY-2135
Clebert Suconic 2013-09-23 16:10:36 UTC Target Release --- EAP 6.2.0
Assignee jmesnil csuconic
Target Milestone --- ER4
Clebert Suconic 2013-09-23 18:14:08 UTC Status NEW POST
mark yarborough 2013-09-23 18:31:17 UTC CC jdoyle, myarboro
Flags needinfo?(jdoyle)
mark yarborough 2013-09-23 18:32:05 UTC CC jawilson, pslavice
Brian Stansberry 2013-09-23 18:45:12 UTC CC brian.stansberry
John Doyle 2013-09-23 18:54:46 UTC Flags needinfo?(jdoyle)
Jimmy Wilson 2013-09-23 19:01:29 UTC Flags needinfo?(csuconic)
Clebert Suconic 2013-09-23 19:07:12 UTC Flags needinfo?(csuconic)
Jimmy Wilson 2013-09-23 19:16:19 UTC Flags needinfo?(csuconic)
Clebert Suconic 2013-09-23 19:19:17 UTC Flags needinfo?(csuconic)
Clebert Suconic 2013-09-23 19:26:37 UTC Summary Change default value for address-full-policy from BLOCK to PAGE Change value for address-full-policy from BLOCK to PAGE on the distributed configurations
Clebert Suconic 2013-09-23 19:44:06 UTC Doc Text Cause:

Producing will block if you don't consume message over the current distributed configuration.

Consequence:

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)


Fix:

The distributed file is now being change to PAGE


Result:

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.
Clebert Suconic 2013-09-23 20:02:23 UTC Doc Text Cause:

Producing will block if you don't consume message over the current distributed configuration.

Consequence:

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)


Fix:

The distributed file is now being change to PAGE


Result:

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. 		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.
Doc Type Bug Fix Enhancement
Jimmy Wilson 2013-09-23 20:10:24 UTC Type Feature Request Bug
Brian Stansberry 2013-09-27 12:13:53 UTC Status POST MODIFIED
Vladimir Dosoudil 2013-10-04 06:55:44 UTC Status MODIFIED ON_QA
CC dosoudil
Brian Stansberry 2013-10-04 15:23:58 UTC CC brian.stansberry
Miroslav Novak 2013-10-07 08:23:22 UTC Status ON_QA VERIFIED
Scott Mumford 2013-11-19 04:01:37 UTC CC smumford
Doc Text 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. 		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 modified by setting the address-policy-full configuration back to BLOCK (or, additionally DROP or FAIL) if required.
Scott Mumford 2013-11-19 04:02:52 UTC 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 modified by setting the address-policy-full configuration back to BLOCK (or, additionally DROP or FAIL) if required. 		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.
mark yarborough 2013-12-15 16:16:53 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2013-12-15 11:16:53 UTC

Back to bug 1011074