Database updates not impacted |
ygu |
2013-09-05 03:20:18 |
Hi,
I'm using Access_JDBC40.jar. I'm facing seemingly a database cache issue when reading from database. Here is the case:
An EJB starts a transaction, updates a row in database then a flush is processed and the transaction is commited. The code used for this is as follows:
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public void changeValue1(final Long id) {
//following line is equivalent to entityManager.find(id)
final myEntity entityToUpdate = entityDAO.read(id);//
entityToUpdate .setValue1(false);
//following line is equivalent to
// entityManager.update(entityToUpdate)
entityDAO.update(entityToUpdate );
//following line is equivalent to entityManger.flush()
entityDAO.flush();
}
Then another bean retrieves "entityToUpdate" from database however the returned object doesn't have the previous modification.
This issue is not reproduced when using other databases.
|
Re:Database updates not impacted |
HXTT Support |
2013-09-05 05:46:47 |
>Then another bean retrieves "entityToUpdate" from database however the returned object doesn't have the previous modification.
Whether two beans is running in different Java Virtual machine? If so, you should use lockType=ACCESS connection property to let both of them to see each other.
|
Re:Re:Database updates not impacted |
ygu |
2013-09-05 07:27:53 |
Thank you for your response.
The two beans are running in the same JVM.
|
Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-05 07:41:44 |
>Then another bean retrieves "entityToUpdate" from database however the
>returned object doesn't have the previous modification.
>The two beans are running in the same JVM.
Then two beans should belong to different connections, and the prior opening bean failed is using an older snapshot?
Of couse, maybe you are using an older verson?
2013-08-02 fixed a cache bug for In subqueryTable expression which subqueryTable contains parameter since 2013-02-25.
2013-06-07 fixed an index cache content refresh bug for refreshInterval parameter since 2013-04-02.
|
Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-07 05:05:32 |
I have downloaded and used the latest access driver from my download area. Nevertheless, the issue still persist. are there any flags to disable caching, force read of the latest commited value ...
|
Re:Re:Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-07 05:07:58 |
Please email us your test sample.
|
Re:Re:Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-07 05:16:36 |
This is part of a large product, I may not be able to send you parts of the code for confidentiality reasons.
My previous question was how do we disable caching and how to set the isolation level on the HXTT driver to read commited.
Regards
|
Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-07 07:31:59 |
Are you using hibernate or other EJB environment?
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-08 11:56:30 |
Yes, we are using Hibernate and EJB env.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-09 04:15:57 |
We really need a technical solution to our issue above. without that, the HxTT access driver we have bought from you is useless for us.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-09 06:36:40 |
Please download the latest version. Your issue should happen when two differenct connections is using, and the prior conection has opened one table, then the following connection udpated the same table, but the prior connection has still seen the older cached row.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-10 01:18:11 |
I am already using the latest drivers.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-10 02:25:43 |
You should redownload it because it has been updated yesterday.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
Tarik Guelzim |
2013-09-11 03:39:16 |
This is the latest version I see in my download area. It dates back to august and it is the one I am using.
Access JDBC 4.0 Package for JDK 1.6.X, and JDK1.7.X ( 2,836Kb )(2013-08-09 05:04)
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
HXTT Support |
2013-09-11 04:25:22 |
Checked. Updated now.
|
Re:Re:Re:Re:Re:Re:Re:Re:Database updates not impacted |
ygu |
2013-10-08 02:38:44 |
Hi,
Using the parameter delayedClose=0 solved the problem.
Thanks
|