July 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10430) Fix JdbcStringBasedStoreFunctionalTest thread leak

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-10430?page=com.atlassian.jira.plugin... ] Katia Aresti updated ISPN-10430: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7171 > Fix JdbcStringBasedStoreFunctionalTest thread leak > -------------------------------------------------- > > Key: ISPN-10430 > URL: https://issues.jboss.org/browse/ISPN-10430 > Project: Infinispan > Issue Type: Bug > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > java.lang.RuntimeException: Leaked threads: {Agroal_756431211: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreVamAltMapperTest]}, {Agroal_18676467981: reported, possible sources [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithManagedConnectionTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltTwoWayMapperTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedSegmentedStoreTest, org.infinispan.persistence.jdbc.stringbased.StringStoreWithPooledConnectionFunctionalTest, org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStoreAltMapperTest, org.infinispan.persistence.jdbc.stringbased.NonStringKeyPreloadTest]} at org.infinispan.commons.test.ThreadLeakChecker.performCheck(ThreadLeakChecker.java:200) at org.infinispan.commons.test.ThreadLeakChecker.checkForLeaks(ThreadLeakChecker.java:165) at org.infinispan.commons.test.TestNGSuiteChecksTest.afterSuite(TestNGSuiteChecksTest.java:46) ... Removed 25 stack frames -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10423) RocksDB ReadOptions memory leak

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10423?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10423: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7169, https://github.com/infinispan/infinispan/pull/7170 > RocksDB ReadOptions memory leak > ------------------------------- > > Key: ISPN-10423 > URL: https://issues.jboss.org/browse/ISPN-10423 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta5, 9.4.16.Final > > > Currently our rocksdb store impl creates a new ReadOptions instance per iterator created. As per the RocksDB we should be calling {{dispose()}} on this once it goes out of scope, so that the c++ underlying impl can free the memory. Currently we're not doing this, resulting in a memory leak. > As we only ever use the same ReadOptions for all iterators, we should simply re-use a singleton for all iterators and then dispose of this on shutdown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10423) RocksDB ReadOptions memory leak

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10423?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10423: -------------------------------- Status: Open (was: New) > RocksDB ReadOptions memory leak > ------------------------------- > > Key: ISPN-10423 > URL: https://issues.jboss.org/browse/ISPN-10423 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta5, 9.4.16.Final > > > Currently our rocksdb store impl creates a new ReadOptions instance per iterator created. As per the RocksDB we should be calling {{dispose()}} on this once it goes out of scope, so that the c++ underlying impl can free the memory. Currently we're not doing this, resulting in a memory leak. > As we only ever use the same ReadOptions for all iterators, we should simply re-use a singleton for all iterators and then dispose of this on shutdown. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10421) ServerNG: semantic network address configuration

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10421?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10421. --------------------------------- Resolution: Done > ServerNG: semantic network address configuration > ------------------------------------------------ > > Key: ISPN-10421 > URL: https://issues.jboss.org/browse/ISPN-10421 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5 > > > Use semantic naming for interface / network address selection compatible with JGroups http://www.jgroups.org/manual4/index.html#Transport > * GLOBAL Picks a global IP address if available. If not, falls back to a SITE_LOCAL IP address. > * SITE_LOCAL Picks a site local (non routable) IP address, e.g. from the 192.168.0.0 or 10.0.0.0 address range. > * LINK_LOCAL Picks a link-local IP address, from 169.254.1.0 through 169.254.254.255. > * NON_LOOPBACK Picks any non loopback address. > * LOOPBACK Pick a loopback address, e.g. 127.0.0.1. > * match-interface Pick an address which matches a pattern against the interface name, e.g. match-interface:eth.\* > * match-address Pick an address which matches a pattern against the host address, e.g. match-address:192.168.\* > * match-host Pick an address which matches a pattern against the host name, e.g. match-host:linux.\* -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10426) ServerNG: tool to add/manipulate users

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10426?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10426. --------------------------------- Resolution: Done > ServerNG: tool to add/manipulate users > -------------------------------------- > > Key: ISPN-10426 > URL: https://issues.jboss.org/browse/ISPN-10426 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5 > > > we need a tool to manipulate the user/group property files (add, change password, set roles) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10416) ServerNG: KeyCloak authentication/authorization

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10416?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10416. --------------------------------- Resolution: Done > ServerNG: KeyCloak authentication/authorization > ----------------------------------------------- > > Key: ISPN-10416 > URL: https://issues.jboss.org/browse/ISPN-10416 > Project: Infinispan > Issue Type: Sub-task > Components: Security, Server > Affects Versions: 10.0.0.Beta4 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta5, 10.0.0.Final > > > Use the Elytron trust realm and the oauth2 introspection to support OAUTHBEARER in Hot Rod and BEARER in REST -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10431) REST client

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10431: -------------------------------------- Summary: REST client Key: ISPN-10431 URL: https://issues.jboss.org/browse/ISPN-10431 Project: Infinispan Issue Type: Feature Request Components: REST Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Beta5 There are several places in Infinispan where we need a common HTTP client API: * CLI * REST loader * Testsuite Since the testsuite already has one based on AHC, it can be refactored and reused. In the future it can be enhanced with ISPN-5186 -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5357?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5357: ---------------------------------- Summary: Hot Rod protocol .NEXT (was: Hot Rod protocol 3.0) > Hot Rod protocol .NEXT > ---------------------- > > Key: ISPN-5357 > URL: https://issues.jboss.org/browse/ISPN-5357 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan should expose a single endpoint which should behave as follows: > - by default offer an HTTP/1.1 RESTftul interface > - through HTTP upgrade allow switching to better protocols > - support an HTTP/2 RESTful interface > - support Hot Rod 3.0, which would be a gRPC protocol with additional L2 and L3 intelligence for capable clients > *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.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-30) Tool to generate protobuf schema from a sample JSON object

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-30?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-30: -------------------------------- Description: This is just nice to have. Could be used to emulate 'schemaless' a la Elastic :) (was: This is just nice to have.) > Tool to generate protobuf schema from a sample JSON object > ---------------------------------------------------------- > > Key: IPROTO-30 > URL: https://issues.jboss.org/browse/IPROTO-30 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Priority: Major > > This is just nice to have. Could be used to emulate 'schemaless' a la Elastic :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-30) Tool to generate protobuf schema from a sample JSON object

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-30?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-30: -------------------------------- Summary: Tool to generate protobuf schema from a sample JSON object (was: Tool to generate protobuf schema from a sample JSON objects) > Tool to generate protobuf schema from a sample JSON object > ---------------------------------------------------------- > > Key: IPROTO-30 > URL: https://issues.jboss.org/browse/IPROTO-30 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2019