Kbase P117004: How to force error 9407
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/18/2010 |
|
Status: Verified
GOAL:
How to force error 9407
GOAL:
How to force "Connection failure for host <host_name> port <port> transport <transport_name>. (9407)"
FACT(s) (Environment):
Progress/OpenEdge Product Family
All Supported Operating Systems
FIX:
The error "Connection failure for host <host_name> port <port> transport <transport_name>. (9407)" can have many causes, but handling it tends to be the same regardless of circumstance - try to reconnect to the AppServer and abort operation if that fails.
The following are guidelines to set up a test environment to simulate the various conditions:
- Make sure the AppServer and clients involved in the testing run on different machines. This will allow for testing of various networking conditions.
- Make sure the test AppServer is running with only 1 agent, unless load testing is being performed. This simplifies tracking the components involved.
- Use the appserver.broker.log and appserver.server.log to find out the PIDs of the processes involved. This is the P-nnnnnn entry seen on each line in the log files.
Possible tests include:
- Killing the AppServer agents on the OS level. ("End Task" from Task Manager on Windows, Kill -9 on Unix)
- Killing the AppServer broker on the OS level. ("End Task" from Task Manager on Windows, Kill -9 on Unix)
- Unplugging the network cables
- Other simulated network interference (ports taken over by other processes etc.)
Note that depending on timing and other factors, there may be other errors seen in addition to or instead of the error 9407