[CONJ-407] Connection.setTransactionIsolation lost on MaxAllowedPacketException Created: 2017-01-06 Updated: 2017-01-12 Resolved: 2017-01-12 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | 1.5.6 |
| Fix Version/s: | 1.5.7 |
| Type: | Bug | Priority: | Major |
| Reporter: | Matthias Pretzer | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
| Description |
|
Transaction isolation level set via Connection#setTransactionIsolation is lost, Although the connection is still usable, it silently switches back to the default isolation behaviour, Testcase:
Javadoc on Connection#setTransactionIsolation reads (excerpt):
Clearly, this does not hold in this situation. |
| Comments |
| Comment by Matthias Pretzer [ 2017-01-07 ] | ||||||||||||||
|
The following patch fixes the test case by ensuring non-default isolation levels are applied again upon reconnecting.
I did run mvn test locally and there were no differences in the outcome (severel tests failed and several skipped, I assume because of my environment). | ||||||||||||||
| Comment by Diego Dupin [ 2017-01-09 ] | ||||||||||||||
|
right, failover will have the same issue. |