February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3974) Compilation error with JDK8 b128

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3974?page=com.atlassian.jira.plugin.... ] Work on ISPN-3974 started by Galder Zamarreño. > Compilation error with JDK8 b128 > -------------------------------- > > Key: ISPN-3974 > URL: https://issues.jboss.org/browse/ISPN-3974 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha1 > > > {noformat} > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4555,45] error: spliterator() in KeySetView cannot implement spliterator() in Set > return type ConcurrentHashMapSpliterator<K> is not compatible with Spliterator<K> > where K,E are type-variables: > K extends Object declared in class KeySetView > E extends Object declared in interface Set > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4613,45] error: spliterator() in ValuesView cannot implement spliterator() in Collection > return type ConcurrentHashMapSpliterator<V> is not compatible with Spliterator<V> > where V,E are type-variables: > V extends Object declared in class ValuesView > E extends Object declared in interface Collection > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4702,58] error: spliterator() in EntrySetView cannot implement spliterator() in Set > 3 errors > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3974) Compilation error with JDK8 b128

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3974?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-3974: -------------------------------------- Assignee: Galder Zamarreño (was: Dan Berindei) > Compilation error with JDK8 b128 > -------------------------------- > > Key: ISPN-3974 > URL: https://issues.jboss.org/browse/ISPN-3974 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 7.0.0.Alpha1 > > > {noformat} > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4555,45] error: spliterator() in KeySetView cannot implement spliterator() in Set > return type ConcurrentHashMapSpliterator<K> is not compatible with Spliterator<K> > where K,E are type-variables: > K extends Object declared in class KeySetView > E extends Object declared in interface Set > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4613,45] error: spliterator() in ValuesView cannot implement spliterator() in Collection > return type ConcurrentHashMapSpliterator<V> is not compatible with Spliterator<V> > where V,E are type-variables: > V extends Object declared in class ValuesView > E extends Object declared in interface Collection > /mnt/ebs/TeamCity/buildAgent/work/masterjdk7/commons/src/main/java/org/infinispan/commons/util/concurrent/jdk8backported/EquivalentConcurrentHashMapV8.java:[4702,58] error: spliterator() in EntrySetView cannot implement spliterator() in Set > 3 errors > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3978) Upgrading to Infinispan 6.0 on JBoss AS 7.1.1

by Adriano Labate (JIRA)

Adriano Labate created ISPN-3978: ------------------------------------ Summary: Upgrading to Infinispan 6.0 on JBoss AS 7.1.1 Key: ISPN-3978 URL: https://issues.jboss.org/browse/ISPN-3978 Project: Infinispan Issue Type: Component Upgrade Components: Core Affects Versions: 6.0.0.Final Environment: Windows 7 FR, NetBeans 7.4, JBoss AS 7.1.1 Reporter: Adriano Labate Assignee: Dan Berindei Priority: Minor JBoss AS 7.1.1 is bundled with Infinispan 5.1.2.FINAL. On the page http://infinispan.org/download, there's a green button "AS 7 Modules" with description "Packaged modules for deploying in JBoss AS 7". I understand that this AS 7 module is for updating to Infinispan version 6.0. I downloaded and extracted the infinispan-as-modules-6.0.0.Final.zip file in the "\modules" folder. I didn't deleted anything, just copied the archive content into modules. Now when I run my application that uses the cache, I can read in my log file the following: {code} [org.infinispan.factories.GlobalComponentRegistry] ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL {code} So I supposed something is wrong. Either the log file displays the wrong version, or my update operation was not sufficient for updating Infinispan to version 6.0 on AS 7. For information, in my application POM, I added dependency as below: {code:xml} <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-core</artifactId> <version>6.0.0.Final</version> <scope>provided</scope> </dependency> {code} After some basic tests, I can notice that I can query the cache and put data in it, and find data. So it seems to work. But with which version of Infinispan? Could anybody know how to correctly update Infinispan to 6.0? Or why the 5.1.2 version is mentioned in the log file instead of version 6.0? Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3978) Updating to Infinispan 6.0 on JBoss AS 7.1.1

by Adriano Labate (JIRA)

