ePO Application Server Service (Tomcat) shuts down shortly after starting due to a port conflict
Last Modified: 2023-06-06 05:30:51 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
ePO Application Server Service (Tomcat) shuts down shortly after starting due to a port conflict
Technical Articles ID:
KB92323
Last Modified: 2023-06-06 05:30:51 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x
Problem
The ePO Application Server Service starts successfully, but soon after shuts down (usually within 1–3 minutes) due to a port conflict. The java.net.BindException: Address already in use: JVM_Bind NOTE: The port, listed in the example as 8005, can vary depending on the environment. If the Solution 1
The shutdown port is a default configuration for Tomcat, and not specific to the ePO Application Server service configuration. As ePO does not use the server shutdown port, you can simply disable this port in the ePO's
Affected ProductsLanguages:This article is available in the following languages: |
|