December 2015 - infinispan-issues

[JBoss JIRA] (ISPN-5985) Add tests for listeners matching the requirements of ClientEvents.addClientQueryListener

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5985?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5985: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1283182|https://bugzilla.redhat.com/show_bug.cgi?id=1283182] from ON_QA to VERIFIED > Add tests for listeners matching the requirements of ClientEvents.addClientQueryListener > ---------------------------------------------------------------------------------------- > > Key: ISPN-5985 > URL: https://issues.jboss.org/browse/ISPN-5985 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.CR1, 8.1.0.Final, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5934) ContinuousQuery must benefit from DSL based filter indexing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5934?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5934: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1283182|https://bugzilla.redhat.com/show_bug.cgi?id=1283182] from ON_QA to VERIFIED > ContinuousQuery must benefit from DSL based filter indexing > ----------------------------------------------------------- > > Key: ISPN-5934 > URL: https://issues.jboss.org/browse/ISPN-5934 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 8.1.0.Alpha2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.CR1, 8.1.0.Final, 8.0.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5903) Spring package split

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5903?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5903: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1266831|https://bugzilla.redhat.com/show_bug.cgi?id=1266831] from ON_QA to VERIFIED > Spring package split > -------------------- > > Key: ISPN-5903 > URL: https://issues.jboss.org/browse/ISPN-5903 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Into: > * remote > * embedded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5879) XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5879?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5879: ----------------------------------------------- Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1273795|https://bugzilla.redhat.com/show_bug.cgi?id=1273795] from ON_QA to VERIFIED > XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety > --------------------------------------------------------------------------------- > > Key: ISPN-5879 > URL: https://issues.jboss.org/browse/ISPN-5879 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Remote Protocols > Reporter: Matej Čimbora > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 8.1.0.CR1 > > > When reusing a HotRod client with several threads, site can be accidentally switched multiple times by threads invoking TcpTransportFactory.trySwitchCluster. This occurs when the threads attain 'maxRetries' limit at the same time, each of them being able to invoke TcpTransportFactory..updateServers with different 'clusterAddresses' parameter. This can lead to unpredictable result (e.g. switching back to failed cluster, while the other one (backup) is up and running). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4905) Remove standalone mode from the server distribution

by Alan Field (JIRA)

[ https://issues.jboss.org/browse/ISPN-4905?page=com.atlassian.jira.plugin.... ] Alan Field closed ISPN-4905. ---------------------------- Resolution: Won't Fix It's never going away... > Remove standalone mode from the server distribution > --------------------------------------------------- > > Key: ISPN-4905 > URL: https://issues.jboss.org/browse/ISPN-4905 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 7.0.0.CR2 > Reporter: Alan Field > > The server currently contains a standalone and clustered mode. The standalone mode can be used for development, but clustered is usually used in production. Removing standalone mode and using a single clustered node for development would mean that the development and production environments are closer to each other and would remove the need to test and verify the standalone mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5940) Add CDI Remote module to Wildfly modules

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5940?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5940: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1279919|https://bugzilla.redhat.com/show_bug.cgi?id=1279919] from MODIFIED to ON_QA > Add CDI Remote module to Wildfly modules > ---------------------------------------- > > Key: ISPN-5940 > URL: https://issues.jboss.org/browse/ISPN-5940 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Vaclav Dedik > Priority: Minor > Fix For: 8.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5982) Custom audit logger is ignored in server mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5982?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5982: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1284846|https://bugzilla.redhat.com/show_bug.cgi?id=1284846] from MODIFIED to ON_QA > Custom audit logger is ignored in server mode > --------------------------------------------- > > Key: ISPN-5982 > URL: https://issues.jboss.org/browse/ISPN-5982 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 8.1.0.CR1, 8.1.0.Final > > > When custom audit logger is configured for cache container in server mode (e.g. sniplet bellow), it's ignored and default logger is still used > {noformat} > <authorization audit-logger="org.infinispan.server.test.security.log.TestAuditLogger"> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5903) Spring package split

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5903?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5903: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1266831|https://bugzilla.redhat.com/show_bug.cgi?id=1266831] from MODIFIED to ON_QA > Spring package split > -------------------- > > Key: ISPN-5903 > URL: https://issues.jboss.org/browse/ISPN-5903 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Fix For: 8.1.0.Beta1, 8.1.0.Final > > > Into: > * remote > * embedded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5974) Continuous query should support projections

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5974?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5974: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1287398|https://bugzilla.redhat.com/show_bug.cgi?id=1287398] from MODIFIED to ON_QA > Continuous query should support projections > ------------------------------------------- > > Key: ISPN-5974 > URL: https://issues.jboss.org/browse/ISPN-5974 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Final, 8.0.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5927?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5927: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1278991|https://bugzilla.redhat.com/show_bug.cgi?id=1278991] from MODIFIED to ON_QA > 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 > Assignee: Pedro Ruivo > 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)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2015