JAX-WS: Support the Caching of SSLSockets to improve performance.

neuwerk commented 2 years ago

Description

Our JAX-WS integration currently doesn't maintain SSLSockets across calls, in order to improve performance and reduce the impact of SSLSocket creation in high traffic environments, we should cache SSLSockets for reuse. Once created and stored in cache, the cache could then be checked for updates to the SSL Config, if the config has not changed, the socket in cache should be reused.

The JAX-RS and JAX-WS features have nearly identical Security services, and JAX-RS has since implemented the caching of SSLSockets. JAX-WS's support should be very very similar to implement. See #15534 for details on how the JAX-RS features were updated to support caching.

Documents

When available, add links to required feature documents. Use "N/A" to mark particular documents which are not required by the feature.

Aha: Externally raised RFE (TWAS-I-99)
UFO: Link to Upcoming Feature Overview document
- Set the Box link to be publicly accessible, with a long expiration (10 years)
- Click "Share" > select "People with link" > click "Link Settings" > under "Link Experation" select "Disable Shared Link on" > set an experation date ~10 years into the future
- If you lack permissions, contact OpenLiberty/release-architect
FTS: Link to Feature Test Summary GH Issue
Beta Blog: Link to Beta Blog Post GH Issue
GA Blog: Link to GA Blog Post GH Issue
Process Overview
Prioritization
Design
Implementation
Legal and Translation
Beta
GA
- Focal Point Approvals
Other Deliverables

General Instructions

The process steps occur roughly in the order as presented. Process steps occasionally overlap.

Each process step has a number of tasks which must be completed or must be marked as not applicable ("N/A").

Unless otherwise indicated, the tasks are the responsibility of the Feature Owner or a Delegate of the Feature Owner.

If you need assistance, reach out to the OpenLiberty/release-architect.

Important: Labels are used to trigger particular steps and must be added as indicated.

Prioritization (Complete Before Development Starts)

The (OpenLiberty/chief-architect) and area leads are responsible for prioritizing the features and determining which features are being actively worked on.

Prioritization

[ ] Feature added to the "New" column of the Open Liberty project board
- Epics can be added to the board in one of two ways:
- From this issue, use the "Projects" section to select the appropriate project board.
- From the appropriate project board click "Add card" and select your Feature Epic issue
[ ] Priority assigned
- Attend the Liberty Backlog Prioritization meeting
Design (Complete Before Development Starts)

Design preliminaries determine whether a formal design, which will be provided by an Upcoming Feature Overview (UFO) document, must be created and reviewed. A formal design is required if the feature requires any of the following: UI, Serviceability, SVT, Performance testing, or non-trivial documentation/ID.

Design Preliminaries

[ ] UI requirements identified. (Owner and UI focal point)
[ ] ID requirements identified. (Owner and ID focal point)
- Refer to Documenting Open Liberty.
- Feature Owner adds label ID Required, if non-trivial documentation needs to be created by the ID team.
- ID adds label ID Required - Trivial, if no design will be performed and only trivial ID updates are needed.
[ ] Serviceability Requirements Identified. (Owner and Serviceability focal point)
[ ] SVT Requirements Identified. (Owner and SVT focal point)
[ ] Performance testing requirements identified. (Owner and Performance focal point)

Design

[ ] POC Design / UFO review requested.
- Owner adds label Design Review Request
[ ] POC Design / UFO review scheduled. (David Chang)
[ ] POC Design / UFO review completed.
[ ] POC / UFO Review follow-ons completed.
[ ] Design / UFO approved. (OpenLiberty/chief-architect) or N/A
- (OpenLiberty/chief-architect) adds label Design Approved
- Add the public link to the UFO in Box to the Documents section.
- The UFO must always accurately reflect the final implementation of the feature. Any changes must be first approved. Afterwards, update the UFO by creating a copy of the original approved slide(s) at the end of the deck and prepend "OLD" to the title(s). A single updated copy of the slide(s) should take the original's place, and have its title(s) prepended with "UPDATED".

No Design

[ ] No Design requested.
- Owner adds label No Design Approval Request
[ ] No Design / No UFO approved. (OpenLiberty/chief-architect) or N/A
- Approver adds label No Design Approved

FAT Documentation

[ ] "Feature Test Summary" child task created
- Use the Feature Test Summary Template
- Add FTS issue link to the Documents section.
Implementation

A feature must be prioritized and socialized (or No Design Approved) before any implementation work may begin and is the minimum before any beta code may be delivered. All new Liberty content must be inaccessible in our GA releases until it is Feature Complete by either marking it kind=noship or beta fencing it.
Code may not GA until this feature has obtained the "Design Approved" or "No Design Approved" label, along with all other tasks outlines in GA section.

Feature Development Begins

[ ] Add the In Progress label

Legal and Translation

In order to avoid last minute blockers and significant disruptions to the feature, the legal items need to be done as early in the feature process as possible, either in design or as early into the development as possible. Similarly, translation is to be done concurrently with development. Both MUST be completed before Beta or GA is requested.

Legal (Complete before Feature Complete Date)

