April 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4217) Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-4217: ----------------------------------------- Summary: Use ArrayList instead of LinkedList for DeltaAware and Delta in M/R Key: ISPN-4217 URL: https://issues.jboss.org/browse/ISPN-4217 Project: Infinispan Issue Type: Enhancement Components: Distributed Execution and Map/Reduce Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Investigate switching to ArrayList as implementation of DeltaAware and Delta as ArrayList uses less memory than LinkedList. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4204) Sync distexec demo project with current test code

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4204?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4204: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha4 Resolution: Done > Sync distexec demo project with current test code > ------------------------------------------------- > > Key: ISPN-4204 > URL: https://issues.jboss.org/browse/ISPN-4204 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 6.0.2.Final, 7.0.0.Alpha3 > Reporter: Alan Field > Assignee: Alan Field > Fix For: 7.0.0.Alpha4 > > > Add a no argument constructor to WordCountCollator > Add a new distributed executor that performs a regular expression search of the values in the cache -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4216) Use IGNORE_RETURN_VALUES flag for inserting keys/values in M/R intermediate cache

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-4216: ----------------------------------------- Summary: Use IGNORE_RETURN_VALUES flag for inserting keys/values in M/R intermediate cache Key: ISPN-4216 URL: https://issues.jboss.org/browse/ISPN-4216 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Whenever data gets inserted in intermediate cache unsafeReturnValues setting is ignored and previous value from cache is returned every time we do cache#put. We did not experience this slowdown before because we only inserted once per key in intermediate cache put. Now that we do partial batching and transfer of these keys/values, we really hit the wall there with multiple insertions. Adding IGNORE_RETURN_VALUES flag to put invocation is the key to resolve this issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4213) clustered Wildfly unexpected nodes SuspectException

by Hielke Hoeve (JIRA)

