Thanks, Mike.
But the field you talk about is temporary, according to Microsoft.
The main problem is that unirpcd.exe doesn't understand the "timeout"
parameter.
You can reproduce this behaviour by telneting any Universe server on port
31438:
After that, any new RPC conection (UVADMIN i.e.) will fail.
If the Universe server is a unix box, then you can workaround it by starting
the unirpcd with the -timeout15 parameter.
What I am looking for, is a similar workaround for a Windows server.
Does anybody knows?
Thanks in advance,
Augusto
----- Original Message -----
From: "Mike Dallaire" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Thursday, May 15, 2008 7:21 PM
Subject: RE: [U2] Unirpc hunghup
Augusto,
I believe you want to go to Administrative Tools\Services and locate the
UniRPC service. From there you can stop the service and then right click
on
it an go to properties. At the bottom you should see a field to enter
start
parameters. This is where you would put your timeout setting, then start
the service.
HTH,
Mike
Michael Dallaire
Senior Applications Developer
IBM Certified Solutions Expert
Mortgage Builder Software, Inc.
Phone: (248) 304-0600 x 103
Fax: (248) 304-0601
[EMAIL PROTECTED]
www.mortgagebuilder.com
Providing Outstanding Support
It's more than just a company philosophy; it's a whole corporate culture
whose foundation is service.
Confidentiality Notice
This transmission may contain confidential information which is intended
for
the exclusive use of the intended recipient. Any disclosure, copying,
distribution or use of the contents by anyone other than the intended
recipient is strictly prohibited. If received in error, please reply to
the
sender immediately.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Augusto Alonso
Sent: Thursday, May 15, 2008 12:14 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Unirpc hunghup
Hi all.
Is there any way to start the unirpcd daemon with a timeout value, in a
Windows box, like in unix "unirpcd -timeout999"?
Whe have done it successfully under Linux, that is quite vulnerable under
viruses or unstable communications.
But is the first time we see this kind of "Denial Of Service" in a
Windows
server.
Is a Win2003 server with UniVerse 10.0.10.
The hung occurs usually in the afternoon, and is caused only by some
remote
users, not the local ones.
Could it would be caused by "black hole" routers?
Note: we have tried to start the service adding
"c:\ibm\uv\bin\unirpcd -timeout15" via REGEDIT, but it doesn't works.
Regards,
______________________________
Augusto Alonso Alonso
I.T. Manager
Quiter Servicios Informaticos S.L.
Tel: +34 902 23 33 23
Fax: +34 902 23 42 80
[EMAIL PROTECTED]
www.quiter.com
______________________________
----- Original Message -----
From: "Patricia Wilson" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Tuesday, July 25, 2006 10:09 PM
Subject: RE: [U2] Unirpc
Oh I found my answer in this Technote on IBM's website....
Is there a way to cause the "unirpcd" to timeout?
Problem
"unirpcd" requires a series of communication handshakes between the
client and server component before a service can be open and closed
down. If one of these handshakes is missing then the "unirpcd" will hang
in a wait / listening state thereby by "hanging" the "unirpcd" daemon.
This problem creates a situation where no new rpc services can be
started.
A timeout parameter was created to allow unirpcd abandon waiting for the
other part of the incoming request after a certain time so that it can
accept new requests. This fix is the result of a number of cases where
the unirpcd is left hanging waiting for input from the client and the
unirpcd daemon never getting it. The addition of this parameter is the
result of ECASE 5040 and applies to UniVerse 10.x and UniData 6.x
Cause
"unirpcd" was hanging due to client session not responding with
information for the "unirpcd" to process
Solution
NOTE: This applies to UNIX and Linux systems.
The "unirpcd" daemon can be started "manually" with a timeout value. The
syntax is as follows:
...../unirpcd -timeout300
There is no space between "-timeout" and the actual value. The timeout
value is in units of "seconds". In this case, the time is for 300
seconds.
The minimum meaningful timeout value is "1".
Note: This must be done at the command line. Existing menus, procedures,
and other code that already have a start sequence in them to start the
"unirpcd" will have to be changed to include this parameter. Until then,
these automated process will continue to start the "unirpcd" without any
timeout value.
-------
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/
