[Bug]: High memory usage in HTTP load tests with Update 12

[TharmiganK]

Description

$Subject

Experiencing this with the following lang timestamped version - 2201.12.0-20250221-092200-b3de4372

Steps to Reproduce

This can be reproducible with h1-transformation

1. Run the backend service - https://github.com/TharmiganK/netty-http-transport-sample using the following command:

   $ java -jar netty-http-echo-service.jar --ssl true --key-store-file ../keystore.p12 --key-store-password ballerina

2. Run the ballerina service: h1-transformation

3. Run the jmeter client using the jmx file by providing the necessary configurations. Use the following payload:

   {"size":"50B","payload":"0123456789ABCDEFGHIJKLM"} 

Update 11:

Update 12:

Affected Version(s)

Ballerina SwanLake Update 12

OS, DB, other environment details and versions

No response

Related area

-> Runtime

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[gimantha]

Shall we refactor the code to use ballerina/data.xmldata as ballerina/xmldata is deprecated now?

[TharmiganK]

Shall we refactor the code to use ballerina/data.xmldata as ballerina/xmldata is deprecated now?

Did that change but getting the same issue

Seems like the following ballerina-lang timestamped version already has the fix: 2201.12.0-20250227-072000-de1960af. Will check by updating this version and close the issue

[TharmiganK]

Checked with the above timestamped version, the load-test: h1-transformation is passing now

But the interceptors_passthrough load test is still failing.

I checked locally by running the load tests and it seems like the memory keeps increasing in update 12. See the screenshots below:

Update 11:

Update 12:

Steps to reproduce the issue:

1. Run the ballerina backend service

2. Run the ballerina service: interceptors_passthrough

3. Run the jmeter client using the jmx file by providing the necessary configurations. Configured jmx file - https://gist.github.com/TharmiganK/2c13075112bd26dffe2bc2d93667084c

[TharmiganK]

The memory issue is resolved with this new lang timestamped version - 2201.12.0-20250228-201300-8d411a0f

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.