viphadke

Results 4 comments of viphadke

Ignite semaphore does not perform well at high concurrency. The API contract of tryAcquire is also violated and the method does not return within the supplied timeout . Ignite 2.16.0

Here is the source package ignitetest; import java.io.IOException; import java.io.Serializable; import java.util.Arrays; import java.util.Collections; import java.util.concurrent.ExecutorService; import java.util.concurrent.Executors; import java.util.concurrent.TimeUnit; import java.util.concurrent.locks.Lock; import javax.cache.Cache; import javax.cache.processor.EntryProcessorException; import javax.cache.processor.MutableEntry; import org.apache.ignite.Ignite;...

Logging framework uses MDC adapter provided by SubstituteServiceProvider even after initialization of CustomServiceProvider

@ceki Thanks for looking into the issue. The issue is a blocker for our release. Do you have any estimate on when the problem can be fixed and released?

Logging framework uses MDC adapter provided by SubstituteServiceProvider even after initialization of CustomServiceProvider

@ceki The fix is not working for use. Let me try to clarify @OmShinde1513 comment. I think this might be very specific to our usage of logback and sl4j. We...

Logging framework uses MDC adapter provided by SubstituteServiceProvider even after initialization of CustomServiceProvider

@ceki Do you have any ETA on a possible solution ?