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:
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM 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 IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
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.
Do not place IBM confidential, company confidential, or personal information into any field.