The fact that you only see this on one job is pretty clearly evidence that
we are seeing a hang of some kind due something a specific connector or
connection is doing.
I'm going to have to guess wildly here to focus us on a productive path.
What I want to rule out is a case where the connector
Actually, I have several jobs, but only one job is running at a time,
and currently the error always happens on the same one. The problem is
that I can't access the environment in debug mode, I also can't activate
debug log because I am limited in log size, so the only thing I can do,
is to
The large number of connections can happen but usually that means something
is stuck somewhere and there is a "train wreck" of other locks getting
backed up.
If this is completely repeatable then I think we have an opportunity to
figure out why this is happening. One thing that is clear is that
