A few months later, it's our turn, our development team is suddenly facing the same understandable behavior from a production code which was running smoothly until today.
From time to time we are thrown the same exception
[ ORA-17412: Bigger type length than Maximum ] on simple jdbc calls like getString() and getINt(). No EJB is involved, plain POJO using Oracle thin jdbc driver.
Anybody has a clue ?
It looks like I found a track to follow:
thos exceptions we had yesterday were followed by other 'Operation interrupted' exceptions.
It looks like this entry:
and the reply was:
The operation interrupted means the transaction timeout interrupted the thread.
Looks like your Oracle8 driver doesn't handle this very well.
What it should do is close the connection rolling back the db transaction.
Your underlying problem sounds like a deadlock to me.
After further investigation it looks like the connection was indeed interrupted, but not by a time out but by a socket write error.
So all of these above might just come from an unstable/unreliable network ?!!?