We are developing an application in Servoy 4.1.0 - deployment is via web-client.
We are encountering ‘Page Expired’ errors on our non-modal windows.
Our basic application arrangement is to have a main form, where the bulk of the application lives followed by a separate ‘GIS map’ window and a separate ‘inventory’ window.
The GIS map and inventory windows are launched as non-modal dialog windows.
The user ends up with 3 separate browser windows on his desktop. The effect is awesome and the users love it.
The three windows share a foundset on their main forms - as the user navigates through records on the main form the two other non-modal windows follow suit. Again, the effect is exactly what we were after and the users love it ![:D]( "Very Happy")
However, we are experiencing situations where one of the non-modal windows will occassionally fail and show a ‘Page Expired’ message. We’ve tried to isolate what set of circumstances leads to this condition but have been unable to formulate anything solid, thusfar.
Has anyone else encountered such a condition?
Does anyone have any theories as to why this is happening ?
Hi,
Any errors in the log when this happens?
I think the best would be to create a case for this in our support system, with the solution + a description how to reproduce it, as this most likely is some race condition.
I know it might be difficult to get to the steps to reproduce it, but my experience so far is that issues like this, in the end, can always be made reproducible. It just might be a lot of work to figure out the exact steps to do so.
Regards,
Paul
There are no errors in the logs ![:?]( "Confused")
We’ve been trying to find a sequence of events that always results in the ‘Page Expired’ problem but we have not been able to detect any pattern.
I can say the there are 3 windows involved… the ‘main’ window and 2 non-modal dialogs. We have all 3 windows up at the same time and will be doing something as simple as navigating from one record to the next on the ‘main’ window and, all of a sudden, one of the 2 non-modal windows will clear and display ‘Page Expired’.
I can have the app up for as little as 1 minute and the problem will happen or I can be running along for 10 minutes before the problem happens.
It really has us puzzled because there are no log messages and the ajax debugger (for developer) doesn’t help either because as soon as the ‘Page Expired’ event happens that window’s debugger mini-window is lost as well.
We are getting very close to wanting to deploy to production but can’t with these Page Expired issues constantly dogging us.
Any ideas on where we need to start to track this down?
I think it’s best to create a case in our support system with the solution + some description how to reproduce it (or whatever you do to get to the point where it fails).
Paul