Hide Forgot
project_key: EDG there was a regression: https://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-build-alt/41/testReport/junit/org.jboss.test.cluster.datagrid.test/ (testcases testNoReply*) for the infinispan snapshot version: 4.2.2-SNAPSHOT-20110418.174252 edg build: http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-build-fast/16/artifact/edg-ispn-4.2.2-SNAPSHOT.zip I'm working on the steps to reproduce
this might be related: echo -e "delete a noreply\r" | nc localhost 11211 produces SERVER_ERROR java.lang.NullPointerException
it seems as delete command inherits noreply flag from previous command with noreply: {code} $ echo -e "set a 0 0 1\r\na\r\ndelete a\r\ndelete a\r\ndelete a\r\ndelete a\r\n" | nc localhost 11211 STORED DELETED NOT_FOUND NOT_FOUND NOT_FOUND $ echo -e "set a 0 0 1 noreply\r\na\r\ndelete a\r\ndelete a\r\ndelete a\r\ndelete a\r\n" | nc localhost 11211 $ {code}
and therefore all testNoReply* tests get read timeout because they expect some reply from delete command in tearDown().
This could well be a regression as a result of the changes I made in the decoder to reduce memory consumption. I had to change quite a few things around. I'll create an ISPN jira to investigate this.
Link: Added: This issue depends ISPN-1083
Michal, I solved this yesterday while travelling back to Switzerland. In fact there're two issues but I've just bundled them into one. As you rightly guessed, on one side old parameters were being leaked into next request if the latter one did not have any extra params. On top of that there was the NPE with no reply. I've now added a listener that verifies that after a noreply op, the operation in the cache has been executed.
The new snapshot 4.2.2-20110509.161652 solved the problem: http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-build-alt/53/testReport/ that existed in previous run: http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-build-alt/52/testReport/
Docs QE Status: Removed: NEW