Troubleshooting
Problem
When a client attempts to communicate with a WebSphere Java virtual machine (JVM) on a port secured with Transport Layer Security (TLS), but does not encrypt the message, the following message can be observed in the SystemOut.log file:
Prior to WebSphere Traditional 8.5.5.23 & 9.0.5.15 and Liberty 22.0.0.12, the message contained less information, and traces must be enabled to provide remote hostname, IP address, and port numbers associated with the connection.
*=info:SSL=all:SSLChannel=all:TCPChannel=allSymptom
It is common for this issue to have no observable functional impact and could be safely ignored. However, the connection is failing. The client which is invoking the connection is likely not functioning properly.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"ARM Category":[{"code":"a8m50000000Cd8DAAS","label":"WebSphere Application Server traditional-All Platforms-\u003ESecurity-\u003ESSL-\u003ESSL - General"}],"ARM Case Number":"TS007087266","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
ibm16497227