10:27 a.m.
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:45 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Owen Tran commented on ISPN-670:
--------------------------------
Needs to be able to pass the 1st test of a mortal entry that should be evicted to bring
the size back down to 128.
public void testEvictionMaxEntries() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >
cache.size());
}
public void testExpirationMaxIdle() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
configuration.setExpirationMaxIdle(100);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertEquals(0, cache.size());
}
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:06 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Owen Tran edited comment on ISPN-670 at 9/24/10 5:06 PM:
---------------------------------------------------------
Needs to be able to pass the 1st test of a mortal entry that should be evicted to bring
the size back down to 128.
public void testEvictionMaxEntries() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >=
cache.size());
}
public void testExpirationMaxIdle() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
configuration.setExpirationMaxIdle(100);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertEquals(0, cache.size());
}
was (Author: owentran):
Needs to be able to pass the 1st test of a mortal entry that should be evicted to
bring the size back down to 128.
public void testEvictionMaxEntries() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >
cache.size());
}
public void testExpirationMaxIdle() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
configuration.setExpirationMaxIdle(100);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertEquals(0, cache.size());
}
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Owen Tran edited comment on ISPN-670 at 9/24/10 5:15 PM:
---------------------------------------------------------
public void testEvictionMaxEntries() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES); // makes entry mortal
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >=
cache.size());
}
public void testExpirationMaxIdle() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
configuration.setExpirationMaxIdle(2000);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1)); // immortal
entry with maxIdle
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >=
cache.size());
}
was (Author: owentran):
Needs to be able to pass the 1st test of a mortal entry that should be evicted to
bring the size back down to 128.
public void testEvictionMaxEntries() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertTrue("cache size too big: " + cache.size(), maxEntries >=
cache.size());
}
public void testExpirationMaxIdle() throws Exception {
int maxEntries = 128;
Configuration configuration = new Configuration();
configuration.setEvictionStrategy(EvictionStrategy.LIRS);
configuration.setEvictionThreadPolicy(EvictionThreadPolicy.PIGGYBACK);
configuration.setEvictionWakeUpInterval(100);
configuration.setEvictionMaxEntries(maxEntries);
configuration.setExpirationMaxIdle(100);
EmbeddedCacheManager manager = new DefaultCacheManager(configuration);
Cache<String, String> cache = manager.getCache();
for (int i = 0; i < 256; i++) {
cache.put("key-" + (i + 1), "value-" + (i + 1), 1,
TimeUnit.MINUTES);
}
Thread.sleep(1000); // sleep long enough to allow the thread to wake-up
assertEquals(0, cache.size());
}
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic updated ISPN-670:
-------------------------------------
Fix Version/s: 4.2.0.BETA1
4.2.0.Final
5.0.0.BETA1
5.0.0.Final
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic commented on ISPN-670:
------------------------------------------
Updated http://community.jboss.org/wiki/Eviction
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:54 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic commented on ISPN-670:
------------------------------------------
Updated http://community.jboss.org/wiki/Eviction
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic updated ISPN-670:
-------------------------------------
Comment: was deleted
(was: Updated http://community.jboss.org/wiki/Eviction)
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:56 p.m.
New subject: [JBoss JIRA] Resolved: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Vladimir Blagojevic resolved ISPN-670.
--------------------------------------
Resolution: Done
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:59 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://jira.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.sys...
]
Mircea Markus updated ISPN-670:
-------------------------------
Fix Version/s: 4.2.0.ALPHA3
(was: 4.2.0.BETA1)
Affects Version/s: (was: 4.2.0.ALPHA2)
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://jira.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.ALPHA3, 4.2.0.Final, 5.0.0.BETA1, 5.0.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:01 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-670) Consider all entries from data container as eviction candidates
[
https://issues.jboss.org/browse/ISPN-670?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-670:
----------------------------------
Fix Version/s: (was: 5.0.0.BETA1)
(was: 5.0.0.Final)
Consider all entries from data container as eviction candidates
---------------------------------------------------------------
Key: ISPN-670
URL: https://issues.jboss.org/browse/ISPN-670
Project: Infinispan
Issue Type: Bug
Components: Eviction
Affects Versions: 4.1.0.Final
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 4.2.0.ALPHA3, 4.2.0.Final
There was a subtle change of eviction semantics starting with 4.1 where only immortal
entries are considered as eviction candidates. By default all entries are immortal, that
is, their expiration and lifespan are -1. As soon as mortal entries are used (expiration
!=-1 || lifespan !=-1) they are not subject to eviction policies and container size can
grow above limit specified in maxEntries.
This policy is confusing and it does not make a lot of sense. All candidates, both mortal
and immortal should be considered as eviction candidates and as such subject to eviction.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5120
days inactive
5203
days old
infinispan-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Galder Zamarreño (JIRA) -
Mircea Markus (JIRA)
-
Owen Tran (JIRA)
-
Vladimir Blagojevic (JIRA)