Bug Fixes (single zmq context, timeout in database connection)

Simultaneous access to a row when writing and reading will cause an exception. This allows the proces to wait until it's available and then write instead.
No. This is part of it. We were creating and destroying contexts for each connection. A context should live as long as the app is running so it wouldn't necessarily cause errors, but it was slowing stuff down having to do all that overhead unnecessarily. I'm still working on a fix for the other issue.