Highlighted
Visitor.
923 views

Multiple Execution Threads with Thinclient and "not responding state"

Perhaps it is better to open a new discussion on the "not responding state".

Situation:

"main-program" (Menue)

          Call Thread "program-1"       (window 1 with user-action)

          Call Thread "program-2"      (window 2 with user-action)

In a normal environment, I can start processing in "program-1" and switch to the "program-2" window or the "main-program" menu window during processing with no problems and limitations.

In the Thinclient environment, it is no longer possible to switch to another window if a processing routine is running in the current window. If the mouse is clicked into another program window, the program falls into the "not responding state" until the processing in "program-1" is finished.

If a progress dialog (for example w$progressdialog) is used, the window of "program-1" will expand to the entire screen and will be reset to the old size only after the end of the processing. The User see the "not responding state" and cannot do any other action in this application.

If processing takes more time, the server runtime detects no more a client activity unless you use the "w$progressdialog" routine.

For me, it looks like the AcuToWeb extension has affected multithreading in general.

Can this be influenced by any configuration settings?

All Components are Version 10.1.

0 Likes
6 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Multiple Execution Threads with Thinclient and "not responding state"

Do your call thread statements use LINK TO THREAD or BIND TO THREAD syntax?
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Multiple Execution Threads with Thinclient and "not responding state"

Another Acu customer provided this on the subject of threads: add accept is-there-a-key-pressed from input status to the background process . Look for the DMiller comment on community.microfocus.com/.../thread
0 Likes
Highlighted
Visitor.

RE: Multiple Execution Threads with Thinclient and "not responding state"

oh, I need some time to read through.

But our application uses Treads for many years and everything works fine. It still works in a none Thinclient environment it also has formerly worked with Thinclient. We have this problem since Version 10.
0 Likes
Highlighted
Visitor.

RE: Multiple Execution Threads with Thinclient and "not responding state"

supplement:

LINK TO THREAD
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Multiple Execution Threads with Thinclient and "not responding state"

If you are (and have been using paged grids and or paged list boxes) you might try setting ECN-3671 to TRUE in your runtime config file. See if that helps.
0 Likes
Highlighted
Visitor.

RE: Multiple Execution Threads with Thinclient and "not responding state"

Update:

It looks like it is a general problem when switching threads.
I just made some tests without thinclient. In this case you also cannot switch a thread when an elaborate processing routine is running in a thread.
Different values in SWITCH_PERIOD; DISPLAY_SWITCH_PERIOD or IO_SWITCH_PERIOD have no effect.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.