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 Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Feb 24, 2015

JAX-WS opens too many SSL connections

In our application we have a client in Liberty that makes JAX-WS soap calls to a backend server, also in Liberty. We've found that when we use ssl to make the JAX-WS calls, we can easily cause the server to open over 1024 sockets simultaneously, which exceeds the ulimit on the system and kills the backend server.
In the previous version of the product we had the same design, but used JAX-RPC/eWAS instead of JAXWS/Liberty and we did not have this issue with too many sockets being opened. We have tried some suggestions like setting http.keepAlive=true and http.maxConnections=5 as system properties but that did not help.

We are using Websphere Liberty where the JAX-WS implementation is provided using Apache CXF (2.2.6). Our understanding is that in eWAS, JAX-WS uses Channel framework to make outbound connections. At that layer there is a connection pool implementation available which maintains “Virtual Connections” that can be shared by multiple upper layer connections. In Websphere Liberty, there is no SSL connection pool available for outbound HTTP connections which can be leveraged by the JAX-WS/CXF layer.

Idea priority Urgent
RFE ID 66989
RFE Product WebSphere Application Server
  • Guest
    Sep 25, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - WebSphere Application Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Application Servers
    Product - WebSphere Application Server