Version 0.0.7 of Schwatcher has been released.
- No longer has external logging library dependencies. Thanks crdueck for the suggestion.
- No longer uses any mutable members for extra thread-safety
Version 0.0.4 of Schwatcher has been released.
Version 0.0.3 of Schwatcher upgrades the Akka library used by the plugin to 2.2.1 so that devs already using Akka 2.2.x are able to use this library.
Those upgrading to 0.0.3 of Schwatcher who aren’t already using Akka 2.2.x should read the 2.1.x to 2.2.x Akka migration guide to make sure their projects don’t break.
For the most part, I’m a very happy Heroku user. The platform allows me deploy my apps, be they Java, Scala or Ruby-based without having to think/worry about infrastructure, which is amazing. They also allow me to, for the most part, do this for free. For the most part, I love it, and so do many others. That said, sometimes you do run into problems that cause you to lose lots of time debugging … in the wrong direction.
Yesterday, after adding non-blocking I/O to my Metascraper library, I load tested my deployed application and found it fatally crashing with
java.lang.OutOfMemoryError: unable to create new native thread errors. Not Good
Sorry for the quick version-up. Version 0.1.1 added non-blocking I/O, but was using Dispatch without configuring the threadpool used for HTTP connections. This caused issues on Heroku where there is a 256 combined thread + process limit for 1x dynos (512 for 2x dynos), whereby Java OOM “unable to create new native thread” errors would be thrown.