You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* xref:pulsar-jms-implementation.adoc#unsupported-features[Unsupported and emulated features]
@@ -36,7 +36,7 @@ When you set a `clientId`, the actual subscription name in Pulsar is constructed
36
36
37
37
One solution for this situation is the *dead letter topic* policy. The *dead-letter topic* policy routes the unsuccessful messages to the *dead-letter topic* for storage, so consumers can keep consuming while the unsuccessful messages are stored in the dead-letter topic for processing or evaluation.
38
38
39
-
{starlight_jms} allows further configuration of `deadLetterPolicy`. For more on `deadLetterTopic` configuration properties, see xref:pulsar-jms-reference.adoc[].
39
+
{starlight_jms} allows further configuration of `deadLetterPolicy`. For more on `deadLetterTopic` configuration properties, see xref:reference:pulsar-jms-reference.adoc[].
40
40
[source,language-java]
41
41
----
42
42
Map<String, Object> deadLetterPolicy = new HashMap<>();
@@ -86,7 +86,7 @@ A few usage notes on negative acknowledgement in {starlight_jms}:
86
86
87
87
* Calling `Session.recover()` stops delivery in the session, restarts message delivery with the oldest unacked message, and sends *negative acknowledgements* to the broker for the unacked messages.
88
88
89
-
* When using xref:pulsar-jms-reference.adoc#client-side-emulation[client side emulation] with *JMS Queues* and *Shared Subscriptions*, if a message does not match the xref:pulsar-jms-implementation.adoc#message-selectors[Selector], the JMS Client *negatively acknowledges* the message to let another consume pick up the message. +
89
+
* When using xref:reference:pulsar-jms-reference.adoc[client side emulation] with *JMS Queues* and *Shared Subscriptions*, if a message does not match the xref:pulsar-jms-implementation.adoc#message-selectors[Selector], the JMS Client *negatively acknowledges* the message to let another consume pick up the message. +
90
90
91
91
* When using xref:pulsar-jms-server-side-filters.adoc[server side filtering] and xref:pulsar-jms-implementation.adoc#message-selectors[Selectors], there is still a chance that a *negative acknowledgement* will be sent when one message in a batch does not match the filter. +
92
92
Using *negative acknowledgement* increases the count of deliveries of the message, which can trigger routing to the dead-letter topic if the number exceeds `maxRedeliverCount`. So if you're seeing messages in the dead-letter topic that shouldn't be there, they might be hitting a consumer with a local selector that doesn't match too many times.
@@ -157,7 +157,7 @@ NOTE: Apache ActiveMQ is licensed under Apache 2.0.
157
157
158
158
For {starlight_jms} to create subscriptions it must be granted permission, and the broker must be configured to automatically create subscriptions by setting the `allowAutoSubscriptionCreation=true` parameter on the broker configuration.
159
159
160
-
For more on subscription creation, including disabling automatic subscription creation, see xref:pulsar-jms-mappings.adoc#subscriptions[JMS subscriptions].
160
+
For more on subscription creation, including disabling automatic subscription creation, see xref:reference:pulsar-jms-mappings.adoc#subscriptions[JMS subscriptions].
161
161
162
162
[#system-properties]
163
163
=== System properties and fields:
@@ -401,10 +401,10 @@ For more on multi-topic subscriptions in Pulsar, see the https://pulsar.apache.o
401
401
402
402
== What's next?
403
403
404
-
* *xref:pulsar-jms-quickstart-sa.adoc[]*: Create a simple command line Java JMS client that connects to a local Pulsar installation.
405
-
* *xref:pulsar-jms-quickstart-astra.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
406
-
* *xref:pulsar-jms-install.adoc[]*: Install {starlight_jms} in your own JMS project.
407
-
* *xref:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
408
-
* *xref:pulsar-jms-faq.adoc[]*: Frequently asked questions about {starlight_jms}.
409
-
* *xref:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
404
+
* *xref:jms-migration:pulsar-jms-quickstart-sa.adoc[]*: Create a simple command line Java JMS client that connects to a local Pulsar installation.
405
+
* *xref:jms-migration:pulsar-jms-quickstart-astra.adoc[]*: Create a simple command line Java JMS client that connects to an Astra Streaming instance.
406
+
* *xref:jms-migration:pulsar-jms-install.adoc[]*: Install {starlight_jms} in your own JMS project.
407
+
* *xref:reference:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
408
+
* *xref:ROOT:pulsar-jms-faq.adoc[]*: Frequently asked questions about {starlight_jms}.
409
+
* *xref:reference:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
Copy file name to clipboardExpand all lines: modules/jms-migration/pages/pulsar-jms-quickstart-astra.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -166,7 +166,7 @@ In the code example above, note the following points of interest and make the re
166
166
. This is the topic URI the client will use to publish and consume messages. You can create this using the Astra Streaming console. See the https://docs.datastax.com/en/astra-streaming/docs/astream-quick-start.html[Astra Streaming quick start].
167
167
. Your Astra Streaming security token which you can retrieve from the *Connect* tab for your tenant in the Astra Streaming console. See the https://docs.datastax.com/en/astra-streaming/docs/astream-quick-start.html[Astra Streaming quick start].
168
168
. A properties object containing your topic URI, your Astra Streaming token and the web and broker service URIs from the *Connect* tab for your tenant in the Astra Streaming console. See the https://docs.datastax.com/en/astra-streaming/docs/astream-quick-start.html[Astra Streaming quick start].
169
-
. Creates a {starlight_jms} queue. For more information on mapping Pulsar to JMS concepts, see xref:pulsar-jms-mappings.adoc[]
169
+
. Creates a {starlight_jms} queue. For more information on mapping Pulsar to JMS concepts, see xref:reference:pulsar-jms-mappings.adoc[]
170
170
. Creates a {starlight_jms} consumer context using the `createConsumer` method...
171
171
. ... and initializes an `onMessage` callback to consume the messages as they arrive.
172
172
. Sends 10 "Hello World!" messages to the queue using the `createProducer` method.
@@ -254,8 +254,8 @@ TIP: You'll find message `0` is produced at the very top of the output. It can g
254
254
255
255
* *xref:pulsar-jms-quickstart-sa.adoc[]*: Create a simple command line Java JMS client that connects to a local Pulsar installation.
256
256
* *xref:pulsar-jms-install.adoc[]*: Install {starlight_jms} in your own JMS project.
257
-
* *xref:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
258
-
* *xref:pulsar-jms-implementation.adoc[]*: Understand key implementation details for {starlight_jms}.
259
-
* *xref:pulsar-jms-faq.adoc[]*: Frequently asked questions about {starlight_jms}.
260
-
* *xref:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
257
+
* *xref:reference:pulsar-jms-mappings.adoc[]*: Understand Pulsar concepts in the context of JMS.
258
+
* *xref:examples:pulsar-jms-implementation.adoc[]*: Understand key implementation details for {starlight_jms}.
259
+
* *xref:ROOT:pulsar-jms-faq.adoc[]*: Frequently asked questions about {starlight_jms}.
260
+
* *xref:reference:pulsar-jms-reference.adoc[]*: {starlight_jms} configuration reference.
0 commit comments