October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4057) ClusteredCacheConfigurationTest.testQueueFlushIntervalMemcached random failures

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4057?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4057: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClusteredCacheConfigurationTest.testQueueFlushIntervalMemcached random failures > ------------------------------------------------------------------------------- > > Key: ISPN-4057 > URL: https://issues.jboss.org/browse/ISPN-4057 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 7.0.0.CR1 > > > This code will always fail (lines 109-110): > {noformat} > assertNotNull(mc1.get("k2")); > assertNull(mc1.get("k2")); > {noformat} > However, this code path is not hit often, so the failures are quite rare. > I think the second line should be {{assertNull(mc2.get("k2"));}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4754) Module dependency to Hibernate Search should use slot version 5.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4754?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4754: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Module dependency to Hibernate Search should use slot version 5.0 > ----------------------------------------------------------------- > > Key: ISPN-4754 > URL: https://issues.jboss.org/browse/ISPN-4754 > Project: Infinispan > Issue Type: Task > Components: Build process > Affects Versions: 7.0.0.Beta2 > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Blocker > Fix For: 7.0.0.CR1 > > > As discussed on the mailing list: > http://lists.jboss.org/pipermail/infinispan-dev/2014-September/015390.html > as we otherwise get a duplicate version of hibernate-search-engine on the classpath when people intend to use Infinispan modules to store Search indexes generated by an Hibernate Search "normal" distribution. > Also integration tests of Infinispan should download and use the Hibernate Search distribution of its modules for WildFly, rather than bundling custom ones. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4789) Avoid having two OSGi containers running at the same time.

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4789?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4789: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR1 Resolution: Done > Avoid having two OSGi containers running at the same time. > ---------------------------------------------------------- > > Key: ISPN-4789 > URL: https://issues.jboss.org/browse/ISPN-4789 > Project: Infinispan > Issue Type: Task > Affects Versions: 7.0.0.Beta2 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.CR1 > > > Combining PerSuite and PerClass/PerMethod PAX EXAM reactors results in two containers running at the same time which could trigger resource conflicts similar to the one below: > {noformat} > karaf@root> Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]" java.lang.RuntimeException: > Port already in use: 44444; > You may have started two containers. If you need to start a second container or the default ports are already in use update the config file etc/org.apache.karaf.management.cfg and change the Registry Port and Server Port to unused ports > at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:244) > {noformat} > To avoid this issue split the OSGi tests into two groups with separate Surefire executions - one with the container reused and one with the container started for each class/method. > Related to an earlier workaround: ISPN-4487 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4788) Remove pax-url-mvn dependency

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4788?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4788: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR1 Resolution: Done > Remove pax-url-mvn dependency > ----------------------------- > > Key: ISPN-4788 > URL: https://issues.jboss.org/browse/ISPN-4788 > Project: Infinispan > Issue Type: Task > Affects Versions: 7.0.0.Beta2 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.CR1 > > > Remove the dependency on pax-url-mvn as it's been replaced by pax-url-aether. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4785) Upgrade PAX URL to 2.2.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4785?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4785: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR1 Resolution: Done > Upgrade PAX URL to 2.2.0 > ------------------------ > > Key: ISPN-4785 > URL: https://issues.jboss.org/browse/ISPN-4785 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 7.0.0.Beta2 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4786) Upgrade PAX EXAM to 4.2.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4786?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4786: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR1 Resolution: Done > Upgrade PAX EXAM to 4.2.0 > ------------------------- > > Key: ISPN-4786 > URL: https://issues.jboss.org/browse/ISPN-4786 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 7.0.0.Beta2 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4782) Server should use FORK instead of a Mux block

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4782?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4782: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Server should use FORK instead of a Mux block > --------------------------------------------- > > Key: ISPN-4782 > URL: https://issues.jboss.org/browse/ISPN-4782 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 7.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR1 > > > The server jgroups subsystem uses a MuxChannel to multiplex messages to different consumers on the same channel. > We should use the FORK protocol instead since it has many advantages (i.e. it is what WildFly uses, it doesn't "dirty" the channel). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-4781. ------------------------------------ Fix Version/s: 7.0.0.Final Resolution: Done > 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: 6.0.2.Final, 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > Fix For: 7.0.0.Final > > > 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)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4781: ----------------------------------- Fix Version/s: 7.0.0.CR1 > 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: 6.0.2.Final, 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > Fix For: 7.0.0.CR1, 7.0.0.Final > > > 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)

10 years, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4781?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4781: ----------------------------------- Affects Version/s: 6.0.2.Final > 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: 6.0.2.Final, 7.0.0.Beta2 > Environment: Mac OS X 10.9.4, Oracle HotSpot 1.7.0_67 > Reporter: Duncan Doyle > Assignee: Duncan Doyle > Fix For: 7.0.0.CR1, 7.0.0.Final > > > 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)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2014