Hi,
Does anybody know anything with regards to the questions above?
Thank you,
Stas.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171071#4171071
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171071
Hi,
We observe same issue in 1.4.1 SP5. Are there any plans on getting it fixed in
1.x code base?
If not how safe is it to use latest stable 2.x release with 4.2.x JBoss AS?
Thank you,
Stas.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169892#4169892
Repl
"[EMAIL PROTECTED]" wrote : It looks like the current WL holder and the RL
requestor are not the same:
|
|
| | ... could not be acquired by :162303 ...
| |
|
| and
|
|
| | ... Write lock owner: Thread[ReportDataTaskRunner-20521017-1,5,jboss]
...
| |
|
|
"genman" wrote : What's the write thread doing? (Can you get a stack trace of
your application at this time?)
Meanwhile, any other ideas?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062531#4062531
Reply to the post :
http://www.jboss.com/index.html?modul
"genman" wrote : What's the write thread doing? (Can you get a stack trace of
your application at this time?)
Yep that's a good idea. However I do not have exact steps to reproduce this
issue, and we observe it only ocassionaly in production. I'll try to reproduce
it and get the stack trace.
T
Hi all,
we have JBoss 4.0.2 , JBossCache 1.2.2 and Hibernate 3.1.
Isolation level = repeatable read
Ocasionay we observe a following in logs:
1) thread x starts a transaction and obtains a write lock on resource A
2) ~30 mins go by
3) transaction in thread x fails to obtain a _read_ lock on res
