redlab-log

Last week I was stress testing a webapplication. While putting heavy load to the server, the server went Oom (Out Of Mana… , euh Memory) . That was a quick stress test. The testing task quickly changed into a debugging task.
Finding the leak isn’t an easy task. With just looking at a java.lang.OutOfMemoryError error you wont find it. You’ll need a profiler or a heapdump inspection tool.

I decided to go for the profiler. A year ago I tried the netbeans internal profiler, that was a very nice profiler but it’s a pain to import projects into NB that don’t follow it’s standards. So this time, no NetBeans.
Continue reading ‘Memory Profiling On Applications’ »

Currently writing code for URLyBird.

A hotelroom booking agent that

• A. requires a new rmi-based server ( server: concurrent! but should also be capable of running in non networked mode) that uses a database with an interface that MUST follow and reads from a custom databasefileformat.
• B. requires a swing client to let the phonemonkeys (multiple: concurrent!) book hotel rooms on certain day without booking the same room at the same time (recordlocking) or booking twice

Sounds simple this way. But it’s a lot of work. Encountering problems with things I’ve never used before. A learning path, yes it is.
Do remind myself to multiply estimated development time by 2.5 next time…

But URLyBird let us swear an ode not to leak any implementation details so I can’t tell more.

Sorry

sun certified java developer

Recently update the list of my frequently used firefox plugins on old-post.
Although some might not work (yet) at the moment of writing with Firefox 3.5

The pirate party of Sweden conquered one seat in the European parliament