January 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7765) Allow HotRodDecoder to be shared between Netty pipelines

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7765?page=com.atlassian.jira.plugin.... ] Radim Vansa closed ISPN-7765. ----------------------------- Resolution: Rejected > Allow HotRodDecoder to be shared between Netty pipelines > -------------------------------------------------------- > > Key: ISPN-7765 > URL: https://issues.jboss.org/browse/ISPN-7765 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > Currently {{HotRodDecoder}} instance can not be shared between Netty pipelines as {{HotRodEncoder}}. Currently each pipeline creates its own instance by calling: > {code} > server.getDecoder() > {code} > in {{NettyChannelInitializer#initializeChannel}}. We could probably make it a bit more efficient (or limit allocation rate at least) if we allow sharing single instance between pipelines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7765) Allow HotRodDecoder to be shared between Netty pipelines

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7765?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-7765: ----------------------------------- Actually we can't bind the decoder to the channel as each operation carries Hot Rod version, so you might use different decoders on the same channel (however unlikely that is). Anyway, I'll close this. > Allow HotRodDecoder to be shared between Netty pipelines > -------------------------------------------------------- > > Key: ISPN-7765 > URL: https://issues.jboss.org/browse/ISPN-7765 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > Currently {{HotRodDecoder}} instance can not be shared between Netty pipelines as {{HotRodEncoder}}. Currently each pipeline creates its own instance by calling: > {code} > server.getDecoder() > {code} > in {{NettyChannelInitializer#initializeChannel}}. We could probably make it a bit more efficient (or limit allocation rate at least) if we allow sharing single instance between pipelines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8738) InfinispanExtensionIT fails due to xpp3 ModuleLoadException

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8738?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-8738: ---------------------------------- Assignee: Gustavo Fernandes (was: Ryan Emerson) > InfinispanExtensionIT fails due to xpp3 ModuleLoadException > ----------------------------------------------------------- > > Key: ISPN-8738 > URL: https://issues.jboss.org/browse/ISPN-8738 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 9.2.0.CR1 > Reporter: Ryan Emerson > Assignee: Gustavo Fernandes > > ISPN-8427 introduced the XStreamException which depends on xpp3, this is defined as a dependency on the xstream module, however the xpp3 module is never defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8738) InfinispanExtensionIT fails due to xpp3 ModuleLoadException

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-8738: ---------------------------------- Summary: InfinispanExtensionIT fails due to xpp3 ModuleLoadException Key: ISPN-8738 URL: https://issues.jboss.org/browse/ISPN-8738 Project: Infinispan Issue Type: Bug Components: WildFly modules Affects Versions: 9.2.0.CR1 Reporter: Ryan Emerson Assignee: Ryan Emerson ISPN-8427 introduced the XStreamException which depends on xpp3, this is defined as a dependency on the xstream module, however the xpp3 module is never defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7765) Allow HotRodDecoder to be shared between Netty pipelines

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7765?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7765: ------------------------------------------- Sounds reasonable to me. > Allow HotRodDecoder to be shared between Netty pipelines > -------------------------------------------------------- > > Key: ISPN-7765 > URL: https://issues.jboss.org/browse/ISPN-7765 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > Currently {{HotRodDecoder}} instance can not be shared between Netty pipelines as {{HotRodEncoder}}. Currently each pipeline creates its own instance by calling: > {code} > server.getDecoder() > {code} > in {{NettyChannelInitializer#initializeChannel}}. We could probably make it a bit more efficient (or limit allocation rate at least) if we allow sharing single instance between pipelines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8682) The events in the server log and DMR are not consistent

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-8682?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-8682: ------------------------------------- Roman, which are the missing events? And are they missing in the admin console (on the right side) ? > The events in the server log and DMR are not consistent > ------------------------------------------------------- > > Key: ISPN-8682 > URL: https://issues.jboss.org/browse/ISPN-8682 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Server > Affects Versions: 9.2.0.Beta2 > Reporter: Roman Macor > > Some events are displayed in server.log file but not in DMR > Steps to reproduce: > start server in the domain mode > turn off server-two node, turn it back on (e.g. through administration console) > connect through CLI and get the logs: > [domain@localhost:9990 /] cd /host=master/server=server-one/subsystem=datagrid-infinispan/cache-container=clustered > [domain@localhost:9990 cache-container=clustered] :read-event-log(lines=20) > compare the logs with server.log file -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8593) Switch to DNS_PING

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8593?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8593: -------------------------------------- Sprint: Sprint #8 Jan 29th - Feb 16th > Switch to DNS_PING > ------------------ > > Key: ISPN-8593 > URL: https://issues.jboss.org/browse/ISPN-8593 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7599) Add Jolokia to the server

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7599?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7599: -------------------------------------- Sprint: Sprint #5 Nov 6th - Nov 24th, Sprint #6 Nov 27th - Dec 15th (was: Sprint #5 Nov 6th - Nov 24th, Sprint #6 Nov 27th - Dec 15th, Sprint #7 Jan 8th - Jan 26th) > Add Jolokia to the server > ------------------------- > > Key: ISPN-7599 > URL: https://issues.jboss.org/browse/ISPN-7599 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud, Server > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 9.2.0.Final > > > The server should support exposing [Jolokia|https://jolokia.org] endpoints. The support should be disabled by default and there should be possibility to enable it using an environmental variable. > OpenShift has special Administration Console for Jolokia-enabled endpoints. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8502) Size Hot Rod (and REST) worker thread pool for limited Pod size

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8502?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8502: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Size Hot Rod (and REST) worker thread pool for limited Pod size > --------------------------------------------------------------- > > Key: ISPN-8502 > URL: https://issues.jboss.org/browse/ISPN-8502 > Project: Infinispan > Issue Type: Bug > Components: Cloud > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Currently we do not size thread pools which may result in OutOfMemory Errors when invoking many concurrent requests. Our environment can be very limited (80 MB or Xmx plus off-heap with eviction). We need to take this into consideration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8593) Switch to DNS_PING

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8593?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8593: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-container-images/jboss-dataservices-image/pull/67 > Switch to DNS_PING > ------------------ > > Key: ISPN-8593 > URL: https://issues.jboss.org/browse/ISPN-8593 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018