Kbase P169320: .Net clients have sporadic problems connecting with the NameServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/28/2010 |
|
Status: Unverified
SYMPTOM(s):
.NET clients have sporadic problems connecting with the NameServer
The client closes after showing a NameServer socket error
Progress.Open4GL.Exceptions.NameServerCommunicationsException: Connect Failure: NameServer Communications Failure - System.NetSockets.SocketException:
A lock Operation was interrupted by a call to WSACancelBlockingCall
at Progress.SupportClass.UdpClientSupport.Recieve (UdpClientSupport tempClient, PacketSupport packet)
at Progress.NameServer.Client.NameServerClient.receiveResponse (int32 responseCount, String applicationService) (8230)
FACT(s) (Environment):
Client can reconnect after the error happened without problems
AppServer and database brokers resides in the same box
AppServer connects to the database through TCP using the -S parameter
AppServer works in Stateless mode
OpenEdge 10.2A
SuSe Enterprise Server 10
CAUSE:
The exact cause is unknown at the time of this writing.
FIX:
Change the AppServer's database connection to self service (using shared memory).