March 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2519) Test org.infinispan.loaders.decorators.BatchAsyncCacheStoreTest.indexWasStored fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2519?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2519: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 847158|https://bugzilla.redhat.com/show_bug.cgi?id=847158] from ON_QA to VERIFIED > Test org.infinispan.loaders.decorators.BatchAsyncCacheStoreTest.indexWasStored fails randomly > --------------------------------------------------------------------------------------------- > > Key: ISPN-2519 > URL: https://issues.jboss.org/browse/ISPN-2519 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.3.0.Alpha1 > > > The failure takes place in case of running testsuit for JDG. > Failure log: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > Another failure: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2519) Test org.infinispan.loaders.decorators.BatchAsyncCacheStoreTest.indexWasStored fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2519?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2519: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 847158|https://bugzilla.redhat.com/show_bug.cgi?id=847158] This bug doesn't appear anymore. Was verified for JDG 6.1.0.ER12 build. > Test org.infinispan.loaders.decorators.BatchAsyncCacheStoreTest.indexWasStored fails randomly > --------------------------------------------------------------------------------------------- > > Key: ISPN-2519 > URL: https://issues.jboss.org/browse/ISPN-2519 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.3.0.Alpha1 > > > The failure takes place in case of running testsuit for JDG. > Failure log: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > Another failure: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2512) org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2512?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2512: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 855343|https://bugzilla.redhat.com/show_bug.cgi?id=855343] This bug doesn't appear anymore. Is verified for JDG 6.1.0.ER12 build. > org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2512 > URL: https://issues.jboss.org/browse/ISPN-2512 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.3.0.Alpha1 > > > The test failed randomly during last Infinispan testsuite run on Rhel5_x86, OpenJDK6. > You can find the log here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > The bug doesn't appear when the test is run separately. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2512) org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2512?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2512: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 855343|https://bugzilla.redhat.com/show_bug.cgi?id=855343] from ON_QA to VERIFIED > org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2512 > URL: https://issues.jboss.org/browse/ISPN-2512 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.3.0.Alpha1 > > > The test failed randomly during last Infinispan testsuite run on Rhel5_x86, OpenJDK6. > You can find the log here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > The bug doesn't appear when the test is run separately. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2517) org.infinispan.statetransfer.StateTransferFileCacheLoaderFunctionalTest.testConcurrentStateTransfer fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2517?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2517: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 855352|https://bugzilla.redhat.com/show_bug.cgi?id=855352] from ON_QA to VERIFIED > org.infinispan.statetransfer.StateTransferFileCacheLoaderFunctionalTest.testConcurrentStateTransfer fails randomly > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2517 > URL: https://issues.jboss.org/browse/ISPN-2517 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 5.3.0.Final > > > The failure takes place in case of JDG test suire run on env: RHEL6_x86, IBM JDK6 > You can find the log here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2517) org.infinispan.statetransfer.StateTransferFileCacheLoaderFunctionalTest.testConcurrentStateTransfer fails randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2517?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2517: ----------------------------------------------- Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 855352|https://bugzilla.redhat.com/show_bug.cgi?id=855352] This bug doesn't appear anymore. Was verified for JDG 6.1.0.ER12 build. > org.infinispan.statetransfer.StateTransferFileCacheLoaderFunctionalTest.testConcurrentStateTransfer fails randomly > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2517 > URL: https://issues.jboss.org/browse/ISPN-2517 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 5.3.0.Final > > > The failure takes place in case of JDG test suire run on env: RHEL6_x86, IBM JDK6 > You can find the log here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2836) org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-2836?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-2836: -------------------------------- Hi Alan, I the POM for RadarGun, I can see that the Infinispan 5.2 plugin still uses Infinispan 5.2.0-SNAPSHOT. This is wrong and should be changed to 5.2.1.Final. I've tested that the combo Infinispan 5.2.1.Final / JGroups 3.3.0.Beta1 works. After this, you'd have to change the JGroups version (Infinispan 5.2.1 uses 3.2.7.Final) to 3.3.0.Beta1. > org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes > --------------------------------------------------------------------------------------------- > > Key: ISPN-2836 > URL: https://issues.jboss.org/browse/ISPN-2836 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.1.Final > Reporter: Alan Field > Assignee: Vladimir Blagojevic > Attachments: afield-tcp-521-final.txt, udp-edg-perf01.txt, udp-edg-perf02.txt > > > Using RadarGun and two nodes to execute the example WordCount Map/Reduce job against a cache with ~550 keys with a value size of 1MB is producing a thread deadlock. The cache is distributed with transactions disabled. > TCP transport deadlocks without throwing an exception. Disabling the send queue and setting UNICAST2.conn_expiry_timeout=0 prevents the deadlock, but the job does not complete. The nodes send "are-you-alive" messages back and forth, and I have seen the following exception: > {noformat} > 11:44:29,970 ERROR [org.jgroups.protocols.TCP] (OOB-98,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (76 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:352) > at org.radargun.cachewrappers.InfinispanMapReduceWrapper.executeMapReduceTask(InfinispanMapReduceWrapper.java:98) > at org.radargun.stages.MapReduceStage.executeOnSlave(MapReduceStage.java:74) > at org.radargun.Slave$2.run(Slave.java:103) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.concurrent.ExecutionException: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.distexec.mapreduce.MapReduceTask$TaskPart.get(MapReduceTask.java:832) > at org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(MapReduceTask.java:477) > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:350) > ... 9 more > Caused by: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.infinispan.util.Util.rewrapAsCacheException(Util.java:541) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:186) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515) > 11:44:29,978 ERROR [org.jgroups.protocols.TCP] (Timer-3,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (60 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:175) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:197) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:254) > at org.infinispan.remoting.rpc.RpcManagerImpl.access$000(RpcManagerImpl.java:80) > at org.infinispan.remoting.rpc.RpcManagerImpl$1.call(RpcManagerImpl.java:288) > ... 5 more > Caused by: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:390) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:301) > 11:44:29,979 ERROR [org.jgroups.protocols.TCP] (Timer-4,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (63 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:179) > ... 11 more > {noformat} > With UDP transport, both threads are deadlocked. I will attach thread dumps from runs using TCP and UDP transport. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2836) org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-2836?page=com.atlassian.jira.plugin.... ] Bela Ban updated ISPN-2836: --------------------------- Comment: was deleted (was: I see, you're running an older Infinispan version. Use the one which has JGroups 3.2.7 (or 3.2.6) in it.) > org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes > --------------------------------------------------------------------------------------------- > > Key: ISPN-2836 > URL: https://issues.jboss.org/browse/ISPN-2836 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.1.Final > Reporter: Alan Field > Assignee: Vladimir Blagojevic > Attachments: afield-tcp-521-final.txt, udp-edg-perf01.txt, udp-edg-perf02.txt > > > Using RadarGun and two nodes to execute the example WordCount Map/Reduce job against a cache with ~550 keys with a value size of 1MB is producing a thread deadlock. The cache is distributed with transactions disabled. > TCP transport deadlocks without throwing an exception. Disabling the send queue and setting UNICAST2.conn_expiry_timeout=0 prevents the deadlock, but the job does not complete. The nodes send "are-you-alive" messages back and forth, and I have seen the following exception: > {noformat} > 11:44:29,970 ERROR [org.jgroups.protocols.TCP] (OOB-98,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (76 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:352) > at org.radargun.cachewrappers.InfinispanMapReduceWrapper.executeMapReduceTask(InfinispanMapReduceWrapper.java:98) > at org.radargun.stages.MapReduceStage.executeOnSlave(MapReduceStage.java:74) > at org.radargun.Slave$2.run(Slave.java:103) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.concurrent.ExecutionException: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.distexec.mapreduce.MapReduceTask$TaskPart.get(MapReduceTask.java:832) > at org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(MapReduceTask.java:477) > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:350) > ... 9 more > Caused by: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.infinispan.util.Util.rewrapAsCacheException(Util.java:541) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:186) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515) > 11:44:29,978 ERROR [org.jgroups.protocols.TCP] (Timer-3,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (60 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:175) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:197) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:254) > at org.infinispan.remoting.rpc.RpcManagerImpl.access$000(RpcManagerImpl.java:80) > at org.infinispan.remoting.rpc.RpcManagerImpl$1.call(RpcManagerImpl.java:288) > ... 5 more > Caused by: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:390) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:301) > 11:44:29,979 ERROR [org.jgroups.protocols.TCP] (Timer-4,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (63 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:179) > ... 11 more > {noformat} > With UDP transport, both threads are deadlocked. I will attach thread dumps from runs using TCP and UDP transport. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2836) org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-2836?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-2836: -------------------------------- I see, you're running an older Infinispan version. Use the one which has JGroups 3.2.7 (or 3.2.6) in it. > org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes > --------------------------------------------------------------------------------------------- > > Key: ISPN-2836 > URL: https://issues.jboss.org/browse/ISPN-2836 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.1.Final > Reporter: Alan Field > Assignee: Vladimir Blagojevic > Attachments: afield-tcp-521-final.txt, udp-edg-perf01.txt, udp-edg-perf02.txt > > > Using RadarGun and two nodes to execute the example WordCount Map/Reduce job against a cache with ~550 keys with a value size of 1MB is producing a thread deadlock. The cache is distributed with transactions disabled. > TCP transport deadlocks without throwing an exception. Disabling the send queue and setting UNICAST2.conn_expiry_timeout=0 prevents the deadlock, but the job does not complete. The nodes send "are-you-alive" messages back and forth, and I have seen the following exception: > {noformat} > 11:44:29,970 ERROR [org.jgroups.protocols.TCP] (OOB-98,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (76 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:352) > at org.radargun.cachewrappers.InfinispanMapReduceWrapper.executeMapReduceTask(InfinispanMapReduceWrapper.java:98) > at org.radargun.stages.MapReduceStage.executeOnSlave(MapReduceStage.java:74) > at org.radargun.Slave$2.run(Slave.java:103) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.util.concurrent.ExecutionException: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.distexec.mapreduce.MapReduceTask$TaskPart.get(MapReduceTask.java:832) > at org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(MapReduceTask.java:477) > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:350) > ... 9 more > Caused by: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.infinispan.util.Util.rewrapAsCacheException(Util.java:541) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:186) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515) > 11:44:29,978 ERROR [org.jgroups.protocols.TCP] (Timer-3,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (60 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:175) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:197) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:254) > at org.infinispan.remoting.rpc.RpcManagerImpl.access$000(RpcManagerImpl.java:80) > at org.infinispan.remoting.rpc.RpcManagerImpl$1.call(RpcManagerImpl.java:288) > ... 5 more > Caused by: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:390) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:301) > 11:44:29,979 ERROR [org.jgroups.protocols.TCP] (Timer-4,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (63 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:179) > ... 11 more > {noformat} > With UDP transport, both threads are deadlocked. I will attach thread dumps from runs using TCP and UDP transport. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2880) infinispan documentation discrepancy (keyset)

by Aleksandar Kostadinov (JIRA)

Aleksandar Kostadinov created ISPN-2880: ------------------------------------------- Summary: infinispan documentation discrepancy (keyset) Key: ISPN-2880 URL: https://issues.jboss.org/browse/ISPN-2880 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.2.2.Final Reporter: Aleksandar Kostadinov Assignee: Mircea Markus I'm seeing some discrepancy between documentation [1] and API docs [2]. In documentation the keySet() and other methods are listed as limited to local cache. In API docs they are only listed as prohibitively expensive but from the wording they seem NOT limited to local cache. I think these both docs need to be put in sync by somebody that knows how it actually works. [1] https://docs.jboss.org/author/display/ISPN/Using+the+Cache+API#UsingtheCa... [2] http://docs.jboss.org/infinispan/5.2/apidocs/org/infinispan/api/BasicCach... -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2013