Uniface version is 7205.
The problem is that out of the blue, when new clients log in, their
uniface.exe process wants 100 % CPU, and hanging up their session and
the server.
The login process is a spawn to a vms server with a token device.
It occurs when the server holds up to 6 to 9 concurrent sessions and
it is hard to reproduce by me without hassing the customers.
On the production NT 4 machines, holding up to 60 concurrent users,
this is not happening.
The uniface application is started form a network location, the only
thing local is the DOL file, for network performance reasons.
Uniface has not been installed on the server. This is our normal
standard because we have this running for over 3 years now. Only some
environment entries for access to the database server is needed.
I hope that someone has a clue for me.
greetings jeroen
I have now placed both the dol and urr on the local file system and set the
$putmess_logfile to ica_prod%p where %p is the process id of the uniface
application appended to the log file name. The combination of all of these
seem for the last 3 days to have stabilised the application. Before this we
were a minimum of 3 times a day having to deal with these problems.
Peterr
"jeroen" <jer...@jeroenpolman.com> wrote in message
news:cj1l5vga2to9dh9j8...@4ax.com...
ok, thanks for the input. Did you had any change of reproducing the
error yourself? I made a test script, stressing the server and i got
the error back once now. The error only occurs when clients log in,
using the spawn service. When i kill the client, then using an
existing session form an other client, any other spawn session for an
action in the application is doing fine.
Did you do this by yourself? Or did you had any assistance from
Microsoft or Compuware?
I will try to reproduce the error again and ten make the changes you
did.
i will keep you informed.
greetings jeroen
The problem is that even the administrator can't open the URR file,
not even in notepad. The error is "an unspecified network error
occurred". MS Technet talks about 2 dll's to upgrade, but they are of
a higher version on the server, so that won't be the problem.
We can live with this work around, so we keep it this way.
greetings jeroen
On Thu, 27 Feb 2003 11:55:39 +0100, jeroen <jer...@jeroenpolman.com>
wrote:
After I followed the steps:
1. modified the entity in uniface development;
2. droped the corresponding table in DB;
3. compiled the object service;
4. created the table in DB;
5. updated the file udesc.urr the same time,
I got -150 when the object service was run.
Anybody tell me what should I do?
Thanks very much!
Tommy
Thanks!
-----Ursprungliche Nachricht-----
Von: owner-U...@uug.org [mailto:owner-U...@uug.org]Im Auftrag
von tommy
Gesendet: Mittwoch, 19. Marz 2003 08:26
An: UNIF...@uug.org
Betreff: [UNIFACE-L:2810] RE: -150 USING OBJECT SERVICE
Dose any one know if any impact when using "USYS$ORA_PARAMS=dpa,oc 800", but in oracle,
open_cursor is 300?
The OS is HP unix 11, oracle is 817, and the uniface is 7206.
Thank you for your help!
Tommy
-----Original Message-----
From: owner-U...@uug.org [mailto:owner-U...@uug.org]On Behalf Of tommy
Sent: Wednesday, March 19, 2003 3:24 PM
To: UNIF...@uug.org
of course you can get problemes. With every user and database-connect
uniface open a new cursor (in some situation more than one).
So if UNIFACE tries to open more than 300 cursor you will get an error
from the database.
Normally 300 are high enough, so that problem should occur, but if you
are dealing with object-services UNIFACE opens a new-transaction for
the service (I believe, but I am not sure). That can bring you in
trouble.
HTH
THOMAS