June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11990) JDK 11 modules do not compile in IntelliJ

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11990?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11990: -------------------------------- Description: The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} {{java: cannot find symbol}} {{symbol: class StackWalker}} {{location: class org.infinispan.commons.jdkspecific.CallerId}} was: The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} {{java: cannot find symbol}} {{ symbol: class StackWalker}} {{ location: class org.infinispan.commons.jdkspecific.CallerId}} > JDK 11 modules do not compile in IntelliJ > ----------------------------------------- > > Key: ISPN-11990 > URL: https://issues.redhat.com/browse/ISPN-11990 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final > > > The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. > {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} > {{java: cannot find symbol}} > {{symbol: class StackWalker}} > {{location: class org.infinispan.commons.jdkspecific.CallerId}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11990) JDK 11 modules do not compile in IntelliJ

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11990?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11990: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8464 > JDK 11 modules do not compile in IntelliJ > ----------------------------------------- > > Key: ISPN-11990 > URL: https://issues.redhat.com/browse/ISPN-11990 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final > > > The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. > {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} > {{java: cannot find symbol}} > {{ symbol: class StackWalker}} > {{ location: class org.infinispan.commons.jdkspecific.CallerId}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11988) Remove include directive for persistence spi assembly

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11988?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11988. --------------------------------- Resolution: Done > Remove include directive for persistence spi assembly > ----------------------------------------------------- > > Key: ISPN-11988 > URL: https://issues.redhat.com/browse/ISPN-11988 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.CR1 > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 11.0.0.Final > > > Persistence SPI assembly was dropped in a separate PR but the include wasn't removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11990) JDK 11 modules do not compile in IntelliJ

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11990?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11990: -------------------------------- Status: Open (was: New) > JDK 11 modules do not compile in IntelliJ > ----------------------------------------- > > Key: ISPN-11990 > URL: https://issues.redhat.com/browse/ISPN-11990 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 11.0.0.Final > > > The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. > {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} > {{java: cannot find symbol}} > {{ symbol: class StackWalker}} > {{ location: class org.infinispan.commons.jdkspecific.CallerId}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11989) Fix ThreadLocalLeakTest

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11989?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11989: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix ThreadLocalLeakTest > ----------------------- > > Key: ISPN-11989 > URL: https://issues.redhat.com/browse/ISPN-11989 > Project: Infinispan > Issue Type: Component Upgrade > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Final > > > Caused by ISPN-11845 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11975) RemoteCacheImpl entry retrieval should be non blocking

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11975?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11975: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Final (was: 12.0.0.Final) Resolution: Done > RemoteCacheImpl entry retrieval should be non blocking > ------------------------------------------------------ > > Key: ISPN-11975 > URL: https://issues.redhat.com/browse/ISPN-11975 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > The RemoteCacheImpl class currently employs blocking while performing entry retrieval. We should able to change this to be fully non blocking, be server segment aware and perform retrieval in parallel across all needed servers. > We will have to add rxjava and reactive streams to the list of dependencies unfortunately, but is well worth it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11990) JDK 11 modules do not compile in IntelliJ

by Dan Berindei (Jira)

Dan Berindei created ISPN-11990: ----------------------------------- Summary: JDK 11 modules do not compile in IntelliJ Key: ISPN-11990 URL: https://issues.redhat.com/browse/ISPN-11990 Project: Infinispan Issue Type: Bug Components: Build Affects Versions: 11.0.0.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.0.Final The {{commons/jdk11}} module fails to compile in IntelliJ, because the IDE doesn't parse <{{release>11</release>}} correctly when the parent has {{<release>8</release}} ({{[IDEA-199818|https://youtrack.jetbrains.com/issue/IDEA-199818])}}. {{/home/dan/Work/infinispan/commons/jdk11/src/main/java/org/infinispan/commons/jdkspecific/CallerId.java:4:19}} {{java: cannot find symbol}} {{ symbol: class StackWalker}} {{ location: class org.infinispan.commons.jdkspecific.CallerId}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11832) ProtobufMetadataManagerInterceptor is blocking

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11832?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11832: --------------------------------- Status: Open (was: New) > ProtobufMetadataManagerInterceptor is blocking > ---------------------------------------------- > > Key: ISPN-11832 > URL: https://issues.redhat.com/browse/ISPN-11832 > Project: Infinispan > Issue Type: Bug > Components: Indexing > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > The interceptor uses invoke on the AsyncInterceptorChain in multiple places. This invocation can and will block. We should be using invokeAsync and chaining the stage. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11727) Async Cache Writer is blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11727?page=com.atlassian.jira.plugi... ] Will Burns resolved ISPN-11727. ------------------------------- Resolution: Out of Date Fixed by ISPN-10373 > Async Cache Writer is blocking > ------------------------------ > > Key: ISPN-11727 > URL: https://issues.redhat.com/browse/ISPN-11727 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > > The current AsyncCacheWriter is blocking on a few different levels. > It first has a lock to add a modification to its queue, which is able to be configured by the end user. It may even be possible to configure a value so low that if a bulkUpdate is done that is larger than the configured value it may hang (needs to be confirmed). > However this lock can and will block if an async update takes too long and the queue is full of writes. We should at least return a future that is complete when the value is written to the queue instead. > We may want to even use something like https://github.com/IBM/java-async-util with their AsyncSemaphore to handle this queueing in a non blocking way. This however will require https://issues.redhat.com/browse/ISPN-10373 to be implemented first, before it can be made fully non blocking. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11974) Remove GenericJbossMarshaller automatic configuration

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11974?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11974: -------------------------------- Description: Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan -12- 11 we should no automatically configure this marshaller if the module is present. (was: Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan 12 we should no automatically configure this marshaller if the module is present.) > Remove GenericJbossMarshaller automatic configuration > ----------------------------------------------------- > > Key: ISPN-11974 > URL: https://issues.redhat.com/browse/ISPN-11974 > Project: Infinispan > Issue Type: Task > Components: Configuration, Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Final > > > Currently if the {{infinispan-jboss-marshalling}} module is on the client classpath we automatically configure the client marshaller to be {{GenericJBossMarshaller}}. This causes issues with our testsuite, as the module is often on the classpath. Furthermore, we want users to start transitioning away from JBoss Marshalling. Therefore, from Infinispan -12- 11 we should no automatically configure this marshaller if the module is present. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 June 2020