Has anyone else seen Perspective cpu spikes/crashes that seem to be caused by flood limit trips that cause clock drifts?
I have a bunch of perspective screens that just call up named queries, nothing really special a few filters and some WHERE IN’s. Opening them in a session seems to start a cascade of flood trips that turn to clock drifts and crash the gateway.
Are you sure it has anything to do with the queries? The flood limit should only be tripped when there’s a cycle in your bindings.
The flood trip only show properties with named query bindings. I removed any refresh binding scripts so I don’t think a loop could be anywhere.
Do your queries include properties whose values are then updated with the result of a query? Even indirectly? That would be a cycle.
lwood Do you remember the fix for this issue?
I have seen this happen with some ways of doing bindings on datepickers to populate a control. You have to check your date bindings to make sure they can't get into a circular reference.