Hmm. Well, I thought it was fixed in 9.0.1. Apparently it isn’t - at least for some people (two so far on this thread). I need to test it again and see.
I ran into this problem last week. Worked fine on my dev machine (single instance on mac an windows) but popped up on a multiserver clustered box (windows). Luis and I banged our heads for a while before we tracked it down. I’m running 9.01 as well. Fixed by declaring the criteria before calling the ORM method. I believe this is a CF bug.
So you are saying this bug only affects Windows (and not *nix) machines, and only with a JRun multi-instance (and not “server”) installation? If yes, do you know if it still exists on Windows under another J2EE server or servlet container (e.g. Glassfish, JBoss, Tomcat, etc.)?
… failed for you in Windows multi-server installation?
If that is the case, then there is definitely more to it than that. I am running that configuration on multiple servers, and my example works exactly as expected.
If you have some other easily testable example that fails, please pass along so that I can test on my machines, too.
When I reported this bug to Adobe 2 years ago, this would not be server install specific. And it would not work in instances like this.
public any function getCategories(event, tempTest = []) {
or
getCategories(event, []);
or
public any function getCategories(event, tempTest = {}) {
getCategories(event, {test1=1,test2=2});
Some of this has been fixed, but there are certain conditions that are not fixed. Have come across them on 9.01 many times myself, and this is on both standalone and mutlserver, j2ee installs I have seen them on.