-
1. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
fungrim Feb 14, 2008 10:27 AM (in response to fungrim)The title was truncated, but it went on to say that this is an issue in 2.1.0.CR3 as well.
-
2. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
fredrikj Mar 7, 2008 9:18 AM (in response to fungrim)I just experienced what might be the same problem.
I started up 6 nodes and one node was using up all CPU without any real load on it. Dumping all stacks shows that all threads are parked except one which is stuck on map.get in OrderedSynchronizationHandler."ReceivingGameEventDaemon-1" prio=1 tid=0x092d5eb0 nid=0x5660 runnable [0x85421000..0x85421f30] at java.util.HashMap.get(HashMap.java:346) at org.jboss.cache.interceptors.OrderedSynchronizationHandler.getInstance(OrderedSynchronizationHandler.java:50) at org.jboss.cache.interceptors.TxInterceptor.registerHandler(TxInterceptor.java:901) at org.jboss.cache.interceptors.TxInterceptor.registerTransaction(TxInterceptor.java:877) at org.jboss.cache.interceptors.TxInterceptor.attachGlobalTransaction(TxInterceptor.java:342) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:292) at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:81) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76) at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
-
3. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
manik Mar 7, 2008 11:19 AM (in response to fungrim)As with all problems of this nature, this is pretty hard to reproduce and I haven't been successful at it, but I can see how it is a problem, both in being not thread safe as well as a static context variable potentially shared across cache instances in the same VM.
In general, the whole use of statics here is pretty ugly - I have changed this in HEAD so if you guys have the time, I'd appreciate your giving it a try in HEAD.
The change is simple and should be very low risk - OSH has no static variables anymore; instead it is instantiated when a TransactionEntry is created and the ref is stored in and obtained from the TransactionEntry, rather than the factory method on OSH. -
5. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
fungrim Mar 10, 2008 11:36 AM (in response to fungrim)Brilliant. Thanks for the attention. I'll see if I'll have time later this week to give head a swirl.
-
6. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
manik Mar 12, 2008 9:11 AM (in response to fungrim)Thank you for spotting and reporting this - helps us build a better product. :-)
-
7. Same issue in 1.4.1 SP5
metastaz Aug 11, 2008 10:51 AM (in response to fungrim)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. -
8. Re: Same issue in 1.4.1 SP5
metastaz Aug 18, 2008 11:04 AM (in response to fungrim)Hi,
Does anybody know anything with regards to the questions above?
Thank you,
Stas. -
9. Re: Concurrency issue in OrderedSynchronizationHandler (2.0.
manik Aug 20, 2008 7:02 AM (in response to fungrim)There are no plans to fix this in 1.x. The latest stable in 2.x is pretty stable, although I'd look at http://wiki.jboss.org/wiki/JBossCacheAsCompatibility about using it with AS 4.x.