November 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5927) Infinispan calling setRollbackOnly() when detecting write skew

by Stephen Fikes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5927?page=com.atlassian.jira.plugin.... ] Stephen Fikes updated ISPN-5927: -------------------------------- Attachment: testcase.zip Testcase producing a write skew and commit failure > Infinispan calling setRollbackOnly() when detecting write skew > -------------------------------------------------------------- > > Key: ISPN-5927 > URL: https://issues.jboss.org/browse/ISPN-5927 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Stephen Fikes > Attachments: testcase.zip > > > In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates that "invalid state" (of the transaction) is actually the cause of the failed commit. Only when debug logging was enabled could we see the root cause. > h3. {anchor:write-skew}Write skew exception > ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) > ... > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... > h3. {anchor:setRollbackOnly}Set Rollback > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) > at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) > ... > at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) > ... > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5927) Infinispan calling setRollbackOnly() when detecting write skew

by Stephen Fikes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5927?page=com.atlassian.jira.plugin.... ] Stephen Fikes commented on ISPN-5927: ------------------------------------- The actual version is infinispan-core-6.2.1.Final > Infinispan calling setRollbackOnly() when detecting write skew > -------------------------------------------------------------- > > Key: ISPN-5927 > URL: https://issues.jboss.org/browse/ISPN-5927 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Stephen Fikes > > In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates that "invalid state" (of the transaction) is actually the cause of the failed commit. Only when debug logging was enabled could we see the root cause. > h3. {anchor:write-skew}Write skew exception > ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) > ... > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... > h3. {anchor:setRollbackOnly}Set Rollback > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) > at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) > ... > at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) > ... > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5927) Infinispan calling setRollbackOnly() when detecting write skew

by Stephen Fikes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5927?page=com.atlassian.jira.plugin.... ] Stephen Fikes updated ISPN-5927: -------------------------------- Description: In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates that "invalid state" (of the transaction) is actually the cause of the failed commit. Only when debug logging was enabled could we see the root cause. h3. {anchor:write-skew}Write skew exception ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) ... at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... h3. {anchor:setRollbackOnly}Set Rollback at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) ... at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) ... at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... was: In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates the "invalid state" is actually the cause of the failed transaction. h3. {anchor:write-skew}Write skew exception ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) ... at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... h3. {anchor:setRollbackOnly}Set Rollback at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) ... at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) ... at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... > Infinispan calling setRollbackOnly() when detecting write skew > -------------------------------------------------------------- > > Key: ISPN-5927 > URL: https://issues.jboss.org/browse/ISPN-5927 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Stephen Fikes > > In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates that "invalid state" (of the transaction) is actually the cause of the failed commit. Only when debug logging was enabled could we see the root cause. > h3. {anchor:write-skew}Write skew exception > ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) > ... > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... > h3. {anchor:setRollbackOnly}Set Rollback > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) > at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) > ... > at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) > ... > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5927) Infinispan calling setRollbackOnly() when detecting write skew

