Ugh! JDBC drivers that throw Null Pointer exceptions should be dragged by meathooks around the village square. That is a horrible thing that they should never do.
What I would suggest though is since you seem to be saying that you do not get this error in your testing environment is use the same driver in deployment that you use in development/testing. Failing that (as in you can't change the deployment driver) you will need to use the same driver as in deployment in your testing/development environment and see what causes the problem.
I would guess from the stacktrace that somewhere there is a call to clear parameters where not all the parameters have been set. I'm not sure how to work around that in Hibernate. But if you can isolate the issue in your development environment it will go a long ways to helping you solve the problem.
Joined: Oct 27, 2003
well you think thats bad, here is the kicker, both enviornments are same. This problem definetly pushed me a little closer to the edge.
And how do I solve it, I changed the oracle provided jdbc driver and it worked just fine. It took me 2 days for this cause, oracle's download website was down.