[ https://issues.jboss.org/browse/ISPN-3978?page=com.atlassian.jira.plugin.... ] Adriano Labate updated ISPN-3978: --------------------------------- Summary: Updating to Infinispan 6.0 on JBoss AS 7.1.1 (was: Upgrading to Infinispan 6.0 on JBoss AS 7.1.1) > Updating to Infinispan 6.0 on JBoss AS 7.1.1 > -------------------------------------------- > > Key: ISPN-3978 > URL: https://issues.jboss.org/browse/ISPN-3978 > Project: Infinispan > Issue Type: Component Upgrade > Components: Core > Affects Versions: 6.0.0.Final > Environment: Windows 7 FR, NetBeans 7.4, JBoss AS 7.1.1 > Reporter: Adriano Labate > Assignee: Dan Berindei > Priority: Minor > Labels: infinispan, jboss-as7, update > > JBoss AS 7.1.1 is bundled with Infinispan 5.1.2.FINAL. > On the page http://infinispan.org/download, there's a green button "AS 7 Modules" with description "Packaged modules for deploying in JBoss AS 7". > I understand that this AS 7 module is for updating to Infinispan version 6.0. > I downloaded and extracted the infinispan-as-modules-6.0.0.Final.zip file in the "\modules" folder. I didn't deleted anything, just copied the archive content into modules. > Now when I run my application that uses the cache, I can read in my log file the following: > {code} > [org.infinispan.factories.GlobalComponentRegistry] ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL > {code} > So I supposed something is wrong. > Either the log file displays the wrong version, or my update operation was not sufficient for updating Infinispan to version 6.0 on AS 7. > For information, in my application POM, I added dependency as below: > {code:xml} > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-core</artifactId> > <version>6.0.0.Final</version> > <scope>provided</scope> > </dependency> > {code} > After some basic tests, I can notice that I can query the cache and put data in it, and find data. So it seems to work. But with which version of Infinispan? > Could anybody know how to correctly update Infinispan to 6.0? Or why the 5.1.2 version is mentioned in the log file instead of version 6.0? > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3971) Make it possible to deploy protostream in OSGI (Karaf)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3971?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3971: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/protostream/pull/1 > Make it possible to deploy protostream in OSGI (Karaf) > ------------------------------------------------------ > > Key: ISPN-3971 > URL: https://issues.jboss.org/browse/ISPN-3971 > Project: Infinispan > Issue Type: Feature Request > Reporter: Martin Gencur > Assignee: Martin Gencur > > When deploying protostream into Karaf (OSGi), the following error is thrown: > Error executing command: Jar is not a bundle, no Bundle-SymbolicName mvn:org.infinispan.protostream/protostream/1.0.0.CR1 > Affects version 1.0.0.CR1 of protostream. > The goal is to make this library deployable to Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3971) Make it possible to deploy protostream in OSGI (Karaf)

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3971?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3971: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in protostream master. Thanks! > Make it possible to deploy protostream in OSGI (Karaf) > ------------------------------------------------------ > > Key: ISPN-3971 > URL: https://issues.jboss.org/browse/ISPN-3971 > Project: Infinispan > Issue Type: Feature Request > Reporter: Martin Gencur > Assignee: Martin Gencur > > When deploying protostream into Karaf (OSGi), the following error is thrown: > Error executing command: Jar is not a bundle, no Bundle-SymbolicName mvn:org.infinispan.protostream/protostream/1.0.0.CR1 > Affects version 1.0.0.CR1 of protostream. > The goal is to make this library deployable to Karaf. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-3942: ------------------------------ Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/2377 (was: https://github.com/infinispan/infinispan/pull/2369, https://github.com/infinispan/infinispan/pull/2370) PR for master > HotRod client keep trying recover a connection to a cluster member after shutdown > --------------------------------------------------------------------------------- > > Key: ISPN-3942 > URL: https://issues.jboss.org/browse/ISPN-3942 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Infinispan server with HotRod client in server-client mode and replicated caches. > Reporter: Wolf-Dieter Fink > Assignee: Pedro Ruivo > Priority: Critical > Labels: clustered, hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > Attachments: hotrod-client.log > > > If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. > There is only a replicated cache configured. > From the server-logfile the new cluster view is established > 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] > There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. > This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3977) Tx caches raise created event on every put if the entry is not local

by William Burns (JIRA)

William Burns created ISPN-3977: ----------------------------------- Summary: Tx caches raise created event on every put if the entry is not local Key: ISPN-3977 URL: https://issues.jboss.org/browse/ISPN-3977 Project: Infinispan Issue Type: Bug Components: Listeners, Transactions Affects Versions: 6.0.1.Final Reporter: William Burns Assignee: Dan Berindei A transactional put originating from a non owner causes a CreatedEventNotification to occur no matter what. The problem lies with the fact that we wrap the entry to provide for repeatable read. We need to only raise the event if it is the owner. Note the DistListenerTest currently verifies this incorrect behavior around line 88. We should also verify that the modified event is not raised from the PutKeyValueCommand from the non owner as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3965) Tests in org.infinispan.server.test.client.hotrod can fail due to NPE

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3965?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3965: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha1 7.0.0.Final Resolution: Done > Tests in org.infinispan.server.test.client.hotrod can fail due to NPE > --------------------------------------------------------------------- > > Key: ISPN-3965 > URL: https://issues.jboss.org/browse/ISPN-3965 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Priority: Minor > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Method {{org.infinispan.server.test.client.hotrod.AbstractRemoteCacheTest#release()}} annotated with {{@AfterClass}} will result in NPE when client tests are run on remote container. It's due to the fact that Arquillian/JUnit runs {{@BeforeClass}} and {{@AfterClass}} locally, not remotely, see e.g. [this thread|https://community.jboss.org/message/731417] for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3976) Protobuf marshalling on Indexed server caches interferes with keySet and bulk marshalling

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3976?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3976: ---------------------------------- Component/s: Remote Querying > Protobuf marshalling on Indexed server caches interferes with keySet and bulk marshalling > ----------------------------------------------------------------------------------------- > > Key: ISPN-3976 > URL: https://issues.jboss.org/browse/ISPN-3976 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 7.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014