September 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Duncan Doyle updated ISPN-4781: ------------------------------- Description: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method and does not call the 'init(Cache<K,V> cache)' method of the failure policy. was: The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. > CustomFailurePolicy.init is never called. > ----------------------------------------- > > Key: ISPN-4781 > URL: https://issues.jboss.org/browse/ISPN-4781 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > > The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and my custom XSite failure policy is this never initiated. > It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method and does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Duncan Doyle commented on ISPN-4781: ------------------------------------ Pull request: https://github.com/infinispan/infinispan/pull/2912 > CustomFailurePolicy.init is never called. > ----------------------------------------- > > Key: ISPN-4781 > URL: https://issues.jboss.org/browse/ISPN-4781 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > > The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and by custom XSite failure policy is this never initiated. > It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

Duncan Doyle created ISPN-4781: ---------------------------------- Summary: CustomFailurePolicy.init is never called. Key: ISPN-4781 URL: https://issues.jboss.org/browse/ISPN-4781 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.0.0.Beta2 Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 Reporter: Duncan Doyle Assignee: Dan Berindei The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and by custom XSite failure policy is this never initiated. It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4781) CustomFailurePolicy.init is never called.

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Duncan Doyle reassigned ISPN-4781: ---------------------------------- Assignee: Duncan Doyle (was: Dan Berindei) > CustomFailurePolicy.init is never called. > ----------------------------------------- > > Key: ISPN-4781 > URL: https://issues.jboss.org/browse/ISPN-4781 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > > The CustomFailurePolicy interface provides an "init(Cache<K, V> cache)" method, which, according to the JavaDoc, should be invoked during the initialization phase. The method is however never called and by custom XSite failure policy is this never initiated. > It seems that the BackupSenderImpl class initiates the CustomFailurePolicy in its 'start()' method does not call the 'init(Cache<K,V> cache)' method of the failure policy. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4739) InfinispanQueryIT test fails randomly on RHEL

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4739?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-4739: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2911 > InfinispanQueryIT test fails randomly on RHEL > --------------------------------------------- > > Key: ISPN-4739 > URL: https://issues.jboss.org/browse/ISPN-4739 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Reporter: Vojtech Juranek > Assignee: Gustavo Fernandes > Labels: testsuite_stability > > {{InfinispanQueryIT.testQueryOnSecondNode}} and {{InfinispanQueryIT.testMassIndexerResult}} fails randomly on RHEL (Oracle java 6) with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: expected:<3> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnSecondNode(InfinispanQueryIT.java:110) > {noformat} > resp. ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: expected:<3> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testMassIndexerResult(InfinispanQueryIT.java:145) > {noformat} > and {{InfinispanQueryIT.testSimpleGetOnSecondNode}} with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:621) > at org.junit.Assert.assertNotNull(Assert.java:631) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testSimpleGetOnSecondNode(InfinispanQueryIT.java:95) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Work on ISPN-4780 started by Adrian Nistor. ------------------------------------------- > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-4780: ------------------------------------- Thanks Gustavo! I'll fix this ASAP. > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Sanne Grinovero > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4780: -------------------------------- Status: Open (was: New) > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Sanne Grinovero > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4780) Protostream should not require package name on imports

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4780?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-4780: ----------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Protostream should not require package name on imports > ------------------------------------------------------ > > Key: ISPN-4780 > URL: https://issues.jboss.org/browse/ISPN-4780 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 7.0.0.Beta2 > Reporter: Gustavo Fernandes > Assignee: Adrian Nistor > Fix For: 7.0.0.CR1 > > > {code:title=file1.proto} > package p; > message A { > optional int32 f1 = 1; > } > {code} > {code:title=file2.proto} > package org.infinispan; > import "file1.proto"; > message B { > required p.A ma = 1; > } > {code} > Does not work since protostream uses the package name + file name to resolve imports -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4739) InfinispanQueryIT test fails randomly on RHEL

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-4739?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-4739: ----------------------------------------- Those tests never failed on master JDK7 or JDK8, including RHEL agents: http://ci.infinispan.org/project.html?tab=testDetails&testNameId=39014776... http://ci.infinispan.org/project.html?tab=testDetails&testNameId=-3079146... But they fail 100% of the time on my mac when connecting to a certain wireless hub, with the following error: {code} 2014-09-28 01:11:37,509 WARNING [org.jgroups.protocols.UDP] (default task-2) JGRP000034: thehouse-35243: failure sending message to /228.6.7.8: java.io.IOException: Can't assign requested address {code} Due to the error above, cluster fail to form and all tests pointing to the second node fail. > InfinispanQueryIT test fails randomly on RHEL > --------------------------------------------- > > Key: ISPN-4739 > URL: https://issues.jboss.org/browse/ISPN-4739 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Reporter: Vojtech Juranek > Assignee: Gustavo Fernandes > Labels: testsuite_stability > > {{InfinispanQueryIT.testQueryOnSecondNode}} and {{InfinispanQueryIT.testMassIndexerResult}} fails randomly on RHEL (Oracle java 6) with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: expected:<3> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testQueryOnSecondNode(InfinispanQueryIT.java:110) > {noformat} > resp. ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: expected:<3> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.junit.Assert.assertEquals(Assert.java:542) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testMassIndexerResult(InfinispanQueryIT.java:145) > {noformat} > and {{InfinispanQueryIT.testSimpleGetOnSecondNode}} with ([see details|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FU...]) > {noformat} > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:621) > at org.junit.Assert.assertNotNull(Assert.java:631) > at org.infinispan.test.integration.as.query.InfinispanQueryIT.testSimpleGetOnSecondNode(InfinispanQueryIT.java:95) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014