January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6121?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6121: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3963 > query-dsl server module must list jboss-logging dependency > ---------------------------------------------------------- > > Key: ISPN-6121 > URL: https://issues.jboss.org/browse/ISPN-6121 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6121?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6121: -------------------------------- Status: Open (was: New) > query-dsl server module must list jboss-logging dependency > ---------------------------------------------------------- > > Key: ISPN-6121 > URL: https://issues.jboss.org/browse/ISPN-6121 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6121: ----------------------------------- Summary: query-dsl server module must list jboss-logging dependency Key: ISPN-6121 URL: https://issues.jboss.org/browse/ISPN-6121 Project: Infinispan Issue Type: Bug Components: Server Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 8.2.0.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6093) When infinispan-remote and infinispan-embedded are deployed together we get an error

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6093?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6093: -------------------------------------- Status: Open (was: New) > When infinispan-remote and infinispan-embedded are deployed together we get an error > ------------------------------------------------------------------------------------ > > Key: ISPN-6093 > URL: https://issues.jboss.org/browse/ISPN-6093 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > {code} > Exception in thread "main" java.lang.NoSuchMethodError: org.infinispan.commons.logging.BasicLogFactory.getLog(Ljava/lang/Class;)Lorg/jboss/logging/BasicLogger; > at org.infinispan.client.hotrod.impl.operations.PingOperation.<clinit>(PingOperation.java:25) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.ping(TransportObjectFactory.java:51) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:45) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) > at infinispan.org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.pingServersIgnoreException(TcpTransportFactory.java:177) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:148) > at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:579) > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:380) > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:387) > at org.infinispan.data.RemoteWordCount.main(RemoteWordCount.java:25) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} > The main cause is that in embedded BasicLogger is relocated whereas in remote it's not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6093) When infinispan-remote and infinispan-embedded are deployed together we get an error

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6093?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6093: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3825 > When infinispan-remote and infinispan-embedded are deployed together we get an error > ------------------------------------------------------------------------------------ > > Key: ISPN-6093 > URL: https://issues.jboss.org/browse/ISPN-6093 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > > {code} > Exception in thread "main" java.lang.NoSuchMethodError: org.infinispan.commons.logging.BasicLogFactory.getLog(Ljava/lang/Class;)Lorg/jboss/logging/BasicLogger; > at org.infinispan.client.hotrod.impl.operations.PingOperation.<clinit>(PingOperation.java:25) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.ping(TransportObjectFactory.java:51) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:45) > at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:16) > at infinispan.org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.pingServersIgnoreException(TcpTransportFactory.java:177) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.start(TcpTransportFactory.java:148) > at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:579) > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:380) > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:387) > at org.infinispan.data.RemoteWordCount.main(RemoteWordCount.java:25) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144) > {code} > The main cause is that in embedded BasicLogger is relocated whereas in remote it's not. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5414) Support (named) parameters in DSL based queries

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5414?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5414: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/3629, https://github.com/infinispan/infinispan/pull/3963 (was: https://github.com/infinispan/infinispan/pull/3629) > Support (named) parameters in DSL based queries > ----------------------------------------------- > > Key: ISPN-5414 > URL: https://issues.jboss.org/browse/ISPN-5414 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5357) Hot Rod protocol 3.0

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5357?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5357: ---------------------------------------- Couple of ideas: * Header and body lengths: With async clients such as Node-based clients, it could be possible that the buffer with the data might contain incomplete data. To help coding of such clients, it'd be good to have both a header size and data size baked into the messages, so that the client can know if the entire header can be read, and once that's read, whether all the data can be read. This would make it much easier to figure out if data has to be buffered compared to current approach which requires at each element read, whether that element has been read completely. * Aeron protocol for ideas: Aeron sends/receives messages and it's [protocol|https://github.com/real-logic/Aeron/wiki/Protocol-Specification] has some interesting ideas in how to layer it. Although the message sizes are bigger, the protocol has been designed with the design principles of SBE, see [here|https://github.com/real-logic/simple-binary-encoding/wiki/Design-Pri...]. > Hot Rod protocol 3.0 > -------------------- > > Key: ISPN-5357 > URL: https://issues.jboss.org/browse/ISPN-5357 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Final > > > *UPDATE (6/10/2015)*: Hot Rod 3.0 could become a HTTP REST protocol taking advantage of existing infrastructure to deal with HTTP requests efficiently, and if it was based on HTTP 2.0, we could have binary data inside of it. Performance should be on par. Text mode could be available for debug or demos. This essentially would mean REST and Hot Rod would merge into one. > A binary protocol rethink is needed to take better advantage of CPUs and buffering. This is based on the ideas of Martin Thompson's Simple Binary Encoding [blog post|http://mechanical-sympathy.blogspot.cz/2014/05/simple-binary-encoding.html] > In essence, we need to move Hot Rod protocol towards having mostly fixed size fields, hence getting rid of `vInt` and `vLong` formats which although safe some bytes, they hinder long stream reading patterns. > An optional part here would be whether to consider using SBE directly, but this JIRA should be mostly oriented at making sure we have a protocol that can be read fast and efficiently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6120?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-6120: ------------------------------ Description: Clusters tab -> cluster -> actions -> stop When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. was: Clusters tab -> cluster -> actions -> stop Pop up should show warning, saying that caches without configured cache store will loose data. > Management console - there should be a warning about possible data loss when stopping the cluster > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6120 > URL: https://issues.jboss.org/browse/ISPN-6120 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Clusters tab -> cluster -> actions -> stop > When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6102) Include the test name in the test thread names

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-6102?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-6102: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Include the test name in the test thread names > ---------------------------------------------- > > Key: ISPN-6102 > URL: https://issues.jboss.org/browse/ISPN-6102 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 8.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.2.0.Beta1 > > > Some random failures are much easier to reproduce when running the entire core test suite, which runs 15 tests in paralle, than when running a single test by itself. In such cases, it helps if we can filter the log messages that belong to the failing test, and the easiest way to do that is to include the test name in the thread name. > Essentially, this means replacing {{ExecutorService}} instances with {{AbstractInfinispanTest.fork()}}, and where not possible instantiating the executor with {{AbstractInfinispanTest.getTestThreadFactory()}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Roman Macor (JIRA)

Roman Macor created ISPN-6120: --------------------------------- Summary: Management console - there should be a warning about possible data loss when stopping the cluster Key: ISPN-6120 URL: https://issues.jboss.org/browse/ISPN-6120 Project: Infinispan Issue Type: Bug Components: Console Reporter: Roman Macor Assignee: Vladimir Blagojevic Clusters tab -> cluster -> actions -> stop Pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016