We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SolaceErrorTopicPublisherHandler
https://github.com/SolaceCoEExt/solace-quarkus/blob/76d9f4fe7052f2c4e5eff06ed9077de93036ca6f/pubsub-plus-connector/src/main/java/io/quarkiverse/solace/fault/SolaceErrorTopicPublisherHandler.java#L33
We can remove the errorTopic field completely.
The text was updated successfully, but these errors were encountered:
@SravanThotakura05 Here we can simply log the exception on the result Uni :
return Uni.createFrom().<PublishReceipt>emitter(e -> { try { // always wait for error message publish receipt to ensure it is successfully spooled on broker. publisher.publish(outboundMessage, Topic.of(errorTopic), e); } catch (Throwable t) { e.fail(t); } }).onFailure().invoke(t -> SolaceLogging.log.publishException(errorTopic, t));
Sorry, something went wrong.
Fixed Issues - #9 #10 #12
fabf948
SravanThotakura05
Successfully merging a pull request may close this issue.
https://github.com/SolaceCoEExt/solace-quarkus/blob/76d9f4fe7052f2c4e5eff06ed9077de93036ca6f/pubsub-plus-connector/src/main/java/io/quarkiverse/solace/fault/SolaceErrorTopicPublisherHandler.java#L33
We can remove the errorTopic field completely.
The text was updated successfully, but these errors were encountered: