I have been having an intermittent problem with my RB program. I get an Waiting on RBServer message that is on the notification bar in Firefox and a connecting message and the corresponding rotating, loading circle in the tab. According to my IT professional, when this even occurs, RB is using 57% of the cpu cycles on the server. He is not a happy camper.
This seems to happen when we use sqlite commands, but it is very random. Some times it happens once a week to 3 or 4 times a day. We are at a low usage period due to construction with only 40 to 60 transactions a day. This intermittent problem was not happening when we were doing 100 to 150 transactions a day. I do not believe I have modified the program in any manner since before this problem has developed.
I've run into this in the past. First check the size of rb. As you know there is a memory leak, and it could be getting toooo big. Only way I know how to fix it is to kill rb and restart it.
Second.. There are a few problems with SQLite. Usually some strange reason. Too bad RB does not support a real DB manager. I've had problems where a sqLITE command will sit there forever. I try the same command in mySQL or other DB's and they always work fine. Years ago it was stated that it would be added.?
I just ran into a problem with a Ancestry system. The person file had two parents - parent1 and parent2. To find the children of a parents here is a cut down version of the SQL command. SELECT * FROM person as parent LEFT JOIN person as child ON parent.personNum IN (child.parent1,child.parent2) It ran forever.. Changed the command to do this: SELECT * FROM person as parent LEFT JOIN person as child ON parent.personNum = (child.parent1+child.parent2) AND parent.personNum IN (child.parent1,child.parent2) This worked.. Why - I dunno. You'd expect it to run slowar!!
Has anyone ever found a fix for the memory usage problem. If you have a lot of action on a system that uses the RUN command, eventually you run out of memory. Stopping RB and restarting it, seems to be the only fix. It's a huge problem and has bugged me for years. I've delayed development of applications, because they cannot be place in operation with the problem.
I have several apps waiting for the fix.. Any information about this?