Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

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

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Mar 21, 2018

Automated In-Doubt TX Cleanup

When there are in-doubt txs in the tranlog and partnerlogs when we undeploy an ear with a BPM resource adapter in it, there is no step done to clear the entries in the tranlog and partnerlog. Over time as we deploy new versions of our BPM application, we end up with a large number of unrecoverable in-doubt tx from our DB2 resource adapter. The in-doubt tx then cause a lot of noise in the BPM SystemOut.log. Currently these in-doubt tx can only be cleaned up manually. We request a functional enhancement for a way to have "unrecoverable" txs be removed from the tranlog and partnerlog files.

Ideally, this would be accomplished by a flag on the transaction service that says to remove or rollback any "unrecoverable" tx during startup. Our understanding is that L3 should be able to determine what is unrecoverable based on errors logged.

Alternatively, there could be a wsadmin command to purge txs for a resource. With the wsadmin command, we could incorporate the call into our automated deployment process. The wsadmin command could trigger the transaction service to locate any tx referencing the resource by its jndiName.

Idea priority Medium
RFE ID 117923
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Oct 27, 2021

    Thank you for the suggestion. The recommendation is to quiesce the BPM runtime before taking it down to avoid in-doubt transactions. Given this recommendation and the unlikelihood that we would deliver this enhancement due to backlog priorities, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters <>.