by Stephen Fikes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5927?page=com.atlassian.jira.plugin.... ] Stephen Fikes updated ISPN-5927: -------------------------------- Description: In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates the "invalid state" is actually the cause of the failed transaction. h3. {anchor:write-skew}Write skew exception ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) ... at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... h3. {anchor:setRollbackOnly}Set Rollback at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) ... at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) ... at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... was: In the context of Java Data Grid, when Infinispan detects write skew [#write-skew] during prepare, it invokes {{setRollbackOnly()}} on the transaction implementation [#set-rollback]. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates the "invalid state" is actually the cause of the failed transaction. h3. {anchor:write-skew}Write skew exception ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) ... at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... h3. {anchor:set-rollback}Set Rollback at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) ... at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) ... at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... > Infinispan calling setRollbackOnly() when detecting write skew > -------------------------------------------------------------- > > Key: ISPN-5927 > URL: https://issues.jboss.org/browse/ISPN-5927 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final > Reporter: Stephen Fikes > > In the context of Java Data Grid, when Infinispan detects [#write-skew] during prepare, it invokes [#setRollbackOnly]() on the transaction implementation. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates the "invalid state" is actually the cause of the failed transaction. > h3. {anchor:write-skew}Write skew exception > ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) > ... > at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... > h3. {anchor:setRollbackOnly}Set Rollback > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) > at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) > ... > at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) > ... > at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) > ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5927) Infinispan calling setRollbackOnly() when detecting write skew

by Stephen Fikes (JIRA)

Stephen Fikes created ISPN-5927: ----------------------------------- Summary: Infinispan calling setRollbackOnly() when detecting write skew Key: ISPN-5927 URL: https://issues.jboss.org/browse/ISPN-5927 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 6.0.2.Final Reporter: Stephen Fikes In the context of Java Data Grid, when Infinispan detects write skew [#write-skew] during prepare, it invokes {{setRollbackOnly()}} on the transaction implementation [#set-rollback]. This results in an exception ({{com.arjuna.ats.jta.exceptions.InvalidTerminationStateException: ARJUNA016064: The transaction is in an invalid state!}}) because this operation is disallowed by Arjuna while in the {{PREPARING}} state. The result is that the causal error ({{org.infinispan.transaction.WriteSkewException}}) is lost and the error that propagates indicates the "invalid state" is actually the cause of the failed transaction. h3. {anchor:write-skew}Write skew exception ... org.infinispan.transaction.WriteSkewException: Write skew detected on key <key> for transaction TransactionImple < ... status: ActionStatus.PREPARING > at org.infinispan.transaction.WriteSkewHelper.performWriteSkewCheckAndReturnNewVersions(WriteSkewHelper.java:53) ... at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:104) at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... h3. {anchor:set-rollback}Set Rollback at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.setRollbackOnly(TransactionImple.java:313) at org.infinispan.interceptors.InvocationContextInterceptor.markTxForRollbackAndRethrow(InvocationContextInterceptor.java:163) ... at org.infinispan.commands.AbstractVisitor.visitPrepareCommand(AbstractVisitor.java:103) ... at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:92) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:213) ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5888) Add bounded container resize to RHQ plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5888?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5888: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 1272490|https://bugzilla.redhat.com/show_bug.cgi?id=1272490] from ON_QA to ASSIGNED > Add bounded container resize to RHQ plugin > ------------------------------------------ > > Key: ISPN-5888 > URL: https://issues.jboss.org/browse/ISPN-5888 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 8.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 8.1.0.Beta1, 8.0.2.Final > > > [~sebastian.laskawiec] added support for resize of data container. We need to allow the server to be changed through the RHQ plugin. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5901) Metrics not registered for local caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5901?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5901: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 1276035|https://bugzilla.redhat.com/show_bug.cgi?id=1276035] from ON_QA to VERIFIED > Metrics not registered for local caches > --------------------------------------- > > Key: ISPN-5901 > URL: https://issues.jboss.org/browse/ISPN-5901 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.0.1.Final, 7.2.5.Final, 8.1.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.1.0.Final, 8.0.2.Final, 7.2.6.Final > > > Common cache metrics are not registered for local caches. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5926) Upgrade to hibernate-search 5.5.1.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5926?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5926: -------------------------------- Status: Open (was: New) > Upgrade to hibernate-search 5.5.1.Final > --------------------------------------- > > Key: ISPN-5926 > URL: https://issues.jboss.org/browse/ISPN-5926 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Beta1, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5926) Upgrade to hibernate-search 5.5.1.Final

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5926: ----------------------------------- Summary: Upgrade to hibernate-search 5.5.1.Final Key: ISPN-5926 URL: https://issues.jboss.org/browse/ISPN-5926 Project: Infinispan Issue Type: Component Upgrade Components: Embedded Querying Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.1.0.Beta1, 8.0.2.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5738) Upgrade to JGroups 3.6.6

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5738?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-5738: ----------------------------------- Assignee: (was: Adrian Nistor) > Upgrade to JGroups 3.6.6 > ------------------------ > > Key: ISPN-5738 > URL: https://issues.jboss.org/browse/ISPN-5738 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process, Core > Reporter: Adrian Nistor > Fix For: 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 November 2015