January 2017 - infinispan-issues - Jboss List Archives

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

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5357?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5357: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > 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.1.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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7407) Investigate flow control performance

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7407: ---------------------------------- Summary: Investigate flow control performance Key: ISPN-7407 URL: https://issues.jboss.org/browse/ISPN-7407 Project: Infinispan Issue Type: Task Components: Core Affects Versions: 9.0.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7228: ------------------------------------------- [~anistor] Yes that's the ultimate cause. Thanks for pushing this one Adrian! > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7406) Update to Hibernate Search 5.6.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7406?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7406: ------------------------------------ Fix Version/s: 9.0.0.CR1 9.0.0.Final > Update to Hibernate Search 5.6.0.Final > -------------------------------------- > > Key: ISPN-7406 > URL: https://issues.jboss.org/browse/ISPN-7406 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR1, 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7406) Update to Hibernate Search 5.6.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7406?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7406: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4807 > Update to Hibernate Search 5.6.0.Final > -------------------------------------- > > Key: ISPN-7406 > URL: https://issues.jboss.org/browse/ISPN-7406 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7406) Update to Hibernate Search 5.6.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7406?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7406: ------------------------------------ Status: Open (was: New) > Update to Hibernate Search 5.6.0.Final > -------------------------------------- > > Key: ISPN-7406 > URL: https://issues.jboss.org/browse/ISPN-7406 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7406) Update to Hibernate Search 5.6.0.Final

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-7406: --------------------------------------- Summary: Update to Hibernate Search 5.6.0.Final Key: ISPN-7406 URL: https://issues.jboss.org/browse/ISPN-7406 Project: Infinispan Issue Type: Component Upgrade Components: Embedded Querying Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7381) PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks'

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7381?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7381: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks' > -------------------------------------------------------------------------- > > Key: ISPN-7381 > URL: https://issues.jboss.org/browse/ISPN-7381 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 9.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Pedro Ruivo > Fix For: 9.0.0.CR1 > > > This can be observed on {{AffinityTopologyChangeTest}}: > {noformat} > 09:49:44,566 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [82] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)09:49:44,794 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [111] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7381) PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks'

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7381?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7381: ------------------------------------ Fix Version/s: 9.0.0.CR1 > PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks' > -------------------------------------------------------------------------- > > Key: ISPN-7381 > URL: https://issues.jboss.org/browse/ISPN-7381 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 9.0.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Pedro Ruivo > Fix For: 9.0.0.CR1 > > > This can be observed on {{AffinityTopologyChangeTest}}: > {noformat} > 09:49:44,566 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [82] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)09:49:44,794 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [111] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7405) DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7405?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-7405: ------------------------------------- [~pruivo] [~dan.berindei] Rings any bells? > DMR operation register-proto-schemas fails with NPE if the proto file has syntax errors > --------------------------------------------------------------------------------------- > > Key: ISPN-7405 > URL: https://issues.jboss.org/browse/ISPN-7405 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying, Server > Affects Versions: 9.0.0.Beta2 > Reporter: Adrian Nistor > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: error.log > > > Start an infinispan server and run the following CLI command: > ./bin/ispn-cli.sh -c '/subsystem=datagrid-infinispan/cache-container=local:register-proto-schemas(file-names=[myFileWithSyntaxErrors.proto], file-contents=[kaboom])' > since the file has syntax errors it should still be placed in the ___protobuf_metadata cache and a myFileWithSyntaxErrors.proto.errors key should also be created. No exception should be thrown. Currently no key is written in cache and the NPE from the attached log happens. > When registering a proper file without syntax errors this works correctly. > The problem disappears if I disable global state persistence, so the cachestore seems to play a role in this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017