June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9258) Transactions dependency should not be provided

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9258?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-9258: ---------------------------------------- [~pruivo], I've created ISPN-9262 as follow up. > Transactions dependency should not be provided > ---------------------------------------------- > > Key: ISPN-9258 > URL: https://issues.jboss.org/browse/ISPN-9258 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Transactions > Affects Versions: 9.3.0.CR1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 9.3.0.Final > > > When starting Java Hot Rod client, I get: > {code} > java.lang.NoClassDefFoundError: javax/transaction/RollbackException > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:95) > at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:106) > at annotated.pojos.PokemonQueryTest.testPokemonQuery(PokemonQueryTest.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) > at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: java.lang.ClassNotFoundException: javax.transaction.RollbackException > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 25 more > {code} > The way the code is designed, the javax.transaction dependency is not really provided. > I'm going to submit a JIRA to make it not provided for now. > [~pruivo], Can you then make the code isolate this so that it's only loaded if using transactions? Then it would be provided. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9262) Make javax.transaction dependency really provided

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9262: -------------------------------------- Summary: Make javax.transaction dependency really provided Key: ISPN-9262 URL: https://issues.jboss.org/browse/ISPN-9262 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Pedro Ruivo Follow up to ISPN-9258, javax.transaction dependency should only be needed when user is using the corresponding APIs. Marking the dependency as provided is not enough, the code should be modularized so that the client code that deals with transactions depending on javax.transaction is only loaded when such APIs are used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9261) Hot Rod Lightweight Transaction (recovery)

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-9261: --------------------------------- Summary: Hot Rod Lightweight Transaction (recovery) Key: ISPN-9261 URL: https://issues.jboss.org/browse/ISPN-9261 Project: Infinispan Issue Type: Feature Request Components: Hot Rod, Remote Protocols, Transactions Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 9.4.0.Alpha1 Recovery support for Hot Rod Transactions -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9176) Hot Rod Lightweight Transaction (XaResource)

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9176?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9176: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.CR1 (was: 9.3.0.Final) Resolution: Done > Hot Rod Lightweight Transaction (XaResource) > -------------------------------------------- > > Key: ISPN-9176 > URL: https://issues.jboss.org/browse/ISPN-9176 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.3.0.CR1 > > > XaResource enlistment for Hot Rod Transactions. No recovery support yet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8905) Segment-aware non-shared cache stores

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8905?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8905: -------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Segment-aware non-shared cache stores > ------------------------------------- > > Key: ISPN-8905 > URL: https://issues.jboss.org/browse/ISPN-8905 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Final > > > Non shared stores should allow for segment based store separation. This might involve creating a store per segment. But this allows for superior iteration performance over a subset of segments. > Distributed stores benefit the most from this due to the fact that iteration is done at the segment level to help ensure that duplicate entries are not retrieved. It also would be beneficial for state transfer and other operations that operate only upon a given set of segments. > This could be advantageous even for REPL and LOCAL caches as there is then a very clear separation of stores to process in parallel for given operations. This would have to be verified with tests to see if this is worth it though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9176) Hot Rod Lightweight Transaction (XaResource)

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9176?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9176: ------------------------------ Status: Open (was: New) > Hot Rod Lightweight Transaction (XaResource) > -------------------------------------------- > > Key: ISPN-9176 > URL: https://issues.jboss.org/browse/ISPN-9176 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.3.0.Final > > > XaResource enlistment for Hot Rod Transactions. No recovery support yet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9176) Hot Rod Lightweight Transaction (XaResource)

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9176?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9176: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5991 > Hot Rod Lightweight Transaction (XaResource) > -------------------------------------------- > > Key: ISPN-9176 > URL: https://issues.jboss.org/browse/ISPN-9176 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.3.0.Final > > > XaResource enlistment for Hot Rod Transactions. No recovery support yet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8234: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema > ------------------------------------------------------------------------------ > > Key: ISPN-8234 > URL: https://issues.jboss.org/browse/ISPN-8234 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9190) Make trace logging faster by writing a separate log file for each test

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9190?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9190: ---------------------------------- Sprint: Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.CR1) > Make trace logging faster by writing a separate log file for each test > ---------------------------------------------------------------------- > > Key: ISPN-9190 > URL: https://issues.jboss.org/browse/ISPN-9190 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.Final > > > Logging each test to a separate file is cheaper because each test uses a separate appender, so there's no contention. The total size may also be smaller (with {{CompressedFileAppender}}) because the test name is repeated a lot and there isn't so much overlap between different tests. > Most important, keeping only the logs of failed tests becomes much faster. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9188) Cancelling the last segment doesn't remove transfer task

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9188?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9188: ---------------------------------- Sprint: Sprint 9.3.0.CR1, Sprint 9.3.0.Final (was: Sprint 9.3.0.CR1) > Cancelling the last segment doesn't remove transfer task > -------------------------------------------------------- > > Key: ISPN-9188 > URL: https://issues.jboss.org/browse/ISPN-9188 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.3.0.Final > > > If an {{InboundTransferTask}} has some completed segments and the last segment in an is cancelled with {{cancelSegments()}} (because the local node is no longer an owner), the task is never completed or removed from the list of active transfers. > In the log below, NodeA adds segment 243 in topology 10. The transfer fails because NodeB shut down, so it's retried in topology 11 from NodeC., > {noformat} > 13:19:17,057 TRACE (transport-thread-Test-NodeA-p22712-t2:[Topology-cluster-listener]) [StateConsumerImpl] Received new topology for cache cluster-listener, isRebalance = true, isMember = true, topology = CacheTopology{id=10, phase=READ_OLD_WRITE_ALL, rebalanceId=4, currentCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (3)[Test-NodeA-53146: 79+82, Test-NodeB-56589: 90+84, Test-NodeC-22289: 87+90]}, pendingCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (4)[Test-NodeA-53146: 55+54, Test-NodeB-56589: 67+60, Test-NodeC-22289: 67+69, Test-NodeD-8561: 67+73]}, unionCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (4)[Test-NodeA-53146: 79+87, Test-NodeB-56589: 90+85, Test-NodeC-22289: 87+93, Test-NodeD-8561: 0+140]}, actualMembers=[Test-NodeA-53146, Test-NodeB-56589, Test-NodeC-22289, Test-NodeD-8561], persistentUUIDs=[dff2268e-e59e-48cc-809d-dcfe0774d1d8, 01379420-7999-4abf-abd8-2777454c035a, e9090b94-dc69-49d8-a2dc-ae0ad7f18fe0, 8edade14-6827-4b67-93d2-49b93844d8ad]} > 13:19:17,097 TRACE (transport-thread-Test-NodeA-p22712-t2:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: added segments: {18 71 91-92 243}; removed segments: {} > 13:19:17,097 TRACE (transport-thread-Test-NodeA-p22712-t2:[Topology-cluster-listener]) [StateConsumerImpl] Adding transfer from Test-NodeB-56589 for segments {18 71 91 243} > 13:19:17,098 TRACE (transport-thread-Test-NodeA-p22712-t2:[Topology-cluster-listener]) [StateConsumerImpl] Adding transfer from Test-NodeC-22289 for segments {92} > 13:19:17,107 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] Received new topology for cache cluster-listener, isRebalance = false, isMember = true, topology = CacheTopology{id=11, phase=READ_OLD_WRITE_ALL, rebalanceId=4, currentCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (2)[Test-NodeA-53146: 122+39, Test-NodeC-22289: 134+43]}, pendingCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (2)[Test-NodeA-53146: 120+31, Test-NodeC-22289: 136+42]}, unionCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (2)[Test-NodeA-53146: 122+60, Test-NodeC-22289: 134+71]}, actualMembers=[Test-NodeA-53146, Test-NodeC-22289, Test-NodeD-8561], persistentUUIDs=[dff2268e-e59e-48cc-809d-dcfe0774d1d8, e9090b94-dc69-49d8-a2dc-ae0ad7f18fe0, 8edade14-6827-4b67-93d2-49b93844d8ad]} > 13:19:17,140 TRACE (stateTransferExecutor-thread-Test-NodeA-p22713-t1:[StateRequest-cluster-listener]) [StateConsumerImpl] Inbound transfer finished: InboundTransferTask{segments={18 71 91 243}, finishedSegments={}, unfinishedSegments={18 71 91 243}, source=Test-NodeB-56589, isCancelled=false, completionFuture=java.util.concurrent.CompletableFuture@5237f653[Completed exceptionally], topologyId=10, timeout=240000, cacheName=cluster-listener} > 13:19:17,156 TRACE (remote-thread-Test-NodeA-p22710-t5:[cluster-listener]) [StateConsumerImpl] Segments not received yet for cache cluster-listener: {Test-NodeB-56589=[InboundTransferTask{segments={18 71 91 243}, finishedSegments={}, unfinishedSegments={18 71 91 243}, source=Test-NodeB-56589, isCancelled=false, completionFuture=java.util.concurrent.CompletableFuture@5237f653[Completed exceptionally], topologyId=10, timeout=240000, cacheName=cluster-listener}]} > 13:19:17,273 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] Removing inbound transfers from node Test-NodeB-56589 for segments {18 71 91 243} > 13:19:17,274 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] Adding transfer from Test-NodeC-22289 for segments {18 71 91 243} > 13:19:17,283 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] Received new topology for cache cluster-listener, isRebalance = true, isMember = true, topology = CacheTopology{id=12, phase=READ_OLD_WRITE_ALL, rebalanceId=5, currentCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (2)[Test-NodeA-53146: 122+39, Test-NodeC-22289: 134+43]}, pendingCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (3)[Test-NodeA-53146: 76+78, Test-NodeC-22289: 90+80, Test-NodeD-8561: 90+98]}, unionCH=PartitionerConsistentHash:DefaultConsistentHash{ns=256, owners = (3)[Test-NodeA-53146: 122+75, Test-NodeC-22289: 134+73, Test-NodeD-8561: 0+188]}, actualMembers=[Test-NodeA-53146, Test-NodeC-22289, Test-NodeD-8561], persistentUUIDs=[dff2268e-e59e-48cc-809d-dcfe0774d1d8, e9090b94-dc69-49d8-a2dc-ae0ad7f18fe0, 8edade14-6827-4b67-93d2-49b93844d8ad]} > 13:19:17,285 WARN (remote-thread-Test-NodeA-p22710-t6:[cluster-listener]) [StateConsumerImpl] Discarding received cache entries for segment 243 of cache cluster-listener because they do not belong to this node. > 13:19:17,286 TRACE (remote-thread-Test-NodeA-p22710-t6:[cluster-listener]) [StateConsumerImpl] Segments not received yet for cache cluster-listener: {Test-NodeC-22289=[InboundTransferTask{segments={18 71 91 243}, finishedSegments={18 71 91}, unfinishedSegments={243}, source=Test-NodeC-22289, isCancelled=false, completionFuture=java.util.concurrent.CompletableFuture@2755cd[Not completed, 1 dependents], topologyId=11, timeout=240000, cacheName=cluster-listener}]} > 13:19:17,428 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] On cache cluster-listener we have: added segments: {45 54-55 63 90 95-98 114-115 119 138-140 155-156 167 174-175 205 220-222}; removed segments: {30 66-67 77 93 190-192 243} > 13:19:17,429 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [InboundTransferTask] Partially cancelling inbound state transfer from node Test-NodeC-22289, segments {243} > 13:19:17,429 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] Adding transfer from Test-NodeC-22289 for segments {45 54-55 63 90 95-98 114-115 119 138-140 155-156 167 174-175 205 220-222} > 13:19:17,430 TRACE (transport-thread-Test-NodeA-p22712-t1:[Topology-cluster-listener]) [StateConsumerImpl] notifyEndOfStateTransferIfNeeded: no active transfers > {noformat} > The last message is incorrect: the rebalance phase is not confirmed because there are 2 active transfers from NodeC: the 243 one, which wasn't completely cancelled, and the 45...222 one, which hasn't yet started. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018