March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10050) unlock for fqn does not work while two udp packet received

by 俐佳张 (Jira)

俐佳张 created ISPN-10050: --------------------------- Summary: unlock for fqn does not work while two udp packet received Key: ISPN-10050 URL: https://issues.jboss.org/browse/ISPN-10050 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 7.2.5.Final Reporter: 俐佳张 Attachments: t783, t785 when udp packet received twice, two threads try to acquire the lock, lock was acquired successfully twice. But unlock only executed ones. That cause fqn couldn't be released. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Persistence Executor threads should use ProcessorInfo

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10049?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10049: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Persistence Executor threads should use ProcessorInfo > ----------------------------------------------------- > > Key: ISPN-10049 > URL: https://issues.jboss.org/browse/ISPN-10049 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.9.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Persistence Executor threads should use ProcessorInfo

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10049?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10049: ----------------------------------- Summary: Persistence Executor threads should use ProcessorInfo (was: Peristence Executor threads should use ProcessorInfo) > Persistence Executor threads should use ProcessorInfo > ----------------------------------------------------- > > Key: ISPN-10049 > URL: https://issues.jboss.org/browse/ISPN-10049 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.9.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Peristence Executor threads should use ProcessorInfo

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10049?page=com.atlassian.jira.plugin... ] William Burns updated ISPN-10049: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6762, https://github.com/infinispan/infinispan/pull/6763 (was: https://github.com/infinispan/infinispan/pull/6762) > Peristence Executor threads should use ProcessorInfo > ---------------------------------------------------- > > Key: ISPN-10049 > URL: https://issues.jboss.org/browse/ISPN-10049 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.9.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Peristence Executor threads should use ProcessorInfo

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10049?page=com.atlassian.jira.plugin... ] William Burns updated ISPN-10049: --------------------------------- Status: Open (was: New) > Peristence Executor threads should use ProcessorInfo > ---------------------------------------------------- > > Key: ISPN-10049 > URL: https://issues.jboss.org/browse/ISPN-10049 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.9.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Peristence Executor threads should use ProcessorInfo

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10049?page=com.atlassian.jira.plugin... ] William Burns updated ISPN-10049: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6762 > Peristence Executor threads should use ProcessorInfo > ---------------------------------------------------- > > Key: ISPN-10049 > URL: https://issues.jboss.org/browse/ISPN-10049 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.9.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10049) Peristence Executor threads should use ProcessorInfo

by William Burns (Jira)

William Burns created ISPN-10049: ------------------------------------ Summary: Peristence Executor threads should use ProcessorInfo Key: ISPN-10049 URL: https://issues.jboss.org/browse/ISPN-10049 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.4.9.Final Reporter: William Burns Assignee: William Burns Fix For: 10.0.0.Beta3, 9.4.10.Final Due to running in containerized environments, we can't use the normal Runtime#availableProcessors method since it is reported correctly in some cases. We need to convert the usage to ProcessorInfo which takes that into account. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10031) Remove doc regarding expiration not working with state transfer

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10031?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10031: -------------------------------- Fix Version/s: 9.4.10.Final > Remove doc regarding expiration not working with state transfer > --------------------------------------------------------------- > > Key: ISPN-10031 > URL: https://issues.jboss.org/browse/ISPN-10031 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > ISPN-4075 changed it so now expiration times are updated properly when retrieving entries via state transfer. We need to make sure documentation doesn't erroneously talk about this limitation anymore. > One example is http://infinispan.org/docs/dev/user_guide/user_guide.html#expiration_maxi... with the third bullet point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10031) Remove doc regarding expiration not working with state transfer

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10031?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10031: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove doc regarding expiration not working with state transfer > --------------------------------------------------------------- > > Key: ISPN-10031 > URL: https://issues.jboss.org/browse/ISPN-10031 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.10.Final > > > ISPN-4075 changed it so now expiration times are updated properly when retrieving entries via state transfer. We need to make sure documentation doesn't erroneously talk about this limitation anymore. > One example is http://infinispan.org/docs/dev/user_guide/user_guide.html#expiration_maxi... with the third bullet point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10048) Remove Jolokia jars and configuration files

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10048?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10048: -------------------------------- Status: Open (was: New) > Remove Jolokia jars and configuration files > ------------------------------------------- > > Key: ISPN-10048 > URL: https://issues.jboss.org/browse/ISPN-10048 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3 > > > Now that we utilise Prometheus to expose our beans via HTTP, there is no reason to keep the agent-bond jars or associated config. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019