Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at Merative works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at Merative, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Not under consideration
Categories Social Program Management Platform
Created by Guest
Created on May 11, 2023

RELATED IDEAS

Enhance curam transaction mgmt to timeout long running transactions

When a long running transaction is timed out by WAS, there is no transaction rollback issued on Curam and a result it leads either JVM to crash or the database, depending on the service layer logic.

In one example, when a large document 50MB is inserted and when that blob data is stored in federated database tables then due to OS issue there is no acknowledgement received by data access layer from DB2. The curam transaction is hanging there until Thread timeout reaches and then WAS terminates the thread, this leads to uncommitted data residing in DB2 memory causing database to crash after few attempts like this.

In another example, service layer logic had date calculation issue which resulted in not exiting the while loop and is calculating infinite future dates. As it gets into infinite loop, when the Thread timeout reaches and WAS terminates the thread and heap size allocated to this transaction (1GB) is not released causing hours of garbage collection and jvm becomes unresponsive.


Irrespective of how these issues can be resolved by other means, if Curam had managed its transaction and when that transaction reached near to timeout, if Curam issued a rollback on that transaction then all the jvm and db resources will be released and system do not crash.


This issue has been reviewed by the Core team via internal ticket associated with WH00013641 and hence creating an enhancement request for this.


Attached is the ticket info with details and examples.

WH00013641-prin...
WH00013641-printout.pdf
 WH00013641-printout.pdf
Open full size
WH00013641-printout.pdf
Customer Name WorkSafe BC
Market Segment Health & Human Services
Type of Request RFP
Market Opportunity

unknown
  • Attach files
  • CLAIRE MCGAFFEY
    Reply
    |     Aug 3, 2023

    Hi Chitanya,

    We have reviewed your enhancement suggestion.

    Based on the information provided, our understanding of your request is as follows:

    • You are requesting an enhancement to provide transaction management in product such that when a transaction reaches near to timeout, that Curam will issue a rollback on the transaction.

    Curam enlists both the database and application online transactions in an overall JTA transaction and if one of these transactions rolls back, then the complete JTA transaction rolls back. Logic exists currently in several places within the product that checks for that exact condition, where these aren't reached, it is intended that it should be that the application server (e.g. WAS) polices and eventually kills threads which it thinks are hung, and that should result in a proper rollback of database and JMS work.

    We do not intend to incorporate any further capabilities related to transaction management into our product as it does not align with our product strategy.

    We are therefore closing this request and do not plan to take any further action.

    Thank you for taking the time to share your ideas with us. Although we cannot pursue all the submitted suggestions, we are committed to involving our users in building our product roadmap and appreciate your ideas.

    Thank you,

    Sheryl Brenton, SPM Product Management Team

  • CLAIRE MCGAFFEY
    Reply
    |     May 15, 2023

    Hi Chitanya,

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    We will review the information you have provided and get back to you within 30 days. If additional details are required to complete our evaluation, we will send you a request for more information.

    Thank you,

    Sheryl Brenton, SPM Product Management Team