32-bit Java.exe breaks with -Xmx parameters with EMET policy

[Jwalker107]

Not an issue with the Fixlet itself, but probably worth a warning. Java.exe command line parameters -Xms and -Xmx configure minimum and maximum memory allocations available to Java. When using 32-bit Java.exe with a -Xmx1024m (or any value larger than ~ 750 MB), java.exe fails to launch with a message
Error occurred during initialization of VM
Could not reserve enough space for 1048576KB object heap

There is a warning on Microsoft's EMET policy page that EMET may not be compatible with the -Xmx parameter, but it's not clear that the only workaround is to completely remove java.exe from the configuration baseline. Disabling every available mitigation on the java.exe definition was not effective in working around the problem, I had to remove java.exe entirely.

I've tested 64-bit Java with allocations up to -Xmx16535m successfully with the EMET policy in place, only reproduced this on 32-bit Java.