Kbase 20106: V8 Error 5483 5476 with appserver broker
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
Connection failure for service <service_name> host <host_name> transport <transport_name>. (5483)
Application server connect failure. (5468)
<component_name> Shutdown. (5476)
CAUSE:
An example of the errors reported in the log may be similar to the
following:
09:23:56 05 Jul 2000 Application Server 123456
Connection failure for service host host1 transport TCP (5483)
09:23:56 05 Jul 2000 Application Server 123456
Application Server shutdown (5476)
10:08:52 05 Jul 2000 Application Broker 112233
Connection failure for service service1 host xx.xx.xx.xx transport
TCP (5483)
10:08:52 05 Jul 2000 Application Broker 112233
Application Broker Shutdown (5476)
These are errors occurring on the AppServer side not on the
client side. The client has no ability to write to the AppServer log.
The 1st 5483 means that the Application Server process with pid 123456
had a networking failure relative to some client. The client was
running on host host1. The "service" is intended to be the port that
the client was connected to. That is, it is the port that the server
is listening on.
Since the server is listening on a dynamically allocated port (the
broker is the one listening in on the port specified via -S) the value
is not getting filled in. This is somewhat misleading.
The 1st 5476 is just indicating that Application Server 123456 is
being shutdown since it is no longer connected to the client.
The 2nd 5483 is coming from the broker whose pid is 112233. It had a
networking failure relative to some client that is running on a
machine whose IP address is xx.xx.xx.xx. Apparently, the broker could
not determine the host name that the second client is running so it is
printing out the IP address rather than the host. In this case the
client was connected to the broker which is listening on port
indicated by the service (-S) .
Since these errors occurred on the server side, there may be network
errors reported on the client side as well.
FIX:
Diagnostics may be run on the network and fix the network connection problem between appserver and the client.