The web server process is very sensitive to any bugs. We ran into the exact 
problem you are having. Our web team was suddenly very unpopular with the other 
developers. Any bug and the whole app would crash.

We no longer run any code on the web server process on 4D server. Instead we 
run a client application that acts as a web server. This works pretty well.

The code that gets traced is the code on the machine that handled the request. 
So if you make the request to your web server client application it will trace 
there. The web server on client can run on the same physical server as your 4D 
server so long as they aren't both handling requests on the same port.

The biggest hurdle we had was getting the correct 4D licensing. There was a 
special license to make the client run the web server. This may be made more 
difficult because we are an OEM.

Joshua Hunter
[email protected]
(425)673-1974
www.dwdev.com
Dataworks Development, Inc.
Providing secure and configurable data management solutions for research and 
clinical labs since 1987.


-----Original Message-----
From: 4D_Tech [mailto:[email protected]] On Behalf Of Sannyasin 
Siddhanathaswami via 4D_Tech
Sent: Thursday, April 6, 2017 2:14 PM
To: 4D iNug Tech
Cc: Sannyasin Siddhanathaswami
Subject: 4D Server Crashes When Tracing Buggy Web Connection Code

Aloha,

If I trace On Web Connection code on 4D Server v15.3 Mac, and I goof and 
reference an out of index array (I know I’m the first to ever do that), our 
server crashes. It just quits to the Finder, no error message nothing. I view 
the trace via screen sharing to the server machine.

This is disastrous when other people are using 4D!!

Have others run into this? What’s the best way to debug On Web Connection code 
without crashing the server?

Maybe starting the webserver on 4D client? But how does adding a “Trace" On Web 
Connection code work? Won’t it still trace on the 4D Server?

Sannyasin Siddhanathaswami
**********************************************************************
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]
**********************************************************************
**********************************************************************
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]
**********************************************************************

Reply via email to