[ ] Changed or new open source libraries are cleared and approved, or N/A. (Legal Release Services/Cass Tucker/Release PM).
[ ] Licenses and Certificates of Originality (COOs) are updated, or N/A

Translation (Complete 1 week before Feature Complete Date)

[ ] PII updates are merged, or N/A. Note timing with translation shipments.
Beta

In order to facilitate early feedback from users, all new features and functionality should first be released as part of a beta release.

Beta Code

[ ] Beta fence the functionality
- kind=beta, ibm:beta, ProductInfo.getBetaEdition()
[ ] Beta development complete and feature ready for inclusion in a beta release
- Add label target:beta and the appropriate target:YY00X-beta (where YY00X is the targeted beta version).
[ ] Feature delivered into beta
- (OpenLiberty/release-manager) adds label release:YY00X-beta (where YY00X is the first beta version that included the functionality).

Beta Blog (Complete 1.5 weeks before beta eGA)

[ ] Beta blog issue created and populated using the Open Liberty BETA blog post template.
- Add a link to the beta blog issue in the Documents section.
GA

A feature is ready to GA after it is Feature Complete and has obtained all necessary Focal Point Approvals.

Feature Complete

[ ] Feature implementation and tests completed.
- [ ] All PRs are merged.
- [ ] All epic and child issues are closed.
- [ ] All stop ship issues are completed.
[ ] Legal: all necessary approvals granted.
[ ] Translation: All messages translated or sent for translation for upcoming release
[ ] GA development complete and feature ready for inclusion in a GA release
- Add label target:ga and the appropriate target:YY00X (where YY00X is the targeted GA version).
- Inclusion in a release requires the completion of all Focal Point Approvals.

Focal Point Approvals (Complete by Feature Complete Date)

These occur only after GA of this feature is requested (by adding a target:ga label). GA of this feature may not occur until all approvals are obtained.

All Features

[ ] FAT All Tests complete and running successfully in SOE or N/A. (OpenLiberty/fat-approvers)
- Approver adds label focalApproved:fat.
[ ] Demo Demo is scheduled for an upcoming EOI or N/A. (OpenLiberty/demo-approvers)
- Approver adds label focalApproved:demo.
[ ] Globalization Translation and TVT are complete or N/A. (OpenLiberty/globalization-approvers)
- Approver adds label focalApproved:globalization.

Design Approved Features

[ ] Accessibility Accessibility testing completed or N/A. (OpenLiberty/accessibility-approvers)
- Approver adds label focalApproved:accessibility.
[ ] APIs/Externals Externals have been reviewed or N/A. (OpenLiberty/externals-approvers)
- Approver adds label focalApproved:externals
[ ] ID Documentation is complete or N/A. (OpenLiberty/id-approvers)
- Approver adds label focalApproved:id.
- NOTE: If only trivial documentation changes are required, you may reach out to the ID Feature Focal to request a ID Required - Trivial label. Unlike features with regular ID requirement, those with ID Required - Trivial label do not have a hard requirement for a Design/UFO.
[ ] Performance Performance testing is complete or N/A. (OpenLiberty/performance-approvers)
- Approver adds label focalApproved:performance.
[ ] Serviceability Serviceability has been addressed or N/A. (OpenLiberty/serviceability-approvers)
- Approver adds label focalApproved:sve.
[ ] STE Skills Transfer Education chart deck is complete or N/A. (OpenLiberty/ste-approvers)
- Approver adds label focalApproved:ste.
[ ] SVT System Verification Test is complete or N/A. (OpenLiberty/svt-approvers)
- Approver adds label focalApproved:svt.

Remove Beta Fencing (Complete by Feature Complete Date)

[ ] Beta guards are removed, or N/A
- Only after all necessary Focal Point Approvals have been granted.

GA Blog (Complete by Feature Complete Date)

[ ] GA Blog issue created and populated using the Open Liberty GA release blog post template.
- Add a link to the GA Blog issue in the Documents section.

Post GA

[ ] Replace target:YY00X label with the appropriate release:YY00X. (OpenLiberty/release-manager)
Other Deliverables
[ ] OL Guides OL Guides assessment is complete or N/A. (Yee-Kang Chang)
[ ] Standalone Feature Blog Post A blog post specifically about your feature or N/A. (OpenLiberty/release-architect)
- This should be strongly considered for larger or more prominent features.
- Follow instructions in the blogs repo.
[ ] WDT Liberty Developer Tools work is complete or N/A. (Leonard Theivendra)

neuwerk commented 1 year ago

Feature is on hold due to other priories, but should pick up by the beginning of the year.

cbridgha commented 1 year ago

Closing at this time - Outlook for resources and priority is too low to justify keeping open

nburazor commented 1 year ago

We experience a high CPU consumption after migrating the customer application from WebSphere Traditional to WebSphere Liberty.

CPU comparison (Month/Month) before and after Migration: Z CPU Std.
========== 2022.08 IAP 388 (CPU h) -> WebShere Traditional 2023.08 IAP 1.689 (CPU h) -> WebSphere Liberty

The application is mainly acting as WebService proxy using a JAX-WS as WebService client. The client communication is using SSL and client certificate authorization.

OpenLiberty / open-liberty