Kbase P134626: 4GL/ABL: What are the possible causes for 'no route to host' which is intermittently generated when
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/27/2008 |
|
Status: Unverified
GOAL:
4GL/ABL: What are the possible causes for 'no route to host' which is intermittently generated when running a socket client application?
GOAL:
How to suppress the 'no route to host' intermittently appearing on the client when running an application involving socket objects?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
The error: 'no route to host' can be caused by one of many network configuration issues. For example, connection timeout, router or other hardware not operating correctly due to hardware bugs, problematic firmware, bad cables, resource limitations etc.
The best way of suppress this error is to identify and resolve the actual network configuration issue responsible for generating it.
If the error occurs only intermittently indicating that the network is usually 'healthy', then using the NO-ERROR option where permissible for all statements referencing the socket object handle, its attributes and methods can minimize or even eliminate the appearance of this error on the client. Make sure to check the ERROR-STATUS system handle after each of the NO-ERROR statements and take the corrective appropriate action.