> I am not familiar with the underlying details of the JRE. Does this mean there is something an application programmer can set as a workaround, or does that mean that there is something that folks at Oracle can change to make a future JRE build not suffer from this problem? No, this has to be fixed in the code. -DrD-