-
1. Re: Is this really fixed ?https://issues.jboss.org/browse/ISPN-1274
dceashish Feb 19, 2013 8:00 AM (in response to dceashish)Can someone pls answer this. This is critical for my application performance. I'll have to put my own fix if this is not working with latest infinispan.
-
2. Re: Is this really fixed ?https://issues.jboss.org/browse/ISPN-1274
dan.berindei Feb 20, 2013 8:18 PM (in response to dceashish)Yes, this is fixed. DefaultExecutorService doesn't use a WithinThreadExecutor since 5.2.0.Beta4.
You can still pass in any Executor implementation you want to the constructor, but the Javadoc advises you against using a WithinThreadExecutor.
-
3. Re: Is this really fixed ?https://issues.jboss.org/browse/ISPN-1274
dceashish Feb 20, 2013 10:52 PM (in response to dan.berindei)Thanks a lot Dan. That has solved my problem. I was on 5.1.6.Final and since this issue was marked as fixed in 5.1.0, I thought it would automatically start working as desired. As of know, I have found the API from where I can pass my own ExecutorService and I can continue to use 5.1.6 with this change.
-
4. Re: Is this really fixed ?https://issues.jboss.org/browse/ISPN-1274
dan.berindei Mar 1, 2013 3:19 AM (in response to dceashish)Ok, sorry for the confusion with the version numbers.
You're right, the initial fix only allowed you to use a different executor. The default actually changed in 5.2.0.Beta4, with the fix for ISPN-2443.