> But I cannot track it down to a special case, since this only
> occurs in our servlets an I have no way to debug them in production.

Most likely that's one of the bugs that have been fixed in 1.5.

> What can I do to track this down?

Try accessing single JDBC connection from single thread.

Roman