This week's book giveaway is in the Cloud forum.
We're giving away four copies of Terraform in Action and have Scott Winkler on-line!
See this thread for details.
Win a copy of Terraform in Action this week in the Cloud forum!

Jan Krystof

Greenhorn
+ Follow
since Feb 12, 2011
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Jan Krystof

Hello,

firstly, I feel that this group (EJB and other Java EE tech...) is perhaps not the best one for this question..., however I guess that here will be experienced guys which I need. Nevertheless, my topic is related to J2EE isuues so I hope this topic will not be kicked off.

I have war file with NO source codes and I need to debug it. I use Eclipse so I did import the WAR file into my IDE. I was able to place breakpoint into the desired file since the respective `.class` file was automatically decompiled into `.java` file with use of JadClipse plug-in. But However, the breakpoint was not working. Then I decided to use jad.exe to decompile all classes into java source files and put them int src folder. Then I found a lot of erros, since the classes used generics and the jad.exe was not able to deal with type erasure.

Do you have any suggestions how to overcome this problem and be able to debug such project?

thanks

Jan
Hi all,

i also had the same problem: After i updated an entity to new value in SESSION1 and i fetched the same entity afterwards in SESSION2, i got old values. I even checked in my DB after closing SESSION1 that new values are present in my db.

There was one not-nice workaround: when I wanted to read updated data, i opend and commited a transation: session.beginTransaction().commit();

However, in my case the problem was in INNODB settings for mysql database. The default isolation level for INNODB is REPEATABLE READ -- I found it here hibernate forum. The solution is in changing the global transaction isolation level to READ_COMMITTED (2) or SERIALIZABLE (8). Check the java.sql.Connection for these isolation levels.

Put the following in your config.hbm.xml

or


all the best
xhanness

PS: do not forget do flush() before closing the session ;-)
Hi all,

i also had the same problem: After i updated an entity to new value in SESSION1 and i fetched the same entity afterwards in SESSION2, i got old values. I even checked in my DB after closing SESSION1 that new values are present in my db.

There was one not-nice workaround: when I wanted to read updated data, i opend and commited a transation: session.beginTransaction().commit();

However, in my case the problem was in INNODB settings for mysql database. The default isolation level for INNODB is REPEATABLE READ -- I found it here hibernate forum. The solution is in changing the global transaction isolation level to READ_COMMITTED (2) or SERIALIZABLE (8). Check the java.sql.Connection for these isolation levels.

Put the following in your config.hbm.xml

or


all the best
xhanness

PS: do not forget do flush() before closing the session ;-)