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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Submitted
Workspace WebSphere Liberty
Created by Guest
Created on Feb 17, 2026

RELATED IDEAS

Suport RMI/IIOP/ORB co-location optimization

If an application uses an EJB Remote interface instead of a local interface, and if the EJB is in the same JVM, each EJB call needs another thread in the Default Executor thread pool because the Liberty Yoko ORB does not support the optional co-location optimization. As observed in a support case, with <executor maxThreads="N" /> (required to limit native memory usage), there is a risk of a deadlock, when, for example, N concurrent HTTP requests each executing the remote EJB cause the thread pool to deadlock waiting for the EJBs to execute on Default Executor which is exhausted (if there's an EJB call timeout, it could still re-deadlock or livelock if there's a lot of queued HTTP work). The common guidance is to change the application to use a local instead and configure classloading to support such use: https://www.ibm.com/docs/en/was-liberty/core?topic=deal-using-enterprise-javabeans-applications-that-call-local-ejb-components-in-another-application

Although it's optimally performant to use local interfaces instead of remote if all calls are expected to be local, this can be a significant application development effort which can affect migration efforts to WebSphere traditional (which does support co-location optimization). If the Yoko ORB supported the co-location optimization, then that would avoid this deadlock potential and generally improve performance by avoiding the extra thread creation.

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.