January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5074?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5074: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1182140|https://bugzilla.redhat.com/show_bug.cgi?id=1182140] from ASSIGNED to POST > Update remote query quickstart with the new annotation driven Protostream marshalling > ------------------------------------------------------------------------------------- > > Key: ISPN-5074 > URL: https://issues.jboss.org/browse/ISPN-5074 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5150) Eager near cache tests randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5150?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5150: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3227 > Eager near cache tests randomly failing > --------------------------------------- > > Key: ISPN-5150 > URL: https://issues.jboss.org/browse/ISPN-5150 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.1.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 7.1.0.CR1 > > Attachments: LazyNearCacheTest_pr_galderz_t_5130_20150115.log > > > expectNearGetValue() failing randomly in eager near cache tests randomly, e..g > http://ci.infinispan.org/viewLog.html?buildId=22924&buildTypeId=bt9&tab=b... > {code} > java.lang.AssertionError: expected:<v1> but was:<null> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.client.hotrod.near.AssertsNearCache.assertGetKeyValue(AssertsNearCache.java:168) > at org.infinispan.client.hotrod.near.AssertsNearCache.expectNearGetValue(AssertsNearCache.java:85) > at org.infinispan.client.hotrod.near.EagerNearCacheTest.testGetNearCache(EagerNearCacheTest.java:37) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} > In this case, the tests afterwards fail with: > {code} > java.lang.AssertionError: [org.infinispan.client.hotrod.near.MockNearCacheService$MockPutIfAbsentEvent{key=1, value=VersionedValueImpl{version=1, value=v1}}] expected:<0> but was:<1> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) > at org.infinispan.client.hotrod.near.AssertsNearCache.expectNoNearEvents(AssertsNearCache.java:71) > at org.infinispan.client.hotrod.near.EagerNearCacheTest.testGetUpdatesNearCache(EagerNearCacheTest.java:59) > {code} > We also see a similar failure in ClusterEagerNearCacheTest > http://ci.infinispan.org/viewLog.html?buildId=22966&tab=buildResultsDiv&b... > {code} > java.lang.AssertionError: expected:<v1> but was:<null> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) > at org.infinispan.client.hotrod.near.AssertsNearCache.assertGetKeyValue(AssertsNearCache.java:168) > at org.infinispan.client.hotrod.near.AssertsNearCache.expectNearGetValue(AssertsNearCache.java:85) > at org.infinispan.client.hotrod.near.ClusterEagerNearCacheTest.expectNearCacheUpdates(ClusterEagerNearCacheTest.java:65) > at org.infinispan.client.hotrod.near.ClusterEagerNearCacheTest.testNearCacheUpdatesSeenByAllClients(ClusterEagerNearCacheTest.java:58) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5158) Transaction rolled back but returns successful response

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5158?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5158: ---------------------------------- Assignee: Dan Berindei > Transaction rolled back but returns successful response > ------------------------------------------------------- > > Key: ISPN-5158 > URL: https://issues.jboss.org/browse/ISPN-5158 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Attachments: tx.txt, views.txt > > > When the cluster is merging, it is possible that a node is removed from the view although it is still responsive. Eventually the cluster is merged correctly, but since the node is reported as missing from the view, transaction originating from this node is rolled back. > {code} > 10:01:36,116 TRACE [org.infinispan.interceptors.TxInterceptor] (remote-thread-151) Rolling back remote transaction GlobalTransaction:<edg-perf02-39415>:28106:remote because either already completed(false) or originator no longer in the cluster(true). > {code} > However, even after this a successful response is sent to the originator: > {code} > 10:01:36,119 TRACE [org.infinispan.remoting.InboundInvocationHandlerImpl] (remote-thread-151) About to send back response null for command PrepareCommand {modifications=[PutKeyValueCommand{key=key_0000000000001318, value=[19 #1: 1195, ], flags=[SKIP_CACHE_LOAD, SKIP_REMOTE_LOOKUP], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedMetadata{version=null}, successful=true}], onePhaseCommit=false, gtx=GlobalTransaction:<edg-perf02-39415>:28106:remote, cacheName='testCache', topologyId=47} > {code} > Originator then expects that the transaction was successfully prepared: > {code} > 10:01:36,124 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-9) Responses: [sender=edg-perf01-36235, received=true, suspected=false] > [sender=edg-perf03-24110, received=true, suspected=false] > 10:01:36,135 TRACE [org.infinispan.transaction.TransactionCoordinator] (DefaultStressor-9) Committing transaction GlobalTransaction:<edg-perf02-39415>:28106:local > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5158) Transaction rolled back but returns successful response

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5158?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5158: ------------------------------- Status: Open (was: New) > Transaction rolled back but returns successful response > ------------------------------------------------------- > > Key: ISPN-5158 > URL: https://issues.jboss.org/browse/ISPN-5158 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Priority: Critical > Attachments: tx.txt, views.txt > > > When the cluster is merging, it is possible that a node is removed from the view although it is still responsive. Eventually the cluster is merged correctly, but since the node is reported as missing from the view, transaction originating from this node is rolled back. > {code} > 10:01:36,116 TRACE [org.infinispan.interceptors.TxInterceptor] (remote-thread-151) Rolling back remote transaction GlobalTransaction:<edg-perf02-39415>:28106:remote because either already completed(false) or originator no longer in the cluster(true). > {code} > However, even after this a successful response is sent to the originator: > {code} > 10:01:36,119 TRACE [org.infinispan.remoting.InboundInvocationHandlerImpl] (remote-thread-151) About to send back response null for command PrepareCommand {modifications=[PutKeyValueCommand{key=key_0000000000001318, value=[19 #1: 1195, ], flags=[SKIP_CACHE_LOAD, SKIP_REMOTE_LOOKUP], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedMetadata{version=null}, successful=true}], onePhaseCommit=false, gtx=GlobalTransaction:<edg-perf02-39415>:28106:remote, cacheName='testCache', topologyId=47} > {code} > Originator then expects that the transaction was successfully prepared: > {code} > 10:01:36,124 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-9) Responses: [sender=edg-perf01-36235, received=true, suspected=false] > [sender=edg-perf03-24110, received=true, suspected=false] > 10:01:36,135 TRACE [org.infinispan.transaction.TransactionCoordinator] (DefaultStressor-9) Committing transaction GlobalTransaction:<edg-perf02-39415>:28106:local > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5074?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5074: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1182140|https://bugzilla.redhat.com/show_bug.cgi?id=1182140] from ON_QA to ASSIGNED > Update remote query quickstart with the new annotation driven Protostream marshalling > ------------------------------------------------------------------------------------- > > Key: ISPN-5074 > URL: https://issues.jboss.org/browse/ISPN-5074 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5074) Update remote query quickstart with the new annotation driven Protostream marshalling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5074?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5074: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1182140|https://bugzilla.redhat.com/show_bug.cgi?id=1182140] from POST to ON_QA > Update remote query quickstart with the new annotation driven Protostream marshalling > ------------------------------------------------------------------------------------- > > Key: ISPN-5074 > URL: https://issues.jboss.org/browse/ISPN-5074 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: jdg > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5158) Transaction rolled back but returns successful response

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5158?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-5158: ------------------------------ Attachment: views.txt > Transaction rolled back but returns successful response > ------------------------------------------------------- > > Key: ISPN-5158 > URL: https://issues.jboss.org/browse/ISPN-5158 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Priority: Critical > Attachments: tx.txt, views.txt > > > When the cluster is merging, it is possible that a node is removed from the view although it is still responsive. Eventually the cluster is merged correctly, but since the node is reported as missing from the view, transaction originating from this node is rolled back. > {code} > 10:01:36,116 TRACE [org.infinispan.interceptors.TxInterceptor] (remote-thread-151) Rolling back remote transaction GlobalTransaction:<edg-perf02-39415>:28106:remote because either already completed(false) or originator no longer in the cluster(true). > {code} > However, even after this a successful response is sent to the originator: > {code} > 10:01:36,119 TRACE [org.infinispan.remoting.InboundInvocationHandlerImpl] (remote-thread-151) About to send back response null for command PrepareCommand {modifications=[PutKeyValueCommand{key=key_0000000000001318, value=[19 #1: 1195, ], flags=[SKIP_CACHE_LOAD, SKIP_REMOTE_LOOKUP], putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedMetadata{version=null}, successful=true}], onePhaseCommit=false, gtx=GlobalTransaction:<edg-perf02-39415>:28106:remote, cacheName='testCache', topologyId=47} > {code} > Originator then expects that the transaction was successfully prepared: > {code} > 10:01:36,124 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-9) Responses: [sender=edg-perf01-36235, received=true, suspected=false] > [sender=edg-perf03-24110, received=true, suspected=false] > 10:01:36,135 TRACE [org.infinispan.transaction.TransactionCoordinator] (DefaultStressor-9) Committing transaction GlobalTransaction:<edg-perf02-39415>:28106:local > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4770) PublicAPI doclet crashes when generics without type parameters are found

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4770?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4770: ----------------------------------------------- Misha H. Ali <mhusnain(a)redhat.com> changed the Status of [bug 1164688|https://bugzilla.redhat.com/show_bug.cgi?id=1164688] from ASSIGNED to POST > PublicAPI doclet crashes when generics without type parameters are found > ------------------------------------------------------------------------ > > Key: ISPN-4770 > URL: https://issues.jboss.org/browse/ISPN-4770 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 7.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR1 > > > The PublicAPI doclet crashes if it encounters a generic without a type parameter, e.g. List instead of List<Object>. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4769) XSD documentation generator does not handle some types (e.g. xs:list)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4769?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4769: ----------------------------------------------- Misha H. Ali <mhusnain(a)redhat.com> changed the Status of [bug 1164688|https://bugzilla.redhat.com/show_bug.cgi?id=1164688] from ASSIGNED to POST > XSD documentation generator does not handle some types (e.g. xs:list) > --------------------------------------------------------------------- > > Key: ISPN-4769 > URL: https://issues.jboss.org/browse/ISPN-4769 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 7.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR1 > > > The XSD documentation generator does not handle xs:list simpleTypes and doesn't show documentation for restrictions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4771) Combine doclets to avoid running javadocs multiple times

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4771?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4771: ----------------------------------------------- Misha H. Ali <mhusnain(a)redhat.com> changed the Status of [bug 1164688|https://bugzilla.redhat.com/show_bug.cgi?id=1164688] from ASSIGNED to POST > Combine doclets to avoid running javadocs multiple times > -------------------------------------------------------- > > Key: ISPN-4771 > URL: https://issues.jboss.org/browse/ISPN-4771 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Affects Versions: 7.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR1 > > > The PublicAPIDoclet and JMXDoclet doclets should be combined so that they only require one pass -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015