October 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8444) JPA cache store failed to deploy in OSGi

by Martin Gencur (JIRA)

Martin Gencur created ISPN-8444: ----------------------------------- Summary: JPA cache store failed to deploy in OSGi Key: ISPN-8444 URL: https://issues.jboss.org/browse/ISPN-8444 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Martin Gencur Assignee: Martin Gencur The test suite hands when running OSGi tests and doesn't show any meaningful error. However, the Karaf server shows this: {code} 2017-10-26T12:21:35,280 | ERROR | pool-1-thread-2 | BootFeaturesInstaller | 9 - org.apache.karaf.features.core - 4.1.2 | Error installing boot features org.apache.karaf.features.internal.util.MultiException: Error: Error downloading file:/home/mgencur/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.1-api/1.0.0.Draft-16/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar${version.hibernate.javax.persistence} Error downloading file:/home/mgencur/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.1-api/1.0.0.Draft-16/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar${version.hibernate.javax.persistence} at org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.<init>(MavenDownloadManager.java:84) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:375) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:372) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:187) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:291) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1233) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$0(FeaturesServiceImpl.java:1132) [9:org.apache.karaf.features.core:4.1.2] at org.apache.karaf.features.internal.service.FeaturesServiceImpl$$Lambda$15/2139805671.call(Unknown Source) [9:org.apache.karaf.features.core:4.1.2] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?] at java.lang.Thread.run(Thread.java:745) [?:?] Suppressed: java.io.IOException: Error downloading file:/home/mgencur/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.1-api/1.0.0.Draft-16/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar${version.hibernate.javax.persistence} at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77) [9:org.apache.karaf.features.core:4.1.2] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:?] at java.lang.Thread.run(Thread.java:745) [?:?] Caused by: java.io.IOException: Could not download [file:/home/mgencur/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.1-api/1.0.0.Draft-16/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar${version.hibernate.javax.persistence}] at org.apache.karaf.features.internal.download.impl.SimpleDownloadTask.download(SimpleDownloadTask.java:90) ~[?:?] at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60) ~[?:?] ... 7 more Caused by: java.io.FileNotFoundException: /home/mgencur/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.1-api/1.0.0.Draft-16/hibernate-jpa-2.1-api-1.0.0.Draft-16.jar${version.hibernate.javax.persistence} (No such file or directory) at java.io.FileInputStream.open0(Native Method) ~[?:?] at java.io.FileInputStream.open(FileInputStream.java:195) ~[?:?] at java.io.FileInputStream.<init>(FileInputStream.java:138) ~[?:?] at java.io.FileInputStream.<init>(FileInputStream.java:93) ~[?:?] at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90) ~[?:?] at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188) ~[?:?] at java.net.URL.openStream(URL.java:1038) ~[?:?] at org.apache.karaf.features.internal.download.impl.SimpleDownloadTask.download(SimpleDownloadTask.java:76) ~[?:?] at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60) ~[?:?] ... 7 more {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-8400: ------------------------------------------- That sounds good to me... [~NadirX][~epbernard] - any thoughts? > Adjust merge policies for JDG Online Services > --------------------------------------------- > > Key: ISPN-8400 > URL: https://issues.jboss.org/browse/ISPN-8400 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > > Both Shared Memory and Caching Service require custom merge policies. > In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-8400: ------------------------------------ So Caching Service will be REMOVE_ALL like you say. For Shared Memory Service, I was thinking that we would utilise the PREFERRED_NON_NULL policy. So this means that if an entry exists in the preferred partition (partition coordinating the merge) than we utilise that value, however if this is NULL we utilise the non-null value from the other partition. As we will be preventing read/writes once the split-brain has been detected, the window for conflicts is going to be reasonably small. So I'm not sure we can do much better than this for now. More advanced options might be available when we have versioning, eventual consistency etc. > Adjust merge policies for JDG Online Services > --------------------------------------------- > > Key: ISPN-8400 > URL: https://issues.jboss.org/browse/ISPN-8400 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > > Both Shared Memory and Caching Service require custom merge policies. > In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-8400: ------------------------------------------- Ok, sounds good. So how this will work in details for each service? For Caching Service we will remove all conflicting entries (since there are no guarantees). But would would be the behavior of Shared Memory Service? > Adjust merge policies for JDG Online Services > --------------------------------------------- > > Key: ISPN-8400 > URL: https://issues.jboss.org/browse/ISPN-8400 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Ryan Emerson > > Both Shared Memory and Caching Service require custom merge policies. > In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8442) Activator not called in off-heap data conatiner

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-8442?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-8442: ---------------------------------- Status: Open (was: New) > Activator not called in off-heap data conatiner > ----------------------------------------------- > > Key: ISPN-8442 > URL: https://issues.jboss.org/browse/ISPN-8442 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Off Heap > Affects Versions: 9.1.0.Final, 9.2.0.Alpha1 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Off-heap container doesn't call activator. This resuls into various issue - e.g if passivation is enabled, cache entry is evicted and later on removed, it's still present in cache, as cache still sees it in cache store. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8442) Activator not called in off-heap data conatiner

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-8442?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-8442: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5541 > Activator not called in off-heap data conatiner > ----------------------------------------------- > > Key: ISPN-8442 > URL: https://issues.jboss.org/browse/ISPN-8442 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Off Heap > Affects Versions: 9.1.0.Final, 9.2.0.Alpha1 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Off-heap container doesn't call activator. This resuls into various issue - e.g if passivation is enabled, cache entry is evicted and later on removed, it's still present in cache, as cache still sees it in cache store. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8443) Activator should delete entries from all stores on removing entries

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-8443?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-8443: ---------------------------------- Status: Open (was: New) > Activator should delete entries from all stores on removing entries > ------------------------------------------------------------------- > > Key: ISPN-8443 > URL: https://issues.jboss.org/browse/ISPN-8443 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Alpha1 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Currently activator {{onRemove}} method deletes entries only from shared cache stores. It should remove entries no matter if the store is shared or not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8443) Activator should delete entries from all stores on removing entries

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-8443?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-8443: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5541 > Activator should delete entries from all stores on removing entries > ------------------------------------------------------------------- > > Key: ISPN-8443 > URL: https://issues.jboss.org/browse/ISPN-8443 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Alpha1 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > Currently activator {{onRemove}} method deletes entries only from shared cache stores. It should remove entries no matter if the store is shared or not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8443) Activator should delete entries from all stores on removing entries

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-8443: ------------------------------------- Summary: Activator should delete entries from all stores on removing entries Key: ISPN-8443 URL: https://issues.jboss.org/browse/ISPN-8443 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.2.0.Alpha1 Reporter: Vojtech Juranek Assignee: Vojtech Juranek Currently activator {{onRemove}} method deletes entries only from shared cache stores. It should remove entries no matter if the store is shared or not. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8442) Activator not called in off-heap data conatiner

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-8442: ------------------------------------- Summary: Activator not called in off-heap data conatiner Key: ISPN-8442 URL: https://issues.jboss.org/browse/ISPN-8442 Project: Infinispan Issue Type: Bug Components: Eviction, Off Heap Affects Versions: 9.2.0.Alpha1, 9.1.0.Final Reporter: Vojtech Juranek Assignee: Vojtech Juranek Off-heap container doesn't call activator. This resuls into various issue - e.g if passivation is enabled, cache entry is evicted and later on removed, it's still present in cache, as cache still sees it in cache store. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2017