This content has been marked as final. Show 4 replies
Sorry for the bump but this one was over holidays and there weren't too many people logged in :)
> - MX 6.1 is subjected to this issue, where tests on the same machine with 7.02
> work fine.
I suspect you've answered your own question. There was a bug in 6.1 that
was fixed in 7. So the remedy for you would be to upgrade to 7.
Not sure what else needs commenting on..?
Good troubleshooting, btw!
Well this doesnt help the problem since we have many clients who are on 6.1 and of course a CF7 upgrade is not free :)
> Well this doesnt help the problem since we have many clients who are on 6.1 and of course a CF7 upgrade is not free :)
Why don't you check which JVM CFMX7 uses - I presume it's a newer one than
CFMX6.1 - and use that instead? I doubt it's actually anything to do with
CF, per se, as CF does not work @ the level that issues like hyperthreading
running/not running would be an issue.