...it *is* the 21st century you know. This...
I failed to use Rational's own tools (Purify in this case) and I had a memory leak in my application server. The solution was to reboot that server, which brought the doorbell back to life.I mean, if you're going to implement your *doorbell* with a network and an application server, at least use some software that doesn't break so easily.
1 comment:
Purify is awfull to use. It's bugged as hell, and it's an outstanding example bad software imho. I used to work on a software ( sorta like an application server ) which, when purified, needed about 24 hours to boot ( 10minutes without ). We figured that was because purify didn't filter any events life, but just wrote down all fucking events to a big list. Needless to say that our purifyed server crashed soon enough because purify consumed all avaiable ram. In any event where the purify traces quite useless, because it generated hundreds of thousends of them, even when filtered afterwards.
Post a Comment