[ https://issues.jboss.org/browse/ISPN-4213?page=com.atlassian.jira.plugin.... ] Hielke Hoeve commented on ISPN-4213: ------------------------------------ Restarting the suspected node after waiting more than 2 hours does not cause the nodes to rediscover each other. Nor do they rediscover each other when restarting each node consecutively. They give no warning, error of info. > clustered Wildfly unexpected nodes SuspectException > --------------------------------------------------- > > Key: ISPN-4213 > URL: https://issues.jboss.org/browse/ISPN-4213 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Environment: ubuntu 13.04, jboss wildfly 8.0.1, infinispan 6.0.1.Final, jgroups 3.4.3.Final > Reporter: Hielke Hoeve > Assignee: Dan Berindei > > Our current production system has a cluster of 2 nodes using Wildfly 8.0.1. We have used the "ha" profile and "ha" socket-binding-group as a baseline to create the profile for the clusters. The cluster has a REST application deployed. This application uses 2 infinispan cache containers (hibernate and application). In total these views have 5 local caches, 3 invalidation caches and 7 replicated caches. The cache containers use udp as transport. Our hibernate container is the default config as provided by the "ha" profile. > Last thursday and yesterday the one of the nodes started throwing SuspectException during a hibernate flush. The applications had only a few active users. > Node 1 says: > ----------------- > 2014-04-15 17:40:53,380 ERROR [org.jboss.as.ejb3.invocation] (default task-22) JBAS014134: EJB Invocation failed on component ConversatieResourceRESTService > for method public javax.ws.rs.core.Response ...ConversatieResourceRESTService.setStatus(...event.Con > versatieStatusObject): javax.ejb.EJBTransactionRolledbackException: Transaction rolled back > ... > ... > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:70) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:333) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1306) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.CacheImpl.putInternal(CacheImpl.java:878) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.CacheImpl.put(CacheImpl.java:870) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.DecoratedCache.put(DecoratedCache.java:401) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.infinispan.AbstractDelegatingCache.put(AbstractDelegatingCache.java:276) [infinispan-core-6.0.1.Final.jar:6.0.1.Final] > at org.hibernate.cache.infinispan.access.TransactionalAccessDelegate.update(TransactionalAccessDelegate.java:192) [hibernate-infinispan-4.3.4.Final.j > ar:4.3.4.Final] > at org.hibernate.cache.infinispan.entity.TransactionalAccess.update(TransactionalAccess.java:89) [hibernate-infinispan-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.action.internal.EntityUpdateAction.cacheUpdate(EntityUpdateAction.java:234) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.action.internal.EntityUpdateAction.execute(EntityUpdateAction.java:209) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:461) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:347) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:350) [hibernate-core-4.3.4.Final.j > ar:4.3.4.Final] > at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:56) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1222) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:425) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorNonTrackingImpl.beforeCompletion(SynchronizationCallba > ckCoordinatorNonTrackingImpl.java:110) [hibernate-core-4.3.4.Final.jar:4.3.4.Final] > ... 117 more > Caused by: SuspectedException > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:406) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:353) [infinispan-core-6.0.1.F > inal.jar:6.0.1.Final] > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:167) [infinispan-core-6.0.1 > .Final.jar:6.0.1.Final] > ... 161 more > 2014-04-15 17:40:53,707 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-7,shared=udp) ISPN000094: Received new cluster view: [node1:rest1-even/hibernate-even|2] (1) [node1:rest1-even/hibernate-even] > 2014-04-15 17:40:53,707 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-14,shared=udp) ISPN000094: Received new cluster view: [node1:rest1-even/application-even|2] (1) [node1:rest1-even/application-even] > Node 2 says: > ----------------- > 2014-04-15 17:40:17,934 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-19,shared=udp) ISPN000094: Received new cluster view: [node2:rest2-even/hibernate-even|2] (1) [node2:rest2-even/hibernate-even] > 2014-04-15 17:40:17,934 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-17,shared=udp) ISPN000094: Received new cluster view: [node2:rest2-even/application-even|2] (1) [node2:rest2-even/application-even] > ... > ... > 2014-04-15 17:40:50,737 WARN [org.jgroups.protocols.UDP] (Timer-2,shared=udp) JGRP000032: null: no physical address for node1:rest1-even/hibernate-even, dropping message > 2014-04-15 17:40:52,543 WARN [org.jgroups.protocols.UDP] (Timer-5,shared=udp) JGRP000032: null: no physical address for node1:rest1-even/application-even, dropping message > (repeats 100 times) > ... > Is there any way I can get more logging than the WARNs above? Does anyone have pointers how or when this SuspectException is thrown? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4215) Synchronize series in report by date

by Radim Vansa (JIRA)

Radim Vansa created ISPN-4215: --------------------------------- Summary: Synchronize series in report by date Key: ISPN-4215 URL: https://issues.jboss.org/browse/ISPN-4215 Project: Infinispan Issue Type: Enhancement Reporter: Radim Vansa Assignee: Mircea Markus Priority: Minor If I have two series; series A with 3 executions on 1st April, 5th April and 10th April, and series B with 2 executions on 2nd April and 12th April, the charts will be as A having datapoints at 0 - 2, and B having datapoints at 0 and 1. I'd prefer A to have datapoints 0, 2 and 3, and B having datapoints 1 and 4. The line in chart should ignore non-existent datapoints and go directly to the next execution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4214) Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4214?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-4214: ------------------------------------- Affects also cluster loader. > Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute > ---------------------------------------------------------------------------------------- > > Key: ISPN-4214 > URL: https://issues.jboss.org/browse/ISPN-4214 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final, 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > This will be a problem when the server gets rebased to latest WildFly components - where it will fail to parse the whole configuration due to an exception being thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4214) Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4214?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4214: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1088214 > Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute > ---------------------------------------------------------------------------------------- > > Key: ISPN-4214 > URL: https://issues.jboss.org/browse/ISPN-4214 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final, 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > This will be a problem when the server gets rebased to latest WildFly components - where it will fail to parse the whole configuration due to an exception being thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4214) Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4214?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4214: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2507 > Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute > ---------------------------------------------------------------------------------------- > > Key: ISPN-4214 > URL: https://issues.jboss.org/browse/ISPN-4214 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final, 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > This will be a problem when the server gets rebased to latest WildFly components - where it will fail to parse the whole configuration due to an exception being thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4214) Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4214?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4214: -------------------------------- Description: This will be a problem when the server gets rebased to latest WildFly components - where it will fail to parse the whole configuration due to an exception being thrown. (was: The "shared" attribute cannot be set due to missing break statement in the parsing method.) > Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute > ---------------------------------------------------------------------------------------- > > Key: ISPN-4214 > URL: https://issues.jboss.org/browse/ISPN-4214 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final, 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > This will be a problem when the server gets rebased to latest WildFly components - where it will fail to parse the whole configuration due to an exception being thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4214) Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4214?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4214: -------------------------------- Summary: Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute (was: Custom cache store and cache loader ignore "shared" attribute in server configuration) > Custom cache store and cache loader sets SHARED attribute to the value of NAME attribute > ---------------------------------------------------------------------------------------- > > Key: ISPN-4214 > URL: https://issues.jboss.org/browse/ISPN-4214 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final, 7.0.0.Alpha3 > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > The "shared" attribute cannot be set due to missing break statement in the parsing method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 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 April 2014