Lee, can you clarify the version you changed to? To be clear, the JVM built into CF was indeed an “official oracle JDK JRE”, albeit not the latest. It’s 1.6.0_29, as installed by Adobe.
So are you saying you updated to a later 1.6? Or do you mean you applied Update 8, and then installed a 1.7 JDK? And if so, which version of that?
And for the sake of others reading this and thinking that that change alone may help something, are you confirming that you changed NOTHING ELSE? Not even any JVM arguments or the GC algorithm? Would be interesting to hear if just an upgrade of the JVM alone had some beneficial impact.
I would note one last possibility: it could be that when you made the change, something ELSE was affected—not so much by the change in the version of the JVM but just in the change of the location of the JVM. By that I mean, there are things that CF uses within the location of the JVM (like the keystore) which would change in the installation of a new JVM (to use the keystore in the new JVM’s location).
I realize you won’t care to “go back” now, since things seem to be working. But I would note that if someone else may be considering this, and they did find that an “updated JVM” did somehow “fix” things, it could be interesting (as a technical curiosity) to see if things would also be “fixed” if you installed 1.6.0_29 also (the same version that CF10 uses by default) and changed CF to point to that.
If things were indeed still “fixed”, then it would indicate that just changing the location was the solution. It would then be really interesting to know then what about the old location caused a problem. Could be a permissions issue. Could be some files it was reading/writing that are not brought forward. Could be anything, really. Just something to consider.
I appreciate, Lee, that you want mainly just to suggest people consider a JVM update if things are amiss. It could well help. But if you can clarify the version, knowing that could even more.
/charlie