jacek187 wrote :
| In my opinion TreeCache is yet NOT READY for production use. Probably it
works in simple single-thread applications, but in real situations, with many
concurent threads TreeCache dosen't work correctly...
|
No, more specifically, it IS ready for production use in multi
i have analyzed this problem and this is caused by asynchronus transaction
rollback. More details in thread:
http://www.jboss.com/index.html?module=bbop=viewtopict=118186,
When transaction entry is removed in separate thrad, corresponding
TransactionEntry couldn't be foundm, so
It's hard to analyze the problem if you don't provide the version number you're
using or the code you're running or the configuration.
As for sharing your opinion ... I don't know if it's designed to generate a
helpful response. Do you want to be helped?
View the original post :
