Regarding my question on twitter about completely disabling the creation of stacktrace.log from a Grails application in production mode, here is my answer: environments { production { log4j = { appenders { null name:’stacktrace’ } } } development { } }environments { production { log4j = { appenders { null name:’stacktrace’ } } } development […]
The last Passenger update brought some good explanation off the problems regarding Passenger and memcache-client (see here). Smart spawning of Passenger processes creates shared file descriptors. As the connections to memcached are sockets they are shared as well so data on them gets corrupted which is explained very nicely in the Passenger documentation: Example 1: […]
Some things are not really different in Rails and Grails world. The pendant to Rails’ respond_to method is Grails withFormat block. Both are supposed to render a different content type as requested according to the accept header and and the format parameter. And both fail to some extend with Internet Explorer 5.5 to 7.0. For […]
if you want something done right, do it yourself If you happen to use the mint tracking tool like me, be careful when migrating from a 32bit to a 64bit server or vice versa. Mint saves ip addresses and a buttload of checksums as signed long values. That bites you right in the ass when […]
I recently switch from a mod_proxy / thin setup to Phusion Passenger and my application started to do the funniest things and the production.log was full with errors related to memcached. It seems, that passengers spawn method “smart” isn’t compatible with memcached. Within seconds on a lightly loaded server the cache gets corrupted big time. […]