When Web Services go Bad
Some people might consider this a failure
I like to think of it as having successfully discovered the 32,768th way to not make a light bulb.
If I've piqued your interest, click the image for details. Make special note of the processor load on the bottom right, and the remaining HDD space on the bottom left.
On a (somewhat) related note: I think I am now as much a fan of VirtualBox as Bill is of iSeries. I may not fully grok all the details of virtualization, but this event was corrected by 2 mouse clicks (Machine | Reset). If this had been running on a "real" (non-virtual) box, it would have required physically cycling the power -which is a tad difficult when the machine is not in the same physical location as you are.
On another (somewhat) related note: please allow me to reiterate the importance of remembering the difference between a LotusScript Integer (a signed 2-byte integer with an inclusive range of -32,768 to 32,767), and a Java int (a signed 4-byte integer with an inclusive range of -2,147,483,648 to 2,147,483,647 ). If you're not careful, this difference can allow a WebService to sneak up and bitch-slap your server. Expecting thirty two THOUSAND and getting two BILLION does tend to muck things up.
-Devin
The Pridelands
Chris Byrne
Show n' Tell Thursdays
Maddox
