While wondering why our FM solution routinely goes down every few
days/everyday, I copied it over to my test FM15 (Mac OS Server). I
can semi-reliable cause my solution to crash the server by using the
record selector on a layout which is linked to a 600 record shadow
table. I randomly select a few various records and then I get the
dreaded SDOD - "Sort dialog of death". In my attempts to debug this, I
dragged everything off the layout and removed any triggers. I seem to
get it to crash when I browser some records, pause for about 2 or 3
minutes. Then when I try to go to the next record, then SDOD pops up.
When I eventually get the redundant SDODs I watch the TopCallStats.log
(see attached) to see the repeating list of queries. I have to force
quit FM Pro client but the ODBC Query lines still continue, however it
replaces my name with an id number. This goes on and on and on even
without anyone connected to the server.
At this point I can use Admin Console to close the file. Amazingly, the
ODBC Queries are still happening. There is no hosted file anymore. I
have to restart FM Server to get them to stop.
On my FM 14 production system (also Mac OS Server), I normally can't
cleanly close the file because I suspect too many hung processes are
going on from all the different users. If just one person gets the
SDOD, then everyone (all windows FM Pro v14.0.5) will be hung up and
it's there's no remedy other than to reboot the Mac server.
See attached. Any insight?