Hey Drew - We reported the stored procedure frozen issue... it's only happened once so far. We're going to get a procdump from the server the next time it happens.
The record lock issue has only happened twice. From what others have written here, it sounds like it's been an issue for others for a long time, although I haven't ever seen a lock reported for a user not connected to the server. Not too worried about it yet. Many of our users report that v16 is noticeably faster, which is good... and the server is stable using the legacy network layer. -- Jeffrey Kain [email protected] > On Sep 22, 2017, at 3:14 PM, Drew Waddell via 4D_Tech <[email protected]> > wrote: > > We are considering upgrading to 4D v16 fairly soon but have been a little > spooked by two conversations recently, '4D v16.2 false record locks' and > 'Server Process "Frozen"-ish'. Have these issues been reported to 4D? Has > there been any resolution or workaround? ********************************************************************** 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] **********************************************************************
