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

Enhancement Request: support multiple JMS messages read in Reactive Messaging #5895

Open
5 tasks
satyanarayana-penugonda-eng opened this issue Jan 18, 2023 · 1 comment · May be fixed by #6074
Open
5 tasks
Assignees
Labels
3.x Issues for 3.x version branch enhancement New feature or request messaging Reactive Messaging P2 performance

Comments

@satyanarayana-penugonda-eng
Copy link

satyanarayana-penugonda-eng commented Jan 18, 2023

Environment Details

  • Helidon Version: 2.5.0
  • Helidon MP
  • JDK version: 11
  • OS: Oracle Linux Server
  • Docker version (if applicable):

Problem Description

I am working on an application (micro service) which uses Helidon MP 2.5.0 and Helidon JMS connector to consume the JMS messages produced by a weblogic server.
the weblogic server produces 1000 JMS messages per second .
The Helidon micro service application uses 14 JMS consumer channels (for the same destination) and acknowledges the JMS message immediately upon receiving the JMS message.
The Hellidon micro service app able to consume max 100 JMS Message per second .
Increasing the number of the JMS consumer channels further (> 14 ) is decreasing the performance.

Expected Behavior:
Request or receive more than one JMS message at a time using the Helidon JMS connector Consumer channel to increase the throughput.

Steps to reproduce

Consumer channel configuration

  IncomingOutboundQueue14:
        connector: helidon-jms
        session-mode: CLIENT_ACKNOWLEDGE
        destination: jms_module!event_outbound

Java code

  @Incoming("IncomingOutboundQueue14")
    @Acknowledgment(Acknowledgment.Strategy.MANUAL)
    public CompletionStage<Void> onMessage(final JmsMessage<String> message) throws IOException {
        if (log.atInfo().isEnabled()) {
            log.atInfo().log("The IncomingOutboundQueue14 message is started.");
        }
        return message.ack();
        
    }

Porting issues:

PRs:

@arjav-desai
Copy link
Member

Possible duplicate of #4380

@m0mus m0mus added enhancement New feature or request messaging Reactive Messaging labels Jan 19, 2023
@m0mus m0mus added the P2 label Jan 19, 2023
@danielkec danielkec linked a pull request Feb 5, 2023 that will close this issue
@github-actions github-actions bot added the 3.x Issues for 3.x version branch label Feb 5, 2023
@danielkec danielkec added this to the 3.1.2 milestone Feb 6, 2023
@barchetta barchetta modified the milestones: 3.1.2, 3.1.3 Feb 9, 2023
@barchetta barchetta modified the milestones: 3.2.0, 3.2.1 Mar 13, 2023
@barchetta barchetta modified the milestones: 3.2.1, 3.2.2 Apr 24, 2023
@barchetta barchetta removed this from the 3.2.2 milestone Jun 29, 2023
@m0mus m0mus added this to Backlog Aug 12, 2024
@m0mus m0mus moved this to In Progress in Backlog Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.x Issues for 3.x version branch enhancement New feature or request messaging Reactive Messaging P2 performance
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

5 participants