Old deployment failing on new hardware any clues you can give me as to why this might be? about activiti HOT 2 OPEN

Further investigation shows that it comes down to finding the task by candidate user i.e. it works when I comment out the line to match candidate users in ActivitiiService.groovy. As I said, the database contents haven't changed, the code hasn't changed. It's just a db export re-imported onto a new box and an existing war file put in a new Tomcat. Any clue as to what happens in this line that might fail when moving hardware?

Task getUnassignedTask(String username, String processInstanceId) {
	getTask("taskCandidateUser", username, processInstanceId)
}

private getTask(String methodName, String username, String processInstanceId) {
	taskService.createTaskQuery()
	.processInstanceId(processInstanceId)
	// THE LINE THAT MAKES THE DIFFERENCE ."${methodName}"(username)
	.singleResult()
}	

from activiti.

Please feel free to close this bug. I eventually found that the issue came down to load order between the activiti plugin and the activity-spring-security plugin as described here:

limcheekin/activiti-spring-security@895ea3c

from activiti.