[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-2262: ----------------------------------- In fact, I am not sure what to do with this. I have similar issues both on 5.1.7.-redhat-1. When I prolonged the test duration for older "marked as working" resilience tests I sometimes get really a lot of exceptions, e.g. I have noticed that some node did not unlocked some key (and other nodes fail requesting it), or just the timeouts... I don't think I can solve the problem without any help. Could someone take a brief look on the enclosed logs, or should I produce some logs from 5.1.7? Usually these are huge (gigabytes on trace level for org.infinispan.*). -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2262: ---------------------------------------- @Radim, the logs you posted are generated with which Infinispan version? -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-2262: ------------------------------ Affects Version/s: (was: 5.1.6.FINAL) -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-2262: ----------------------------------- Well, I've generated another situation without so many exceptions but where the newly started cache waits for state transfer (and it does not happen). I have uploaded the logs (again pretty big) on http://dl.dropbox.com/u/103079234/serverlogs_waiting.zip -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-2262: ----------------------------------- Is some additional feedback required? We cannot continue with 5.2 testing until this problem is resolved. -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2262: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1307 -- 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

[ https://issues.jboss.org/browse/ISPN-2262?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-2262 at 9/13/12 8:45 AM: ------------------------------------------------------------- A node can receive a message from a joiner before it has installed a JGroups view that contains the joiner. If it tries to send a response immediately, it will fail with a SuspectException. And since we don't retry sending state, the joiner will never finish the state transfer. The fix is to wait for the local node to install the new JGroups view before handling any state request. This can be done indirectly, by waiting on the new CacheTopology instead. was (Author: dan.berindei): A node can receive a message from a joiner before it has installed a JGroups view that contains the joiner. If it tries to send a response immediately, it will fail with a SuspectException. And since we don't retry sending state, the joiner will never finish the state transfer. -- 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