Hello,

we have a forms application and would like to run it on a windows 2003
terminal server, but the user experience is very bad. When the user
types the letters appeare on screen slowly.
We have Jinitiator 1.3.1.30 installed.
Does anyone know a solution ?

Thanks
Andreas

Op 28-4-2010 18:09, Andreas Moroder schreef:

Found this (for what it's worth):

The problem is caused by new 2D and 3D functionality in Java 1.3 (which
is used by JInitiator). It was not bugfree at that time in combination
with certain graphical cards and drivers. You can solve this problem by
tuning this functionality off by the next parameter in de JInitiator
console:

-Dsun.java2d.noddraw=true

It works perfect at out company and we don't have issues anymore with
popping-up characters seconds after you type them.


Maybe you should stop using jinitiator at all (the latest forms versions
don't seem to need it anymore)


Shakespeare

Hello,


I tried this months ago but it did not speedup. Maybe It was not exact
this parameter. I will retry.

No. The people that wrote the apps tested them with java without
jinitiator, but some forms triggers don't work.

Bye
Andreas

Op 29-4-2010 11:07, Andreas Moroder schreef:
Thanks for the info. An Oracle consultant told me lately that jinitiator
was not needed anymore, but indeed, I remember from the old days that
forms could behave very differently when used without jinitiator.

The real problem here is roundtrips to the server with every key
pressed. It's like the browser telling the server: "This key was
pressed, what should I do?" and the server replies: "Show the character!"


I vaguely remember a trick to circumvent this, but working with forms is
quite a long time ago for me. I'll try to find it in my long-time-ago
notes.....

Shakespeare

(Somehow brings to mind the song "There's a hole in my bucket, dear
Liza" - http://en.wikipedia.org/wiki/There's_a_Hole_in_My_Bucket )

I'd really appreciate that.

Thanks
Andreas

Op 30-4-2010 13:33, Andreas Moroder schreef:
This is a very old trick, which used to work some years ago (but since
your still on Win2003 it might still work):

"we are using oas 10g and database 10g. we have the same problem with oas on
terminal services. it looks like a problem with jinitiator or java.
refreshing the screen with CTL ALT END or CTL ALT DEL to raise the windows
security screen from the terminal server and pressing ESC. this has to be
done after starting the application. i think this does a screen refresh
and boosts the performance of the oas."

HTH,

Shakespeare