June 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4426) Transaction replayed but not committed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4426?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4426: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1111644 > Transaction replayed but not committed > -------------------------------------- > > Key: ISPN-4426 > URL: https://issues.jboss.org/browse/ISPN-4426 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: State Transfer > Affects Versions: 7.0.0.Alpha4 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > > Dist TX cache, node C is joining. In previous topology, entry is owned by A (primary) and B (backup). In new topology, primary ownership is transferred to C, B stays backup. > 1. TX is prepared in old topology and is being committed, when topology changes > 2. on C (the new owner), the TX info is received and later even the old entry > 3. C receives the CommitCommand, therefore, it correctly replays the PrepareCommand. > 4. When the entries are about to be committed, in TxInterceptor the transaction is found to be already completed as it has lower TxID. > Result: the transaction is not being executed and stale data stay on the node (with my algortihm it eventually led to complete entry loss). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4426) Transaction replayed but not committed

by Radim Vansa (JIRA)

Radim Vansa created ISPN-4426: --------------------------------- Summary: Transaction replayed but not committed Key: ISPN-4426 URL: https://issues.jboss.org/browse/ISPN-4426 Project: Infinispan Issue Type: Bug Security Level: Public (Everyone can see) Components: State Transfer Affects Versions: 7.0.0.Alpha4 Reporter: Radim Vansa Assignee: Dan Berindei Priority: Critical Dist TX cache, node C is joining. In previous topology, entry is owned by A (primary) and B (backup). In new topology, primary ownership is transferred to C, B stays backup. 1. TX is prepared in old topology and is being committed, when topology changes 2. on C (the new owner), the TX info is received and later even the old entry 3. C receives the CommitCommand, therefore, it correctly replays the PrepareCommand. 4. When the entries are about to be committed, in TxInterceptor the transaction is found to be already completed as it has lower TxID. Result: the transaction is not being executed and stale data stay on the node (with my algortihm it eventually led to complete entry loss). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4112) RHQ library plugin: restart cache -- availability report DOWN but cache running

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4112?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-4112: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2665 > RHQ library plugin: restart cache -- availability report DOWN but cache running > ------------------------------------------------------------------------------- > > Key: ISPN-4112 > URL: https://issues.jboss.org/browse/ISPN-4112 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, reporting and management > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 63gablocker > > When we explicitly call STOP operation on particular cache using RHQ UI, this operation is successfully issued and cache is stopped. > Then, we can issue START operation as well. > Cache is started but RHQ is still not-correctly reporting that cache is DOWN and unavailable. > I will investigate this issue, this is just for proper heads up and for tracking purposes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4112) RHQ library plugin: restart cache -- availability report DOWN but cache running

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4112?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-4112: ------------------------------------- Originally this issue was caused by issues with performance on the availability check, which was fixed by ISPN-4235. However ISPN-4235 also removed the ability for RHQ JMX plugin to report a cache being down if it was stopped. So I added that back in and optimized it for the performant way of doing the lookup, but not doing a wildcard query as it used to. Also I enhanced the RHQ JBoss plugin to also support a cache being DOWN if it is not running, which we never had before. Now they both should operate the same with regards to showing a cache UP or DOWN between plugins. > RHQ library plugin: restart cache -- availability report DOWN but cache running > ------------------------------------------------------------------------------- > > Key: ISPN-4112 > URL: https://issues.jboss.org/browse/ISPN-4112 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, reporting and management > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 63gablocker > > When we explicitly call STOP operation on particular cache using RHQ UI, this operation is successfully issued and cache is stopped. > Then, we can issue START operation as well. > Cache is started but RHQ is still not-correctly reporting that cache is DOWN and unavailable. > I will investigate this issue, this is just for proper heads up and for tracking purposes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4425) Validate format of comparison operands (non-indexed query)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4425?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4425: -------------------------------- Summary: Validate format of comparison operands (non-indexed query) (was: Validate format for comparison operands (non-indexed query)) > Validate format of comparison operands (non-indexed query) > ---------------------------------------------------------- > > Key: ISPN-4425 > URL: https://issues.jboss.org/browse/ISPN-4425 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Alpha5 > > > The operands need to have valid format (eg. number) and a proper parsing exception with a descriptive message needs to be thrown otherwise. Currently we just see a NumberFormatException being thrown from the ObjectPropertyHelper.convertToPropertyType(). > This is not just for numbers, other primitives too. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4425) Validate format for comparison operands (non-indexed query)

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4425: ----------------------------------- Summary: Validate format for comparison operands (non-indexed query) Key: ISPN-4425 URL: https://issues.jboss.org/browse/ISPN-4425 Project: Infinispan Issue Type: Bug Security Level: Public (Everyone can see) Components: Embedded Querying Affects Versions: 7.0.0.Alpha4 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Alpha5 The operands need to have valid format (eg. number) and a proper parsing exception with a descriptive message needs to be thrown otherwise. Currently we just see a NumberFormatException being thrown from the ObjectPropertyHelper.convertToPropertyType(). This is not just for numbers, other primitives too. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4301) Handle storeMetadata=false in JpaStore.process and JpaStore.purge methods

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4301?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4301: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1099156|https://bugzilla.redhat.com/show_bug.cgi?id=1099156] from ON_QA to VERIFIED > Handle storeMetadata=false in JpaStore.process and JpaStore.purge methods > ------------------------------------------------------------------------- > > Key: ISPN-4301 > URL: https://issues.jboss.org/browse/ISPN-4301 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Loaders and Stores > Affects Versions: 7.0.0.Alpha4 > Reporter: Radim Vansa > Assignee: Dan Berindei > Labels: 63gablocker > > Even when storing metadata is disabled, JpaStore tries to fetch them in process (when ran with fetchMetadata=true) and in purge, the code enumerating and removing the metadata is executed even when there can't be any metadata. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4112) RHQ library plugin: restart cache -- availability report DOWN but cache running

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4112?page=com.atlassian.jira.plugin.... ] Work on ISPN-4112 started by William Burns. > RHQ library plugin: restart cache -- availability report DOWN but cache running > ------------------------------------------------------------------------------- > > Key: ISPN-4112 > URL: https://issues.jboss.org/browse/ISPN-4112 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX, reporting and management > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Tomas Sykora > Assignee: William Burns > Labels: 63gablocker > > When we explicitly call STOP operation on particular cache using RHQ UI, this operation is successfully issued and cache is stopped. > Then, we can issue START operation as well. > Cache is started but RHQ is still not-correctly reporting that cache is DOWN and unavailable. > I will investigate this issue, this is just for proper heads up and for tracking purposes. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4382) Introduce a lightweight security as an alternative for the SecurityManager

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4382?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4382: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1109582|https://bugzilla.redhat.com/show_bug.cgi?id=1109582] from ON_QA to ASSIGNED > Introduce a lightweight security as an alternative for the SecurityManager > -------------------------------------------------------------------------- > > Key: ISPN-4382 > URL: https://issues.jboss.org/browse/ISPN-4382 > Project: Infinispan > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Core, Remote Protocols, Security, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Beta1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4424) ReplaceIfUnmodified is broken under concurrent execution

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4424?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4424: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1110647 > ReplaceIfUnmodified is broken under concurrent execution > -------------------------------------------------------- > > Key: ISPN-4424 > URL: https://issues.jboss.org/browse/ISPN-4424 > Project: Infinispan > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Remote Protocols > Affects Versions: 6.0.2.Final, 7.0.0.Alpha4 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final > > > Versioned update with a multi threaded Hot Rod client results in inconsistency. Some replaceWithVersion return true ignoring a version update executed in another thread. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2014