81009 is rpc failed.  This can happen for a number of reasons, it could be
network related, it could be the data server timing out your connection.  

A few points to look at / questions

Is this ud or uv ?

Does it take a fair amount of time to happen ? - what are your timeout
settings for unirpcd etc

What else is going on at this time - are there heavy reads and writes ?
have you got the network connections set as full duplex - I have had
experience of busy systems in half duplex giving this error.

Are you using pooling ?  - this can happen if the pool is busy and you
timeout during the connect.


Other things you can try are looking at netstat (if your data server is on
linux) and looking at the input and output queues for port 31438
 

Rgds
Symeon.



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of u2ug
Sent: 04 June 2008 19:41
To: [email protected]
Subject: [U2] UniObjects 81009 error

Occasionally when executing 
        ...
        UniDataSet DataSet = File.ReadRecords( RecordIds , FieldList )
        ...

We get this error :

IBMU2.UODOTNET.UniFileException: Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote
host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC
failedTABLENAME
   at IBMU2.UODOTNET.UniFile.ReadRecords(String[] aRecordIDSet, String[]
aFieldNameSet)

this happens in a loop using the same File & FieldList - RecordIds
varies.
Rerunning this same loop will sometimes complete successfully or could
generate the above exception at different points - no consistency.

Anyone have any insight as to what is causing this error or how to
prevent it ?

Gerry
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
No virus found in this incoming message.
Checked by AVG. 
Version: 8.0.100 / Virus Database: 269.24.6/1481 - Release Date: 6/3/2008
7:31 PM
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to