"I had technical oversight of a project related to overnight valuations of the bank's credit derivative products,"
"We needed to know quickly if something did go awry with the process, so we implemented a Log4j plug-in that sent out an email whenever an error was detected, together with all the error details,"
"He duly went through the build and release scripts, decided that the Log4j plug-in had no place in a release system and pulled it, without mentioning this to the rest of the team."
"I logged in but could not see any error messages - because the system had generated two billion SQL error messages."
Nick worked as a contractor at a London investment bank in the late 2000s with technical oversight of overnight valuations for the bank's credit derivative products. The system produced nightly valuations so trading could proceed in the morning. The team implemented a Log4j plug-in to send detailed error emails, rate-limited to one message every ten seconds. A new project manager removed the plug-in during a release without informing the team and also omitted a changed SQL script. The release produced massive SQL errors, generating two billion error messages that swamped the bank's email servers.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]