November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10936) StaticFileResource does not detect correct media types for files

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10936?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10936: ------------------------------------- Status: Open (was: New) > StaticFileResource does not detect correct media types for files > ---------------------------------------------------------------- > > Key: ISPN-10936 > URL: https://issues.jboss.org/browse/ISPN-10936 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently is uses {{java.nio.Files.probeContentType}} which is broken as it is environment dependent -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10936) StaticFileResource does not detect correct media types for files

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10936: ---------------------------------------- Summary: StaticFileResource does not detect correct media types for files Key: ISPN-10936 URL: https://issues.jboss.org/browse/ISPN-10936 Project: Infinispan Issue Type: Bug Components: REST Affects Versions: 10.0.0.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Fix For: 10.1.0.Beta1 Currently is uses {{java.nio.Files.probeContentType}} which is broken as it is environment dependent -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10925) CacheMgmtInterceptor.visitComputeCommand uses millis to update store time stats which are in nanos

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10925?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10925: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheMgmtInterceptor.visitComputeCommand uses millis to update store time stats which are in nanos > -------------------------------------------------------------------------------------------------- > > Key: ISPN-10925 > URL: https://issues.jboss.org/browse/ISPN-10925 > Project: Infinispan > Issue Type: Bug > Components: Core, JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10935) No marshaller registered for Java type java.util.UUID

by Joaquim Mascarenhas (Jira)

