Repeated Error 'The Administration Server was unable to establish JMX Connectivity with the $ManagedServerName' in the Managed Server Logs and Ephemeral Port Exhaustion on Server Running the WebLogic Domain After Configuring WebLogic for SSL
(Doc ID 2460284.1)
Last updated on MARCH 22, 2022
Applies to:Primavera P6 Enterprise Project Portfolio Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
The Windows server hosting WebLogic experiences ephemeral port exhaustion (resource starvation problem where a server is no longer able to use its TCP subsystem because it does not have any available connection slots). The bound status of Java to the ports increases rapidly (5-10 connections bound every 30 seconds) until port exhaustion, requiring a restart to the server hosting WebLogic. Also, users are unable to login to Team Member (which is one of the applications deployed to a managed server where all other domain resources are running) when this occurs and/or the P6 EPPM applications start to run very slowly. Monitoring the bound status of the Java processes on the server will indicate rapid connection bound growth until the point of ephemeral port exhaustion.
The WebLogic java processes should not experience ephemeral port exhaustion and/or extreme slowness within the applications - if users are able login.
The issue can be reproduced at will with the following steps:
1. Startup the WebLogic domain hosting the P6 EPPM applications.
2. Observe the reported behavior after the managed server has been running for a while.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!