Have you gotten an answer on this? I just got the same error today and do not know what it is.
Unfortunately I haven't found solution for this occurrence. But I suppose using explicit connection to database isn't the best decision for business processes. Therefore it was replaced in our case with some kind of process utilizing adobe jdbc service.