If I use the synchronous events API, database disconnect errors are thrown by the
eventManager.waitForEvent() method; what's the expected result if I switch to using the
asynchronous API instead?

I'm specifically looking to support auto-reconnect; I use jaybird's connection-string options for
this for my tomcat resource (?autoReconnect=true), but I don't think it'll accept those same
options via eventManager.setDatabase(), so I need to actually trap database disconnect errors, and
attempt to reconnect and re-register my interest in events.

Thoughts? Thanks!

-Philip