This error should no longer be occuring, at least it does not for us. I'm guessing Adobe fixed it or it is from one of the more recent Java updates.
You might be able to fix it on your end by updating to the most recent version of CF or updating to the following java versions, which we have installed on our production server:
Java 7 Update 25 (64-bit)
Java SE Development Kit 7 Update 17 (64-bit)
Java SE Development Kit 7 Update 25 (64-bit)
Java 6 Update 39 (64-bit)
Java SE Development Kit 6 Update 38 (64-bit)
Java SE Development Kit 6 Update 39 (64-bit)