Oracle 8.1.7, Windows and Linux clients running JRE 1.2.2_008, RMI server running on Linux or Windows NT with JRE 1.2.2_008.

Pontus Strand

The problem has now been solved. It was caused by a bug in Oracle's thin JDBC client version 8.1.6. So the answers are as follows:

Q1: We use OracleConnectionCacheImpl.getConnection in our connection pool, it obviously keeps a stack of connections or something along those lines. This stack gets empty on occasions.

Q2: This bug seems to be fixed in version 8.1.7, at least we haven't been able to reproduce the problem.

Q3: We still don't know why it worked using JRE 1.3.1 but we think it is because it is faster and we therefore got some extra time before the EmptyStackException occurs and we didn't use enough clients to have any problems.

We probably would have found the reason for this much earlier if we had caught the exception on the server instead of on the client. Oh well, you learn by your mistakes :-)