Message8275

There's a bug with the caching of the jline_.dll on windows. It's being cached in %TEMP% with the same name for both 32bit as well as 64bit versions of the VM. So if you're running a 32bit script at the same time as a 64bit script, you'll get an error along the lines of "Can't load IA 32-bit .dll on a AMD 64-bit platform" (since the second jython instance isn't rewriting the jline_.dll as it already exists and is in use by the 32bit version).

The workaround is to disable jline: -Dpython.console=org.python.util.InteractiveConsole. Obviously not very handy for interactive scripts but works well for batch scripts.

The simplest solution would be to suffix the name of the dll with _32 and _64 as appropriate to eliminate this conflict.