Hi Tim, > This is how a programming forum is supposed to work. People contributing > ideas and sharing experiences. I think we are getting close to nailing down > where 4D engineers need to look to solve this problem. >
I just want to add that one of the main benefits of the Forums (http://forums.4d.com) is that it is also used by the 4D Engineers and they do monitor, read, and participate in the discussions. So posting on the forums could give you the opportunity to discuss this directly with the Engineers. This participation is one of the main reasons why Feature Requests are handled on the forums (as described here: http://kb.4d.com/assetid=76725). > Somebody needs to forward this email chain to 4D engineering. Hopefully Tim > Penner can do this and get 4D engineering motivated to stop waiting for a > demo database that reproduces this problem and have somebody go do a code > review looking for something that doesn’t look quite right. > I wish it were that simple. I see some theories about what's causing it but I don’t think anyone has nailed down a concrete explanation or reproducible test that could be used in a bug report. Sorry, but I cannot file a bug report for something this vague. Although, to be clear, I have tried running some tests to see if I can provoke the issue and I never saw it (so technically if a bug was filed with the information we currently have it could be marked as 'verified and non-reproducible' by tech support). It is great to see confirmation that using the Runtime Explorer allows the DB Admin to issue the command RESUME PROCESS; this gives me hope that we are on the right track and for the time being we have a way of kicking the process back into gear. I will continue monitoring this thread for additional clues but at this time I still don't have enough information to reproduce the issue and ultimately file a bug report. For anyone following along and actively looking for this problem, hopefully you are also using the Information Component to log reports on a regular basis (default 5 minute interval) so that if the issue does arise you have a set of reports that depict the period of uptime for the database. There may be a clue in these reports (for example, an item in the attention section warning you of an issue). At the very least the reports would include the amount of uptime for the computer, which could be used to help understand at which point of uptime this problem is happening (assuming it is related to uptime). -Tim ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
