TIBCO Spotfire Server installed on Linux machine fails to start with 'java.net.SocketException: Permission denied' error in catalina.log
Article ID: KB0076862
Updated On:
| Products | Versions |
|---|---|
| Spotfire Server | All Versions |
Description
TIBCO Spotfire Server installed on Linux machines may fail to start after configuring HTTP on port 80 or HTTPS on port 443. In this situation, the following error is returned in the catalina.log:
10-Oct-2019 16:08:35.926 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-443]] org.apache.catalina.LifecycleException: Protocol handler initialization failed ... ... Caused by: java.net.SocketException: Permission denied
10-Oct-2019 16:08:35.926 SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component [Connector[HTTP/1.1-443]] org.apache.catalina.LifecycleException: Protocol handler initialization failed ... ... Caused by: java.net.SocketException: Permission denied
Issue/Introduction
TIBCO Spotfire Server installed on Linux machine fails to start with 'java.net.SocketException: Permission denied' error in catalina.log
Resolution
In Linux, ports below 1024 are called Privileged Ports and you get 'java.net.SocketException: Permission denied' error when you try to use ports under 1024 as a non-root user. This is a security feature originally implemented as a way to prevent a malicious user from setting up a malicious service on a well-known service port.
To resolve, the user running the TIBCO Spotfire Server needs to be root (superuser) or should have superuser privileges to bind to ports under 1024. Alternatively, a port above 1024 can be used for the TIBCO Spotfire Server.
To resolve, the user running the TIBCO Spotfire Server needs to be root (superuser) or should have superuser privileges to bind to ports under 1024. Alternatively, a port above 1024 can be used for the TIBCO Spotfire Server.
Additional Information
External: Privileged ports
External: Failed to bind to port 443
Feedback
Yes
No
Powered by
