May 2013 - infinispan-issues - Jboss List Archives

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

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Divya Mehra updated ISPN-3076: ------------------------------ Summary: Infiinispan should enable use of log4j2 (was: Switch log4j --> log4j2 in JGroups) > Infiinispan should enable use of log4j2 > --------------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-3076: -------------------------------- No, I think only 5.3 uses JGroups 3.3. But double-check with the Infinispan folks > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Divya Mehra commented on ISPN-3076: ----------------------------------- Does Infinispan 5.2.5.Final use JGroups 3.3.x? > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Divya Mehra updated ISPN-3076: ------------------------------ Comment: was deleted (was: Is log4j2 used by Infinispan?) > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Divya Mehra edited comment on ISPN-3076 at 5/6/13 10:35 AM: ------------------------------------------------------------ Is log4j2 used by Infinispan? was (Author: dmehra): Is it used by Infinispan? > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Divya Mehra (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Divya Mehra commented on ISPN-3076: ----------------------------------- Is it used by Infinispan? > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-3076?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-3076: -------------------------------- JGroups 3.3.x already supports log4j2: https://issues.jboss.org/browse/JGRP-1585 > Switch log4j --> log4j2 in JGroups > ---------------------------------- > > Key: ISPN-3076 > URL: https://issues.jboss.org/browse/ISPN-3076 > Project: Infinispan > Issue Type: Bug > Components: Querying > Affects Versions: 5.2.5.Final > Environment: Any > Reporter: Divya Mehra > Assignee: Sanne Grinovero > > 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3076) Switch log4j --> log4j2 in JGroups

by Divya Mehra (JIRA)

Divya Mehra created ISPN-3076: --------------------------------- Summary: Switch log4j --> log4j2 in JGroups Key: ISPN-3076 URL: https://issues.jboss.org/browse/ISPN-3076 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.2.5.Final Environment: Any Reporter: Divya Mehra Assignee: Sanne Grinovero 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2974) DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2974?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2974: ------------------------------------- [~anistor] seems like a different issue to me, please open a different issue if this is the case. > DeltaAware based fine-grained replication corrupts cache data, if eviction is enabled > ------------------------------------------------------------------------------------- > > Key: ISPN-2974 > URL: https://issues.jboss.org/browse/ISPN-2974 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.1.Final, 5.2.5.Final, 5.2.6.Final > Reporter: Horia Chiorean > Assignee: Adrian Nistor > Priority: Critical > Labels: 5.2.x > Fix For: 5.2.6.Final, 5.3.0.Beta1 > > > When using a custom {{DeltaAware}} implementation in a cluster with 2 replicated nodes with eviction enabled, data transferred from one node (the writer) to the another (the reader) causes data stored on this node and evicted at the time of the change, to be rewritten with whatever the partial latest delta was. > In more detail: > * configure 2 nodes in replicated mode, with eviction enabled > * consider NodeA the writer and NodeB the reader > * NodeA inserts some data (custom entries) into the cache > * NodeB correctly receives via state transfer the initial data > * NodeA loads & partially updates some information about an entry which was not in the cache - was evicted previously > * NodeB receives the partial delta with the changes from NodeA, but *instead of merging* with whatever is stored in the persistent store, *replaces the entire entry in the cache*, leaving it in effect with "partial/corrupt information" > If eviction is not enabled, everything works as expected. -- 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 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2336) Allow basic per-cache access control on endpoints

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2336?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2336: ---------------------------------- Description: Currently an endpoint exposes all caches within the configured container as read / write. We need the ability to decide which caches to expose and with which access semantics (read-only / read-write) (was: It would be nice to configure endpoints to be read-only. This can be done reasonably easily with REST by disabling certain methods, but a common method would be welcome) > Allow basic per-cache access control on endpoints > ------------------------------------------------- > > Key: ISPN-2336 > URL: https://issues.jboss.org/browse/ISPN-2336 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.Final > > > Currently an endpoint exposes all caches within the configured container as read / write. We need the ability to decide which caches to expose and with which access semantics (read-only / read-write) -- 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 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2013