• State Not Answered
  • Replies 7 replies
  • Subscribers 7 subscribers
  • Views 5946 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Integrations

JBoss servers' CPU usage reaching >300% when Appian API is triggered by MuleSoft

Apoorv Gangwar
A Score Level 2

When the integration layer, MuleSoft triggers Appian's "PUT" service Web API sending around 100MB of data, the 2 JBoss servers CPU usage on the Appian side reaches >300%. Thereby causing performance issues and the MuleSoft gets 401 error, as the Web API is taking long time to process the data.

Has anyone faced this issue earlier and found a working solution to it? Any suggestions on how to resolve this JBoss CPU over utilization issue.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    What is the Web API doing functionally speaking? That's a large amount of data to send to the endpoint at once, and depending on the activities you are executing (e.g. starting processes, calling costly functions), it seems just to be an expensive operation. I would first consider batching the data into smaller chunks if possible, as well as analyzing the Web API to see if it can be optimized at all.
Reply
  • 0
    Certified Lead Developer
    What is the Web API doing functionally speaking? That's a large amount of data to send to the endpoint at once, and depending on the activities you are executing (e.g. starting processes, calling costly functions), it seems just to be an expensive operation. I would first consider batching the data into smaller chunks if possible, as well as analyzing the Web API to see if it can be optimized at all.
Children
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.