RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-24 Thread Raymond P. de Bourbon
Whenever we have run into this kind of error (RPC error 81009) using
UniObjects.NET we have pretty much always been able to trace it back to
a single UDT/UV process that is taking excessively long, or requiring
excessive disk/memory IO in order to complete.. 

The common one we initially ran into was a particular select on a file
was not returning in a timely fashion, and only once a proper index was
put in place this problem was then mitigated, until later an additional
method that tried to read batches of records (which can be quite large
individually) from the same file started to timeout and generate
excessive amounts of this error. Through trial and error we found that
our particular process needed parameters to allow each client
installation to fine tune the size of batches and frequency with which
the offending file was scanned and processed...

It's probably not going to give you much, but I would recommend running
Filemon (from sysinternals) to watch the file/disk IO on the UDT server
while your .NET code executes to try and identify any IO bottlenecks...
It may just give you a direction with which to dig into...

Ray

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data from
th
 transport connection: An existing connection was forcibly closed by the
re
 host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed[IBM

 U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please verify UniVerse or
UniData
 Version. This feature may not be supported in older UniVerse or UniData

 version.

 UNIDATA 7.1.0

 Windows 2003


I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-23 Thread Glenn Batson
After speaking with our administrator he said:

Technically the card and switches are set to Auto-Duplex, which means
they are running in Full Duplex mode.

One weird things is these transport errors only occur between 1 AM and 6
AM.  We receive multiple in that time span but not all at the same time
and the same client does not have more than one.  For example:

2:01 AM Client A has the issue
2:32 AM Client C has the issue
2:46 AM Client B has the issue
2:59 AM Client D has the issue

I should mention that our backups complete before 2AM.  The night before
they were staggered like this but it all started at 3:00 AM.  Here is
the interesting thing.  We have 5 minute trapping of the listuser on our
UniData server.  We trap how many connections each client is using
(count of udcs by authentication credentials).  Every time this
transport occurs it occurs when a new udcs connection is being spawned.
For example client A may have not connections because the worker process
on IIS has shutdown for inactivity.  When activity occurs and the worker
process spawns the min connection I believe that connection is throwing
the transport error.  It also occurs when a client has had a min
connection of one and then it spawns a new connection and that new
connection has the transport error.  I believe these new connections are
the ones getting the transport error and I don't see the count go up
because a new one is spawned as a result of the transport error
happening.  This is because the logs on the server are only every 5
minutes.

Weird.  We are bumping up network logging but again we are pretty much
done with trying to figure out why and just writing better code to
handle the error when it occurs.

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Wednesday, April 22, 2009 1:19 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Need assistance replicating UniObjects.NET issue

I presume this is an intermittent error you are getting ?

Are you using the latest uodotnet.dll that goes with udt 7.1 ?

I see you are on windows, i am not sure if it has the same problems - i
know
on *nix you have to get the LANG env variable correct.

This may happen i suppose if your backend process crashes out, maybe
becuae
of a corrupt file or the machine is having some sort of problem - it may
be
worth seeing what else is happening when this happens. If you are
capturing
the exception in your .net app you can add some further info regarding
what
processes are running, time date etc into your error log.

Is your network card set to full duplex and the switch port it is
connected
to as well, i have had problems when comms have been in half duplex, and
the
connection is busy.



-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data from
th
 transport connection: An existing connection was forcibly closed by the
re
 host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed[IBM

 U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please verify UniVerse or
UniData
 Version. This feature may not be supported in older UniVerse or UniData

 version.

 UNIDATA 7.1.0

 Windows 2003


I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-23 Thread Symeon Breen
Glen wrote

 After speaking with our administrator he said:

Technically the card and switches are set to Auto-Duplex, which means
they are running in Full Duplex mode.


That may be the case but auto negotiate between the PC NIC and the switch
port does not always work - you should be able to tell from the switch port
if it actually has negotiated to full duplex or not. - Probably a barking up
the wrong tree there anyway.


Yes I agree a better way of capturing and dealing with these problems is the
way to go - my experience is of uniobjects.net in a web environment where we
are getting over 1 million hits per day, peaking at say 20 or more per
second and we do get a multitude of errors most days in the logs. - We
should not really ignore them but i think blips do just happen, certainly i
have found that the udt licence management is always a bit behind so if I
have all licences used and i drop a uniobjects connection and connect a new
one straight away it gives me a out of licence error - i sometimes have to
wait a few seconds before connecting again, which in web terms is a long
time. Sometimes i also getto thepoint where udt does not accept any new
uniobjects connections and the only way to fix this is to kill the unirpcd
service and restart it. 
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Need assistance replicating UniObjects.NET issue

2009-04-23 Thread Bill Haskett
   Symeon:
   Do you think this is pretty bogus or is it the Windows lag on releasing
   resources?
   Bill
   __

   From: Symeon Breen syme...@gmail.com
   Sent: 4/23/2009 1:34 PM
   To: u2-users@listserver.u2ug.org
   Subject: Re: [U2] Need assistance replicating UniObjects.NET issue

Glen wrote

After speaking with our administrator he said:

Technically the card and switches are set to Auto-Duplex, which means
they are running in Full Duplex mode.

That may be the case but auto negotiate between the PC NIC and the switch
port does not always work - you should be able to tell from the switch port
if it actually has negotiated to full duplex or not. - Probably a barking up
the wrong tree there anyway.

Yes I agree a better way of capturing and dealing with these problems is the
way to go - my experience is of uniobjects.net in a web environment where we
are getting over 1 million hits per day, peaking at say 20 or more per
second and we do get a multitude of errors most days in the logs. - We
should not really ignore them but i think blips do just happen, certainly i
have found that the udt licence management is always a bit behind so if I
have all licences used and i drop a uniobjects connection and connect a new
one straight away it gives me a out of licence error - i sometimes have to
wait a few seconds before connecting again, which in web terms is a long
time. Sometimes i also getto thepoint where udt does not accept any new
uniobjects connections and the only way to fix this is to kill the unirpcd
service and restart it.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-22 Thread Symeon Breen
I presume this is an intermittent error you are getting ?

Are you using the latest uodotnet.dll that goes with udt 7.1 ?

I see you are on windows, i am not sure if it has the same problems - i know
on *nix you have to get the LANG env variable correct.

This may happen i suppose if your backend process crashes out, maybe becuae
of a corrupt file or the machine is having some sort of problem - it may be
worth seeing what else is happening when this happens. If you are capturing
the exception in your .net app you can add some further info regarding what
processes are running, time date etc into your error log.

Is your network card set to full duplex and the switch port it is connected
to as well, i have had problems when comms have been in half duplex, and the
connection is busy.



-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data from
th
 transport connection: An existing connection was forcibly closed by the
re
 host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed[IBM

 U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please verify UniVerse or
UniData
 Version. This feature may not be supported in older UniVerse or UniData

 version.

 UNIDATA 7.1.0

 Windows 2003


I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Need assistance replicating UniObjects.NET issue

2009-04-22 Thread Bill Haskett
   Glen:
   Are  you  logging  the  UniObjects connection?  This may give you some
   additional information (it usually does for me).  To do so you should create
   a file in the ud71 directory named serverdebug.  I put the following
   line in mine:
   udcs 9 E:\IBM\ud71\log\udcs\udcs.log
   As you can see, the output goes to a new directory, ...\ud71\logs\udcs.
   To turn logging off change 9 to 0 (no quotes).
   HTH,
   Bill

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data
from the transport connection: An existing connection was forcibly
closed by the re host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009]
The RPC failed[IBM U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please
verify UniVerse or UniData Version. This feature may not be supported
in older UniVerse or Unidata version.

 UNIDATA 7.1.0

 Windows 2003

I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-22 Thread Glenn Batson
I am getting the error intermittently and in production.  We are using
the latest DLL on several of the clients that are having the issue, but
there are clients using the older version that are also getting the
issue.  We have not had to do anything with the LANG environment
variable for our UniObjects implementation to work.  The issue is not
happening due to a corrupt file.  In our logging we know the queries the
transport happened on.  I can go into the account and run the UniQuery
statement from ECL and it works just fine.  I'm not sure about your
network card full duplex comment. I've sent your email over to our admin
for clarification.  The servers are setting in the same rack/switch (big
enough pipe).

Right now I've pretty much given up on trying to figure out why the
exception is occurring and just try to make sure the code will handle
the issue more gracefully.  So I wanted to try and replicate to make
sure our code is good before putting in to production.

Thanks for the feedback.

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Wednesday, April 22, 2009 1:19 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Need assistance replicating UniObjects.NET issue

I presume this is an intermittent error you are getting ?

Are you using the latest uodotnet.dll that goes with udt 7.1 ?

I see you are on windows, i am not sure if it has the same problems - i
know
on *nix you have to get the LANG env variable correct.

This may happen i suppose if your backend process crashes out, maybe
becuae
of a corrupt file or the machine is having some sort of problem - it may
be
worth seeing what else is happening when this happens. If you are
capturing
the exception in your .net app you can add some further info regarding
what
processes are running, time date etc into your error log.

Is your network card set to full duplex and the switch port it is
connected
to as well, i have had problems when comms have been in half duplex, and
the
connection is busy.



-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data from
th
 transport connection: An existing connection was forcibly closed by the
re
 host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009] The RPC failed[IBM

 U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please verify UniVerse or
UniData
 Version. This feature may not be supported in older UniVerse or UniData

 version.

 UNIDATA 7.1.0

 Windows 2003


I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] Need assistance replicating UniObjects.NET issue

2009-04-22 Thread Glenn Batson
I tried setting up the logging on our development servers to see how it
works but there was really not any information being logged.  All I saw
was startup type info and logging of the authentication of the user.  So
only about 3 lines of logs for many queries to the database.  Maybe the
issue is on my development server it was using the old UniObjects DLL.
I'll have to try and correct this to see if I get more logging with the
new one.  One concern is we have a bunch of clients running on the same
server and so I'm not sure how well I'll be able to weed through the
debug logs or if there is any performance impact I should be concerned
about.

Thanks for the feedback.

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Bill Haskett
Sent: Wednesday, April 22, 2009 10:50 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Need assistance replicating UniObjects.NET issue

   Glen:
   Are  you  logging  the  UniObjects connection?  This may give you
some
   additional information (it usually does for me).  To do so you should
create
   a file in the ud71 directory named serverdebug.  I put the
following
   line in mine:
   udcs 9 E:\IBM\ud71\log\udcs\udcs.log
   As you can see, the output goes to a new directory,
...\ud71\logs\udcs.
   To turn logging off change 9 to 0 (no quotes).
   HTH,
   Bill

-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Glenn Batson
Sent: 22 April 2009 02:17
To: u2-users@listserver.u2ug.org
Subject: [U2] Need assistance replicating UniObjects.NET issue

Does anyone have any insight into how to create the following error.

Error Message: IBMU2.UODOTNET.UniXMLException: Unable to read data
from the transport connection: An existing connection was forcibly
closed by the re host.[IBM U2][UODOTNET - UNIRPC][ErrorCode=81009]
The RPC failed[IBM U2][UODOTNET - UNICLIENT][ErrorCode=91]  Please
verify UniVerse or UniData Version. This feature may not be supported
in older UniVerse or Unidata version.

 UNIDATA 7.1.0

 Windows 2003

I've tried killing the udapislave.exe process associated with the
connection and then accessing the connection.  I get a similar error but
not this one.  I've tried to sleep to long but noticed I we don't set
the timeout property on the UniObject and the default is no timeout.  So
it just sits there waiting.  I haven't tried unplugging the network
cable yet or mimicking some network interruption.

Any ideas would be greatly appreciated.

Thanks,

Glenn
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/