Skip to content

Added a suggestion #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Rutuja-desh wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Added a suggestion #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...-examples/pages/developing-producers-and-consumers-with-java-core-protocol.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ To effectively develop a Java Core Protocol client, it's crucial to understand t
.The relationship between ConnectionFactory, Connection, Session, Producer, and Consumer
image::core-protocol-components.png[Core Protocol Client Components, 600, 400]

// no image aaded here, please add
FIXME: no image aaded here, please add

[NOTE]
As highlighted in the provided context, the Core Protocol JMS client library allows for advanced features like flow control. You can configure `ConnectionFactory` properties such as `setConsumerWindowSize()` and `setProducerWindowSize()` to regulate the flow of messages and prevent resource exhaustion, especially in scenarios with varying producer and consumer speeds. For basic examples, default settings are often sufficient, but for performance-critical or high-volume applications, understanding and tuning these settings is crucial.
Expand Down
Loading