August 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (HRJS-35) Enable clients to pass in String or native JSON objects

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño commented on HRJS-35: -------------------------------------- A few subtasks can be identified here: * Make client support HR protocol 2.8 as is, without any further changes. * Support latest 9.4 server. Then eventually add the ability to automatically switch between String or native JSON representation. > Enable clients to pass in String or native JSON objects > ------------------------------------------------------- > > Key: HRJS-35 > URL: https://issues.jboss.org/browse/HRJS-35 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Galder Zamarreño > > Implement Hot Rod protocol changes to enable JS client to read data from Hot Rod in a particular MIME type, e.g. JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-35) Enable clients to pass in String or native JSON objects

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño reassigned HRJS-35: ------------------------------------ Assignee: Galder Zamarreño > Enable clients to pass in String or native JSON objects > ------------------------------------------------------- > > Key: HRJS-35 > URL: https://issues.jboss.org/browse/HRJS-35 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.6.0 > > > Implement Hot Rod protocol changes to enable JS client to read data from Hot Rod in a particular MIME type, e.g. JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-35) Enable clients to pass in String or native JSON objects

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-35: --------------------------------- Status: Open (was: New) > Enable clients to pass in String or native JSON objects > ------------------------------------------------------- > > Key: HRJS-35 > URL: https://issues.jboss.org/browse/HRJS-35 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.6.0 > > > Implement Hot Rod protocol changes to enable JS client to read data from Hot Rod in a particular MIME type, e.g. JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-35) Enable clients to pass in String or native JSON objects

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-35?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-35: --------------------------------- Summary: Enable clients to pass in String or native JSON objects (was: Implement transcoding Hot Rod changes) > Enable clients to pass in String or native JSON objects > ------------------------------------------------------- > > Key: HRJS-35 > URL: https://issues.jboss.org/browse/HRJS-35 > Project: Infinispan Javascript client > Issue Type: Enhancement > Reporter: Galder Zamarreño > > Implement Hot Rod protocol changes to enable JS client to read data from Hot Rod in a particular MIME type, e.g. JSON. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9423) HotRodDecoder should identify what is HotRod operation

by Diego Lovison (JIRA)

Diego Lovison created ISPN-9423: ----------------------------------- Summary: HotRodDecoder should identify what is HotRod operation Key: ISPN-9423 URL: https://issues.jboss.org/browse/ISPN-9423 Project: Infinispan Issue Type: Task Reporter: Diego Lovison Priority: Minor During a failover test, it will be good if we know what operation the server will execute. For example, the client will call a PrepareTransactionOperation (HotRodConstants.PREPARE_TX_2_REQUEST), on the server side, what method will be called? There is no "easy way" to know what is the method. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-66) Fix Jsdoc generation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-66?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-66: --------------------------------- Status: Open (was: New) > Fix Jsdoc generation > -------------------- > > Key: HRJS-66 > URL: https://issues.jboss.org/browse/HRJS-66 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.5.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.6.0 > > > * Add jsdoc to devDependencies > * Fix jsdoc generation (currently fails) > * Add jsdoc generation check to PR CI checks. > * Publish jsdoc for 0.5.0 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-66) Fix Jsdoc generation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-66?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-66: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/js-client/pull/26 > Fix Jsdoc generation > -------------------- > > Key: HRJS-66 > URL: https://issues.jboss.org/browse/HRJS-66 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.5.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.6.0 > > > * Add jsdoc to devDependencies > * Fix jsdoc generation (currently fails) > * Add jsdoc generation check to PR CI checks. > * Publish jsdoc for 0.5.0 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9422) Remove infinispan.server.*.workerThreads properties

by Radim Vansa (JIRA)

Radim Vansa created ISPN-9422: --------------------------------- Summary: Remove infinispan.server.*.workerThreads properties Key: ISPN-9422 URL: https://issues.jboss.org/browse/ISPN-9422 Project: Infinispan Issue Type: Sub-task Components: Server Affects Versions: 9.4.0.Final Reporter: Radim Vansa Assignee: Tristan Tarrant Fix For: 10.0.0.Final These properties are not documented ATM. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7168) Prevent user from configuring passivation with a shared store

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7168?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7168. -------------------------------- Resolution: Done > Prevent user from configuring passivation with a shared store > ------------------------------------------------------------- > > Key: ISPN-7168 > URL: https://issues.jboss.org/browse/ISPN-7168 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.4.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Final > > > Passivation only makes sense with a non shared cache store. --The problem is that if an entry is passivated on a shared cache store only the first node will be able to activate the entry and subsequent nodes will always see null.-- > Looking closer the bigger issue is if an entry becomes passivated and then subsequently written to you will have a different value in the store as you would in memory. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-59) Under heavy load of servers and javascript client ERROR messages about timeouts can starve resources in limited environments (kubernetes/openshift)

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-59?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño commented on HRJS-59: -------------------------------------- [~rafaeska], we've just released version 0.5.0 of the Node.js client which improves hangling in heavy load conditions. Can you try that version and see if it works better? > Under heavy load of servers and javascript client ERROR messages about timeouts can starve resources in limited environments (kubernetes/openshift) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HRJS-59 > URL: https://issues.jboss.org/browse/HRJS-59 > Project: Infinispan Javascript client > Issue Type: Enhancement > Affects Versions: 0.4.0 > Environment: Node 8.6.0 in a container inside Openshift with limits of 1000 millicores and 1000MB of memory > Infinispan 'Chakra' 8.4.0.Final-redhat-3 running in 2 pods running image registry.access.redhat.com/jboss-datagrid-7/datagrid71-openshift/images/1... with limits of 1000 millicores and 1000MB of memory > Reporter: Rafa Eska > > During charge tests Infinispan undersizes server end denegating service, and Javascript Hotrod client consume all Node.js pod resources emitting this:{{ > {code:java} > [31m[2018-05-10 12:38:24.956] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.957] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.957] [ERROR] decoder -[39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > jdg error org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.958] [ERROR] decoder -[39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) > [31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) > [31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses > [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) > {code} > }} > Shouldn't it be WARNINGS? Or control in any way number of emitted messages? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 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 August 2018