Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517375 - HornetQ: Address Full Policy eq BLOCK is ignored when using core bridges
Summary: HornetQ: Address Full Policy eq BLOCK is ignored when using core bridges
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.18
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-24 17:05 UTC by Ângelo Galvão
Modified: 2017-11-30 13:26 UTC (History)
2 users (show)

Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
Reproducer of the issue (deleted)
2017-11-30 13:26 UTC, Ângelo Galvão
no flags Details

Description Ângelo Galvão 2017-11-24 17:05:36 UTC
Description of problem:

When using core bridges the message flows between the origin queue to the target queue no matter if the target queue has a BLOCK policy and the address full policy is reached.

Version-Release number of selected component (if applicable):
6.4.18

How reproducible:


Steps to Reproduce:
1. Create 2 instances of JBoss EAP: server1 and server2.
2. Create queue1 on server1.
3. Create queue2 on server2.
4. Configure a address-settings for queue2 on server2 with address-full-policy to BLOCK and max-size-bytes to 100.
5. Create a bridge from queue1 on server1 to queue2 to server2.
6. Send 10000 test text messages to queue1. 

Actual results:

The message flows from queue1 to queue2 no matter the target queue has a BLOCK policy and the address full policy is reached.


Expected results:

Accumulate messages on queue1 when address full policy is reached on the queue2, blocking the flow between the queues until the BLOCK condition is over. This way he still can receive messages on queue1. 

Additional info:

Comment 1 Ângelo Galvão 2017-11-30 13:26:25 UTC
Created attachment 1360930 [details]
Reproducer of the issue

I attached a reproducer. It's content 3 artifacts:

1. domain.xml and host.xml - to configure your EAP 6.4 instances

2. hello-world java project - a modified version of the quickstart examples projects that are shipped with JBoss EAP. If you run the HelloWorldJMSClientSend class you can see the described behavior. 

If you run the commands you can see that the messages are following between the queues.

/host=master/server=broker-producer-server/subsystem=messaging/hornetq-server=default/jms-queue=queue-origin:count-messages

/host=master/server=broker-consumer-server/subsystem=messaging/hornetq-server=default/jms-queue=queue-target:count-messages


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