Kbase P141849: Periodically database performs a forced shutdown after a select failure.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/07/2009 |
|
Status: Unverified
SYMPTOM(s):
Periodically database performs a forced shutdown after a select failure.
Select returned -1 , errno=<n>. (5138)
Select returned -1 , errno=10038. (5138)
net helpmsg 10038 returns: An operation was attempted on something that is not a socket.
Forcing shutdown, reason <num>. (744)
Forcing shutdown, reason 15. (744)
Clients connected to the database receive 9545 and 1423 errors when the select error occurs.
Disconnecting from database <database>, user number <usernum>. (9545)
There is no server for database <dbname>. (1423)
Server machine experiencing this issue is not up to the latest Microsoft updates.
Wireshark traces show that a socket was reset / closed by TCP upon initial client connection request to the broker.
Wireshark shows that the packet of information being sent between the client and the Broker during a connect statement was good.
FACT(s) (Environment):
Issue is not experienced on a backup server at this same site with 9.1E04 installed.
Backup server is running with the latest updates from Microsoft
9.1D09 Service Pack
Windows Advanced Server 2000 SP4
Progress 9.1D
CAUSE:
Enhancement Request# 0000003902
CAUSE:
TCP closed the socket for some unknown reason.
FIX:
Follow up with Operating System vendor to further investigate the network layer to identify why TCP closed/reset a socket when the packet being sent between the client and the broker process was valid.
An enhancement request 0000003902 was generated in the Enhancement Request System to change the behavior in future releases so that if a select error should occur with the errno=10038, that we would not perform a forced shutdown of the database. Once implemented, this change in behavior would result in the production database remaining online to service other client requests instead of shutting down. If you are interested in having this enhancement added to a future version of OpenEdge, please vote for enhancement request 0000003902 within the Enhancement Request System. See solution: P11255, ""Where is the Progress Enhancement Request System?"