On Window Transaction trigger not always useful

[iwitschi]

Hi
We experienced problems on windows servers when the OnWindowTransaction trigger and the OnLastWindowClose trigger are enabled together and a lot of server scripting is happening.

The effect was that after some time other server scripts, in the same or other apps, are just not run anymore until we changed the amount of allowed server sessions, or, in the end, disabled the OnWindowTransaction trigger completely.

It looks as if sessions are not closed properly on the server side. It's our experience on two servers with the same app, although we cannot prove it. We don't have possibilities to count sessions on the FMS.
This is for the record. Be careful if you use this feature.
Cheers

[Malcolm]

Sounds nasty. Have you drawn flow charts to map the differences between desired behaviour and current behaviour? You may find a solution there.

[iwitschi]

Thanks for your hint.
I tried already different possibilities and tried to provide a complete description here: Claris Community (English)

There is currently no solution to that, I guess.

[Kirk]

Take a look at this server side script queue as a possible option......

Performance update from 24u and server side script queues

24u is a great resource for lots of FM things and Honza is truly focused on performance. This new blog post on their site has some good info. For those not aware of the “server side script queue” mentioned in the post as an alternative to PSoS execution, it is functionally equivalent to the old school mainframe job scheduler. A script places the name of a script to execute into a new record in a table. A server side script running on short intervals looks for a record in that table and runs a…