Skip to content
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.

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

Upgrade Pulsar client (3.2.2) and fix JMS priority on consumer side using Pulsar 3.x #119

Merged
merged 7 commits into from
Apr 9, 2024

Conversation

nicoloboschi
Copy link
Contributor

@nicoloboschi nicoloboschi commented Apr 8, 2024

  • Upgraded Pulsar client to 3.2.2
  • Implemented PriorityQueue on the consumer when it's an instance of Pulsar's structure (GrowableArrayBlockingQueue)

Other notes:

  • Upgraded plugins to work w/ jdk21

@nicoloboschi nicoloboschi changed the title make build compatible with jdk21 Upgrade Pulsar client (3.2.2) and improve JMS priority on consumer side Apr 8, 2024
Copy link
Collaborator

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

I left some style comments

@nicoloboschi nicoloboschi changed the title Upgrade Pulsar client (3.2.2) and improve JMS priority on consumer side Upgrade Pulsar client (3.2.2) and fix JMS priority on consumer side Apr 8, 2024
@nicoloboschi nicoloboschi changed the title Upgrade Pulsar client (3.2.2) and fix JMS priority on consumer side Upgrade Pulsar client (3.2.2) and fix JMS priority on consumer side using Pulsar 3.x Apr 8, 2024
@eolivelli
Copy link
Collaborator

eolivelli commented Apr 9, 2024

TCK Failure (suite with server side filters)

`FAILED........com/sun/ts/tests/jms/core20/jmscontexttopictests/Client.java#createSharedDurableConsumerTest1_from_standalone``

TCK failure (suite with client side filters)

FAILED........com/sun/ts/tests/jms/core20/sessiontests/Client.java#createSharedDurableConsumerTopicTest1_from_standalone

@@ -81,7 +81,7 @@ public void testAUTO_ACKNOWLEDGE() throws Exception {
}

try (MessageConsumer consumer = session.createConsumer(destination); ) {
assertEquals("foo", consumer.receive().getStringProperty("test"));
assertEquals("foo", consumer.receive(com.datastax.oss.pulsar.jms.utils.PulsarCluster.DEFAULT_RECEIVE_TIMEOUT).getStringProperty("test"));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is changing the test, why ?

receive() is different than receive(timeout)

@@ -92,12 +98,12 @@ public void testPulsar211Transactions() throws Exception {

@Test
public void testPulsar3Transactions() throws Exception {
test("apachepulsar/pulsar:3.0.0", true);
test("apachepulsar/pulsar:3.2.2", true);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.2.2 is buggy, maybe we can use 3.2.1 if tests don't pass

@@ -106,11 +112,22 @@ public void testLunaStreaming210Transactions() throws Exception {
test(LUNASTREAMING, true);
}

@Test
public void testLunaStreaming31Transactions() throws Exception {
// waiting for Apache Pulsar 2.10.1, in the meantime we use Luna Streaming 2.10.0.x
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can drop this comment

Copy link
Collaborator

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@nicoloboschi nicoloboschi merged commit cfda137 into master Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants