Integration
This is an IBM Automation portal for Integration 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Idea / RFE Review. We continue to monitor this idea which unfortunately has not yet received sufficient support to get business prioritization. In the interim, we note that in similar circumstances other users have been able to achieve the desired behaviour through tuning other WXS parameters ... specifically, a combination of the parameters xioTimeout, xioRequestTimeout, requestRetryTimeout.
The goal for configuring these three properties is to find the balance between failing fast for the failing requests and ensuring that new failures are not introduced by the timeout settings. Having a very low timeout setting would lead to new requests to fail as well, while having a higher value would lead to longer wait times for threads which are waiting on failed requests.
The optimal value for these timeout parameters depends on a lot of external factors e.g. Network/IO operations, CPU for the servers. The optimal values can be only determined after running number of tests with various parameters.
For details about the three properties please refer to the Knowledge center link -
https://www.ibm.com/support/knowledgecenter/SSTVLU_8.6.1/com.ibm.websphere.extremescale.doc/txsreblmaps.html
**********************
Excerpts from the Knowledge center documentation -:
The xioTimeout setting determines how long the XIO transport attempts to establish a network socket connection.
The xioRequestTimeout value specifies how many seconds any request waits for a response before giving up. This property influences the amount of time a client takes to fail over if a network outage failure occurs. If you set this property too low, requests might time out inadvertently. Carefully consider the value of this property to prevent inadvertent timeouts.
The next level of tuning is the requestRetryTimeout. With each transport type, after it throws a system exception because an RPC did not complete in time, the eXtreme Scale client can use the additional time that is defined by the requestRetryTimeout setting (for example, the request timeout is 10 seconds, and the retry request timeout is 20 seconds) to specify how long it takes to complete the following actions.
The requestRetryTimeout property is set in milliseconds. Set the value greater than zero for the request to be retried on exceptions for which retry is available. Set the value to 0 to fail without retries on exceptions. To use the default behavior, remove the property or set the value to -1.
**********************
RFE Review. Thank you for taking the time to raise this enhancement suggestion and apologies it has been in Submitted status for so long. The embedded global cache capability is a functional area of the product which we have returned to in order to enhance it multiple times throughout the lifecycle of IIBv9, IIBv10 and ACEv11. We agree this suggestion would further refine how interactions occur and would lead to a more positive experience. Status of the RFE is updated to Uncommitted Candidate.