Server Smalltalk
Joachim goes through some of the hassles involved in debugging a server issue in Smalltalk (specifically VA, although I think the basic issues are agnostic):
Yesterday I packaged my Seaside Application for the first time on VA Smalltalk 8.5.2 and deployed it to a staging server. And promptly as expected, I got some errors: The first few were easy to find. One of them being a missing rule in AbtXDSingleImagePackagingRule (or some superclass) to include the new EsTimeZone code. That could be fixed by hand. But this morning I spent quite some time searching for a problem in the walkback.log that didn’t exist. And this post is mostly intended for myself to remember next time. But it might also save you some time. The second purpose of this post (or, to be exact, the next one) is to underline why I think the VAST port of Glorp has a lousy adaption of error handling.
There's more, but I have a small word of advice that's made my life easier: don't package images for deployment when going to the server. I run a VW server for this blog, and it's a full dev image, simply running headless. That makes debugging it far, far simpler. I can set up the same image locally, and test things with all the tools available. For that matter, I can set up the same image on a different port on the server, and debug it headful using VNC.
Tags: server smalltalk