Joaquim Mascarenhas created ISPN-10935: ------------------------------------------ Summary: No marshaller registered for Java type java.util.UUID Key: ISPN-10935 URL: https://issues.jboss.org/browse/ISPN-10935 Project: Infinispan Issue Type: Bug Affects Versions: 10.0.1.Final Environment: Java version: openjdk version "13" 2019-09-17 Infinispan dependencies: <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-hibernate-cache-v53</artifactId> <version>10.0.1.Final</version> </dependency> <dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-jcache</artifactId> <version>10.0.1.Final</version> </dependency> Reporter: Joaquim Mascarenhas Project is based on Wicket with hibernate and infinispan. Page render tests are failing after I updated infinispan version to 10.0.1.Final. Works if I change version to 9.4.16.Final. Caused by: javax.cache.CacheException: org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.MarshallingException: No marshaller registered for Java type java.util.UUID at org.infinispan.jcache.Exceptions.launderException(Exceptions.java:70) at org.infinispan.jcache.Exceptions.launderException(Exceptions.java:78) at org.infinispan.jcache.embedded.JCache.get(JCache.java:191) at com.windcam.web.SubdomainHeaderLogoImageTag.getCachedImageInfo(SubdomainHeaderLogoImageTag.java:113) at com.windcam.web.SubdomainHeaderLogoImageTag.<init>(SubdomainHeaderLogoImageTag.java:71) at com.windcam.web.SubdomainHeaderLogoImageTag.<init>(SubdomainHeaderLogoImageTag.java:67) at com.windcam.web.SubdomainManagementListPage$1.populateItem(SubdomainManagementListPage.java:26) at org.apache.wicket.markup.html.list.ListView.onPopulate(ListView.java:523) at org.apache.wicket.markup.repeater.AbstractRepeater.onBeforeRender(AbstractRepeater.java:124) at org.apache.wicket.Component.beforeRender(Component.java:939) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1754) ... 99 more Caused by: org.infinispan.persistence.spi.PersistenceException: org.infinispan.commons.marshall.MarshallingException: No marshaller registered for Java type java.util.UUID at org.infinispan.marshall.persistence.impl.MarshallableEntryImpl.marshall(MarshallableEntryImpl.java:211) at org.infinispan.marshall.persistence.impl.MarshallableEntryImpl.<init>(MarshallableEntryImpl.java:36) at org.infinispan.marshall.persistence.impl.MarshalledEntryFactoryImpl.create(MarshalledEntryFactoryImpl.java:64) at org.infinispan.jcache.embedded.JCacheLoaderAdapter.loadEntry(JCacheLoaderAdapter.java:51) at org.infinispan.persistence.manager.PersistenceManagerImpl.loadFromAllStoresSync(PersistenceManagerImpl.java:830) at org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$loadFromAllStores$19(PersistenceManagerImpl.java:848) at org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$supplyOnPersistenceExAndContinue$9(PersistenceManagerImpl.java:559) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1771) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:830) Caused by: org.infinispan.commons.marshall.MarshallingException: No marshaller registered for Java type java.util.UUID at org.infinispan.marshall.persistence.impl.PersistenceMarshallerImpl.objectToBuffer(PersistenceMarshallerImpl.java:164) at org.infinispan.marshall.persistence.impl.PersistenceMarshallerImpl.objectToBuffer(PersistenceMarshallerImpl.java:132) at org.infinispan.marshall.persistence.impl.MarshallableEntryImpl.marshall(MarshallableEntryImpl.java:209) ... 10 more -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10920) [9.4.x] SB Starter Versions

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10920?page=com.atlassian.jira.plugin... ] Donald Naro closed ISPN-10920. ------------------------------ > [9.4.x] SB Starter Versions > --------------------------- > > Key: ISPN-10920 > URL: https://issues.jboss.org/browse/ISPN-10920 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need to document SB starter dependencies, relates to JDG-3308 > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 1.0.7.Final-redhat-00011 is for SB 1.5.x > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 2.1.8.redhat-00001 is for SB 2.x > https://github.com/infinispan/infinispan/blob/792fdc4d7b98bd009eea8632b28... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10868) Default whitelist should allow primitives, arrays and reference arrays

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10868?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10868: -------------------------------- Description: Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating. was: Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. ~~There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating.~~ > Default whitelist should allow primitives, arrays and reference arrays > ---------------------------------------------------------------------- > > Key: ISPN-10868 > URL: https://issues.jboss.org/browse/ISPN-10868 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: Dan Berindei > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final > > > Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. > There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10868) Default whitelist should allow primitives, arrays and reference arrays

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10868?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10868: -------------------------------- Description: Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. ~~There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating.~~ was: Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating. > Default whitelist should allow primitives, arrays and reference arrays > ---------------------------------------------------------------------- > > Key: ISPN-10868 > URL: https://issues.jboss.org/browse/ISPN-10868 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: Dan Berindei > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final > > > Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. > ~~There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating.~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10868) Default whitelist should allow primitives, arrays and reference arrays

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10868?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10868: -------------------------------- Summary: Default whitelist should allow primitives, arrays and reference arrays (was: Default whitelist should allow primitives, arrays and ArrayList) > Default whitelist should allow primitives, arrays and reference arrays > ---------------------------------------------------------------------- > > Key: ISPN-10868 > URL: https://issues.jboss.org/browse/ISPN-10868 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: Dan Berindei > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final > > > Java serialization whitelist should include primitive wrapper classes and arrays types, if only because it's tedious to specify all of them in the configuration. > There's a similar argument for adding {{java.util.ArrayList}} to the default whitelist, especially to use as keys, because {{Object[]}} keys do not work with {{OBJECT}} storage ({{equals()}} and {{hashCode()}} are wrong). I'm not convinced yet, because applications eventually want to use a custom key class, and POCs can get away with converting to {{String}} and concatenating. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10855?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10855: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7498, https://github.com/infinispan/infinispan/pull/7571, https://github.com/infinispan/infinispan/pull/7573 (was: https://github.com/infinispan/infinispan/pull/7498, https://github.com/infinispan/infinispan/pull/7571) > MultipleCacheManagersTest factory issues are ignored > ---------------------------------------------------- > > Key: ISPN-10855 > URL: https://issues.jboss.org/browse/ISPN-10855 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > TestNG doesn't like exceptions being thrown from {{@Factory}} methods, so when {{MultipleCacheManager.defaultFactory()}} finds a problem with the concrete {{factory()}} implementation or with the annotations it replaces the test instance with a {{TestFrameworkFailure}}. > Turns out that doesn't actually work: TestNG ignores the {{TestFrameworkFailure}} instance and runs the tests on a "default instance" of the test class. This is ok when the problem is the concrete class didn't override {{factory()}} and very likely the test author wanted a single test instance, but it's not ok for other errors like {{factory()}} being copy-pasted from super with the wrong class name. > We can make TestNG report our factory failures if we implement {{IInstanceInfo}} and mock all the test/configuration methods to throw our exception. We just need to make all configuration methods non-final so we can mock them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10929) ClusterPublisher reduction combineStages concurrency level is too high

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10929?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10929: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7569, https://github.com/infinispan/infinispan/pull/7572 > ClusterPublisher reduction combineStages concurrency level is too high > ---------------------------------------------------------------------- > > Key: ISPN-10929 > URL: https://issues.jboss.org/browse/ISPN-10929 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > The combineStages method in ClusterPublisherImpl currently uses flatMap without an explicit concurrency level. That means it will subscribe to up to 128 futures at the same time. This isn't a problem when only in memory is used as the stages are completed as they are received. However when a segmented store is in play, this means it will process 128 segments at the same time, even when doing sequential publisher. > We should instead limit the concurrency to the cpuCount when the publisher is parallel and just 1 when it is sequential. The latter matches how many threads the upstream publisher will use as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019