Kbase P48672: Error starting Fathom probe - The socket name is already in
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/17/2003 |
|
Status: Unverified
FACT(s) (Environment):
Fathom for Management 2.1A
SYMPTOM(s):
Exception at Fri Oct 17 11:18:18 CEST 2003: org.mortbay.util.MultiException
Message (throw): Error starting Fathom probe.
Message (excp): Multiple exceptions
Stack Trace:
org.mortbay.util.MultiException[java.net.BindException: The socket name is already in use.]
at org.mortbay.http.HttpServer.start(HttpServer.java(Compiled Code))
at com.progress.isq.ipqos.http.WebServer.startServer(WebServer.java(Compiled Code))
at com.progress.isq.ipqos.Probe.start(Probe.java(Compiled Code))
at com.progress.isq.ipqos.plugin.Fathom.start(Fathom.java(Compiled Code))
at com.progress.isq.ipqos.plugin.FathomPlugIn.run(FathomPlugIn.java:460)
at java.lang.Thread.run(Thread.java:513)
[Fathom] * Error starting Fathom probe: "Multiple exceptions" (10148)
Error starting Fathom probe - The socket name is already in use
Fathom does not start
Cannot access Fathom Management console
CAUSE:
Port being used by Fathom WebServer is busy.
FIX:
In order to fix the issue, please
1) stop the AdminServer
2) edit $FATHOM/config/fathom.properties and change the port for the webserver as per following example
[webserver]
httpport=9095
3) save the file and restart the AdminServer