January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-3076: ----------------------------------- And regarding overengineered async appender: In practice, I've found that async appender is really no cure for trace logging in infinispan, as the logging will be always faster than writing the logs down and eventually we will only synchronize on the writing queue, but the problems with stuck logging during tracing won't go away. Before Xmas I was working on a modified version of async appender that would slow down the system but never pause it for more than few ms, nor make ST unbearably slow. > Infinispan should enable use of log4j2 > -------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.2.5.Final, 6.0.0.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Mircea Markus > > log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing > 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). > Also refer: https://issues.jboss.org/browse/ISPN-2976 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Infinispan should enable use of log4j2

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-3076: ----------------------------------- [~sannegrinovero] Because Infinispan which uses jboss logging as the logging wrapper, by default routes the messages to Log4j? At least, if I type mvn dependency:copy-dependencies in infinispan/core, I get log4j-1.2.16 > Infinispan should enable use of log4j2 > -------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.2.5.Final, 6.0.0.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Mircea Markus > > log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing > 1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar). > Also refer: https://issues.jboss.org/browse/ISPN-2976 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3868) Deadlock in RemoteCache getAsync

by Alexander Furer (JIRA)

Alexander Furer created ISPN-3868: ------------------------------------- Summary: Deadlock in RemoteCache getAsync Key: ISPN-3868 URL: https://issues.jboss.org/browse/ISPN-3868 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 6.0.0.Final Environment: RemoteCahe component of 6.0.0.Final Reporter: Alexander Furer Assignee: Mircea Markus Priority: Critical Here is the implementation of remoteCahe.getAsync() : public NotifyingFuture<V> getAsync(final K key) { assertRemoteCacheManagerIsStarted(); final NotifyingFutureImpl<V> result = new NotifyingFutureImpl<V>(); Future<V> future = executorService.submit(new Callable<V>() { @Override public V call() throws Exception { V toReturn = get(key); result.notifyFutureCompletion(); return toReturn; } }); result.setExecuting(future); return result; } 2 problems here : 1. Callable's call method might be called BEFORE calling client had a chance to add listener (i.e. getAsync is not returned yet), in this case its' listener futureDone method will never be called. 2. Even case #1 has not happened and notifyFutureCompletion is called on listener, but the future is not resolved yet : "call" has not returned, that's why the future that is passed to listener is not resolved, and calling future.get from listener blocks forever. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3867) L1 cache of ISPN server cannot be enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3867?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3867: ------------------------------------- Also need to update L1 so that L1OnRehash is not enabled by default when L1 is enabled. > L1 cache of ISPN server cannot be enabled > ----------------------------------------- > > Key: ISPN-3867 > URL: https://issues.jboss.org/browse/ISPN-3867 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 6.0.0.Final > Reporter: Martin Gencur > Assignee: William Burns > Priority: Critical > > L1 cache in the server distribution cannot be enabled. The problem is in DistributedCacheAdd:100: > The file should include > builder.clustering().l1().enable().lifespan(lifespan); > instead of > builder.clustering().l1().lifespan(lifespan); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3867) L1 cache of ISPN server cannot be enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3867?page=com.atlassian.jira.plugin.... ] Work on ISPN-3867 started by William Burns. > L1 cache of ISPN server cannot be enabled > ----------------------------------------- > > Key: ISPN-3867 > URL: https://issues.jboss.org/browse/ISPN-3867 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 6.0.0.Final > Reporter: Martin Gencur > Assignee: William Burns > Priority: Critical > > L1 cache in the server distribution cannot be enabled. The problem is in DistributedCacheAdd:100: > The file should include > builder.clustering().l1().enable().lifespan(lifespan); > instead of > builder.clustering().l1().lifespan(lifespan); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3867) L1 cache of ISPN server cannot be enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3867?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-3867: ----------------------------------- Assignee: William Burns (was: Tristan Tarrant) > L1 cache of ISPN server cannot be enabled > ----------------------------------------- > > Key: ISPN-3867 > URL: https://issues.jboss.org/browse/ISPN-3867 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 6.0.0.Final > Reporter: Martin Gencur > Assignee: William Burns > Priority: Critical > > L1 cache in the server distribution cannot be enabled. The problem is in DistributedCacheAdd:100: > The file should include > builder.clustering().l1().enable().lifespan(lifespan); > instead of > builder.clustering().l1().lifespan(lifespan); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3867) L1 cache of ISPN server cannot be enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3867?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3867: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1047860 > L1 cache of ISPN server cannot be enabled > ----------------------------------------- > > Key: ISPN-3867 > URL: https://issues.jboss.org/browse/ISPN-3867 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.3.0.Final, 6.0.0.Final > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Priority: Critical > > L1 cache in the server distribution cannot be enabled. The problem is in DistributedCacheAdd:100: > The file should include > builder.clustering().l1().enable().lifespan(lifespan); > instead of > builder.clustering().l1().lifespan(lifespan); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3867) L1 cache of ISPN server cannot be enabled

by Martin Gencur (JIRA)

Martin Gencur created ISPN-3867: ----------------------------------- Summary: L1 cache of ISPN server cannot be enabled Key: ISPN-3867 URL: https://issues.jboss.org/browse/ISPN-3867 Project: Infinispan Issue Type: Bug Affects Versions: 6.0.0.Final, 5.3.0.Final Reporter: Martin Gencur Assignee: Tristan Tarrant Priority: Critical L1 cache in the server distribution cannot be enabled. The problem is in DistributedCacheAdd:100: The file should include builder.clustering().l1().enable().lifespan(lifespan); instead of builder.clustering().l1().lifespan(lifespan); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2014