-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GridCacheStore operations are not eligible to join JTA transaction with write-behind disabled #69
Comments
Can we move this discussion to StackOverflow? Please provide the code and configuration. You can use http://pastebin.com/ to paste code or logs. |
Relevant code and config at: http://pastebin.com/jzvZyi11 |
I have responded on StackOverflow. Any reason you are not using GridGain Hibernate L2 Cache integration here? |
I have responded on SO. Regardless of whether or not I use the GridGain L2 cache implementation it doesn't address the issue I've brought up here with JTA and GridCacheStore. |
Just one more question. Do you have more than one data source? If yes, can you tell us what they are? |
Yes, I have a MysqlXADataSource for JTA in REPEATABLE_READ and a BoneCPDataSource for reporting in READ_UNCOMMITTED |
JPA uses MysqlXADataSource |
We have reproduced the issue and are fixing it. I will update this issue with GridGain version that will contain the fix. |
Awesome. Thanks. |
From testing I have found that by the time the methods in my GridCacheStore implementation are invoked by GridGain the JTA TX is already in the COMMITTING state thus changes made through my cache store (JPA operations w/ Hibernate) fail to actually commit to the database. For reference I am using GridGain 6.1.6 with Spring 4.0.5 and Hibernate 4.3.5 (JPA 2.1). TX Manager is Narayana (JBoss) 5.0.2 using JTA 1.2. I have a debug log I'd be happy to share but github won't allow me to upload a text file. Here's the relevant part:
The text was updated successfully, but these errors were encountered: