DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Info |
|---|
This page applies to Java Broker versions before 0.18. For the master copy of this documentation see the Producer Flow Control section in the Java documentation |
| Table of Contents |
|---|
General Information
The Qpid Java Broker 0.6 release introduces a simplistic producer-side flow control mechanism into the Java Messaging Broker, causing producers to be flow-controlled when they attempt to send messages to an overfull queue or overfull message store on a virtual host.
Server configuration
Configuring a Queue to use flow control
...
The disk quota functionality is based on "best effort" principle. It means that broker cannot guarantee that disk space limit will not be exceeded. If several concurrent transactions are started before the limit is reached then all of them will be committed into disk even when disk quota is exceeded.
Broker Log Messages for quota flow control
There are 2 new Broker log messages that may occur if flow control through disk quota limits is enabled.
When virtual host is blocked due to exceeding of the disk quota limit the following message appears in the broker log
| No Format |
|---|
[vh(/test)/ms(BDBMessageStore)] MST-1008 : Store overfull, flow control will be enforced
|
When virtual host is unblocked after cleaning the disk space the following message appears in the broker log
| No Format |
|---|
[vh(/test)/ms(BDBMessageStore)] MST-1009 : Store overfull condition cleared
|
Client impact and configuration
...