Hello folks :-)
I have a roo-based enterprise application, with an underlying database, which I have reverse engineered (with the help of roo of course). One of the data base tables (lets name it tableA) contains several hundred of thousands of records :-) Another table (tableB) which is in relationship with tableA has only 5 recors. While accessing tableB, the response lasts much too long resulting in other "parts" of my application to fail, since they depend on the database response (though they run asynchronously).
I have tried to solve the problem by using Hibernate lazy-fetching mechanism. To do that I changed the code of the TableB_RooDB_Managed.aj in this way:
@OneToMany(mappedBy = "tableb", fetch = FetchType.LAZY)
private Set<TableA> Tableb.tableas;
I also have increased the maximum memory reserved for the JVM. The problem has been partly solved, since a response from the database is returned sometime. But since it lasts too long the other parts of my application dismiss (give up probably to an internal timeout, which is not set by me).
Further details may hel ypu to help me :
- Roo-version: 1.1.0.RELEASE
- mysql-version: 5.1.24
Any (efficient) help would be more than appreciated :-)