Salesforce

OEE/OEM Fathom WebServer fails to start

Printable View
« Go Back

Information

 
TitleOEE/OEM Fathom WebServer fails to start
URL Name000059364
Article Number000171132
EnvironmentProduct: OpenEdge
Version: 10.2B
OS: Windows, Linux, Solaris
Other: Oracle Java 1.5
Question/Problem Description
Fathom WebServer fails to start: WARN!! Failed to start: FathomHTTPListener@0.0.0.0:9090
Exception : java.lang.Exception
   Message (excp):  Web Server startup failure java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind

fathom -query returns "Not running"

Fathom WebServer previously started without error.
Steps to Reproduce
Clarifying Information
Fathom plugin set to autostart with the AdminServer.
No port conflicts with fathom HTTP port (9090 default).
Error MessageCreating Fathom WebServer. (10169)
Fathom WebServer created. (10170)
Starting Fathom WebServer. (10144)
Listening for HTTP connections on port 9090
Fathom WebServer started. (10145)
Fathom probe started. (10147)
Listening for HTTP connections on port 9090
WARN!! Failed to start: FathomHTTPListener@0.0.0.0:9090

Exception : java.lang.Exception
Message (excp): Web Server startup failure java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind

Stack Trace:
java.lang.Exception: Web Server startup failurejava.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind

at com.progress.isq.ipqos.http.WebServer.startServer(WebServer.java:228)
at com.progress.isq.ipqos.http.WebServer.bounceServer(WebServer.java:162)
at com.progress.isq.ipqos.Probe.restartWebServer(Probe.java:1306)
at org.apache.jsp.about_jsp._jspService(about_jsp.java:244)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:204)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:651)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:863)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:775)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:939)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:792)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:455)
Defect Number
Enhancement Number
Cause
The socket does not get properly closed due to SUN (oracle) JVM 1.5 defect with regards to IPv6.
Resolution
In order to prevent this issue from happening the AdminServer needs to be configured to strictly use IPv4 only.

1. Stop the AdminServer

2. edit DLC/properties/AdminServerPlugin.properties file  
add to the current jvmargs under the [PluginPolicy.Progress.AdminServer] section with :

jvmargs=-Xmx1024x <whatever the current jvmargs are here> -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false

3. Restart the AdminServer.
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:29 AM
Powered by