Kbase P122056: .NET exception when passing a MEMPTR as input parameter from a .NET Open Client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/02/2009 |
|
Status: Unverified
SYMPTOM(s):
.NET exception when passing a MEMPTR as input parameter
Communication layer message: Client communications Failure -System.IO.IOException: Failed 1000 attempts to read TcpClientMsgInputStream.
at Progress.UBroker.ClientMsgInputStream.readStream(Byte[] msgbuf, Int32 ofst, Int32 len)
at Progress.UBroker.ClientMsgInputStream.readubhdr()
at Progress.UBroker.BrokerSystem.readPacket() (8409). (7175)
Client Communications Failure - <Java Exception> (8409)
Communication layer message: <message text>. (7175)
When enabling tracing the following exception appears in the client log file:
WRITEDATA IOException: System.IO.IOException: Unable to write data to the transport connection: A non-blocking socket operation could not be completed immediately. ---> System.Net.Sockets.SocketException: A non-blocking socket operation could not be completed immediately
The AppServer agent status remains on "RECEIVING"
The problem also occurs when passing a large .NET DataSet
FACT(s) (Environment):
The options used from the .NET client to enable tracing are
Progress.Open4GL.RunTimeProperties.LogfileName = "log.txt";
Progress.Open4GL.RunTimeProperties.LoggingLevel = 7;
Progress.Open4GL.RunTimeProperties.LogEntryTypes = "DynamicApi,Broker";
Progress.Open4GL.RunTimeProperties.EnableTracing = true;
Using .NET 2.0
OpenEdge 10.1A
Windows
CAUSE:
Bug# OE00133967
FIX:
Upgrade to OpenEdge 10.1B or later.