I have discovered strange functionality in a specific scenario, not sure if it will qualify as a bug.
If two H2 servers are clustered, running version 1.3.163 and a client connects using version 1.3.155 things appear to work fine, unless the client calls Connection.setTransactionIsolation with TRANSACTION_READ_COMMITTED. In this case the client experiences an epic stack-overflow exception. I've noticed this behavior with many versions of H2 now, as long as the client is using an older version than the cluster servers. I'm attempting to attach a test-case to reveal this issue. Simply build Cluster.java and Client.java, and then run them with different versions of H2 on their classpath. For example, in one terminal run: javac -cp h2-1.3.161.jar:. Cluster.java java -cp h2-1.3.161.jar:. Cluster ...and in another terminal run: javac -cp h2-1.3.155.jar:. Client.java java -cp h2-1.3.155.jar:. Client -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
Client.java
Description: Binary data
Cluster.java
Description: Binary data
