When the Resource disconnects the SessionPool at a very specific time -
when the slot connected to SessioPool's connectDone() disconnects the
SessionPool we end up in an inconsistent state since the SessionPool
then proceeds to insert the session into the unusedPool, which
triggers an assert later as no sessions are allowed in internal pools
when SessionPool is offline.