This content has been marked as final. Show 6 replies
Better to submit bugs at Feature Request/Bug Report Form.
Although this bug has already been submitted as 71432. You can watch for the next cf8 cumulative hot fix to see if it is resolved there or in cf8.01 (in beta). I will try to post if I see it is fixed.
Thank you so much for the answer.
There were updates to GetPageContext that improve performance, generally. But they cause this issue. You can workaround this error by setting the property coldfusion.markResetForMultiPart=false.
You set the jvm argument as -Dcoldfusion.markResetForMultiPart=false
or programatically set it as:
sys = createObject("java","java.lang.System");
It is better to set it as a JVM argument since the script does impact the whole CF server. There will be some loss of performance for fileupload. It will remain similar to cfmx7 performance with this property set false.
Ken, thank you for the answer.
I tried both solutions but the problem persists.
I found a post in the "Coldfused?" blog about the new upload code in CF8:
There, the solution proprosed to use the old upload code from CF mx7 is to set the argument markResetForMultiPart to true:
I would like to remind you that we use the enctype=”multipart/form-data” in the form, however uploading or not a file we get this exception. I don’t thinl our problem is related with the size of the file.
Do you know any other workaround for this problem?
Thank you in advance,
Apparently, the new Coldfusion 8 update 1 (8.0.1) resolved the problem.
I did some tests with the code above and with another one more complex and none problem occurred.
I think this bug can be marked as resolved.
Maiquel Sampaio de Melo
The Coldfusion 8 has not fixed the problem.
You gotta do a combination of things to get this problem solved.
Indeed you need to have the version 8.0.1 running, but it must be running on the JRE 184.108.40.206 and you must also set in the JVM the argument -Dcoldfusion.markResetForMultiPart=true (not false as mentioned above).
It was a nightmare to figure out all this, I hope adobe get this fixed in the next hot fixes. This is nothing something easy to get it fix, and can drive a man mad!
I hope no one besides us have faced this problem!