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
[WFLY-15405] AMQP Connector for reactive messaging #16281
Conversation
7258098
to
777dd34
Compare
@kabir The weld/transaction commit can be rebased out; that JIRA is resolved in main. |
777dd34
to
133380c
Compare
@bstansberry oops. Should be good now |
Dependency Tree Analyzer Output: New Dependencies:
CC @wildfly/prod |
133380c
to
b8342b3
Compare
b8342b3
to
67d8c99
Compare
67d8c99
to
68b13d5
Compare
68b13d5
to
1a9c7a6
Compare
1a9c7a6
to
6857ad1
Compare
6857ad1
to
b18b151
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've went through circa half of this PR and put some comments. Mostly regarding the documentation. I'll do rest later :)
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...mon/src/main/resources/layers/standalone/microprofile-reactive-messaging-amqp/layer-spec.xml
Outdated
Show resolved
Hide resolved
...galleon-common/src/main/resources/modules/system/layers/base/io/vertx/proton/main/module.xml
Outdated
Show resolved
Hide resolved
...file/reactive/messaging/config/amqp/ssl/context/AmqpReactiveMessagingSslConfigProcessor.java
Outdated
Show resolved
Hide resolved
...tive/messaging/config/amqp/ssl/context/_private/MicroProfileReactiveMessagingAmqpLogger.java
Outdated
Show resolved
Hide resolved
...microprofile/reactive/messaging/common/security/BaseReactiveMessagingSslConfigProcessor.java
Outdated
Show resolved
Hide resolved
...tension/microprofile/reactive/messaging/deployment/ReactiveMessagingDependencyProcessor.java
Outdated
Show resolved
Hide resolved
...le/reactive/messaging/config/kafka/ssl/context/KafkaReactiveMessagingSslConfigProcessor.java
Show resolved
Hide resolved
6d18c38
to
97d574c
Compare
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...asciidoc/_admin-guide/subsystem-configuration/MicroProfile_Reactive_Messsaging_SmallRye.adoc
Outdated
Show resolved
Hide resolved
...file/reactive/messaging/config/amqp/ssl/context/AmqpReactiveMessagingSslConfigProcessor.java
Outdated
Show resolved
Hide resolved
...file/reactive/messaging/config/amqp/ssl/context/AmqpReactiveMessagingSslConfigProcessor.java
Outdated
Show resolved
Hide resolved
477b3f8
to
7589e86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Kabir, I've put two more minor comments regarding the documentation. I believe that this is all from me at the moment. Note there is one comment from me from last week that you didn't address. Is it on purpose or you just missed it/postponed it? 🙂
|
||
`mp.messaging.outgoing.to.connector=smallrye-amqp` says that we want to use AMQP to back the `to` channel. Note that the value `smallrye-amqp` is SmallRye Reactive Messaging specific, and will only be understood if the AMQP connector is enabled. | ||
|
||
`mp.messaging.outgoing.to.address=my-queue` says that we will send data via `to` channel to the AMQP queue on address called `my-queue`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`mp.messaging.outgoing.to.address=my-queue` says that we will send data via `to` channel to the AMQP queue on address called `my-queue`. | |
`mp.messaging.outgoing.to.address=my-topic` says that we will send data via `to` channel to the AMQP topic (or queue) on address called `my-topic`. |
Just to stay consistent with the above example.
|
||
`mp.messaging.incoming.from.connector=smallrye-amqp` says that we want to use AMQP to back the `from` channel. As above, the value `smallrye-amqp` is SmallRye Reactive Messaging specific. | ||
|
||
`mp.messaging.incoming.from.address=my-queue` says says that the channel named `from` will read data from the AMQP topic (or queue) on address called `my-topic`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`mp.messaging.incoming.from.address=my-queue` says says that the channel named `from` will read data from the AMQP topic (or queue) on address called `my-topic`. | |
`mp.messaging.incoming.from.address=my-topic` says that the channel named `from` will read data from the AMQP topic (or queue) on address called `my-topic`. |
7589e86
to
35e1293
Compare
@jstourac I missed it. Hopefully it should be fine now :-) |
f14da54
to
67f8e46
Compare
67f8e46
to
891747a
Compare
d7ad79d
to
35a71f7
Compare
8a57a4c
to
7b2cf2a
Compare
31cfb8d
to
f859204
Compare
FYI: I've run Wildfly TS with latest changes and there is no issue related to this PR. |
Google DNS causes problems looking up services in Kubernetes
f859204
to
2bb00dd
Compare
/* | ||
* Copyright The WildFly Authors | ||
* SPDX-License-Identifier: Apache-2.0 | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one has two headers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the second one
@@ -0,0 +1,57 @@ | |||
/* | |||
* JBoss, Home of Professional Open Source. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be ASL now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See L24-27 -- it looks like the header switch got messed up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bstansberry already fixed?
@@ -0,0 +1,74 @@ | |||
/* | |||
* JBoss, Home of Professional Open Source. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be ASL now?
56b528b
to
1d4a7c4
Compare
Next we will briefly discuss each of these entries. Remember the `to` channel is on the `send()` method, and the `from` channel is on the `receive()` method. | ||
|
||
|
||
'amqp-host=localhost' '`amqp-port=5672` points the connector to an AMQP broker running on `localhost:5672`. As before we could also have done these for an individual channel by for example specifying `mp.messaging.outgoing.to.host=localhost` instead. If the host is not specified, it defaults to `localhost. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kabir This can be done in a follow up fix, but whatever turns on italics here needs to be fixed.
Note -- please don't make any docs fixes I mention here on this PR unless you have to change something that justifies new CI. They can come later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bstansberry I've never seen the source be italic before, but it turns out it was due to some unclosed quotes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in #17491
<dependency> | ||
<groupId>io.smallrye.reactive</groupId> | ||
<artifactId>smallrye-mutiny-vertx-amqp-client</artifactId> | ||
<exclusions> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Future fix:
'exclusions' should not appear here unless there is a good reason they don't appear in the bom.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICR those boms did not exist when I worked on this code 1.5 years ago :-D
I'll leave it as-is, and have opened https://issues.redhat.com/browse/WFLY-18852 to clean up this pom since I see other exclusions than mine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made a start in #17491
@@ -705,6 +705,7 @@ | |||
<layer>microprofile-openapi</layer> | |||
<layer>microprofile-reactive-streams-operators</layer> | |||
<layer>microprofile-reactive-messaging</layer> | |||
<layer>microprofile-reactive-messaging-amqp</layer> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please file a JIRA to add a provisioning execution with only the layer. All layers need an individual execution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in #17491
Thanks @kabir! |
https://issues.redhat.com/browse/WFLY-15405 - Support for the AMQP connector in the MP Reactive Messaging subsystem
Includes #17343 so this can be tested with the latest SmallRye Reactive Messaging which will likely be merged by the time this is tested