I uploaded this security fix today, but from looking at the code hadn't predicted it'd cause this behavior. I'll roll it back tomorrow (it's after 2am here).
Meanwhile, can anyone provide a backtrace or other sorts of trace data that indicates why java is being broken by the fix to this security issue? Might help in narrowing down which of the five security patches caused the problem...
I uploaded this security fix today, but from looking at the code hadn't predicted it'd cause this behavior. I'll roll it back tomorrow (it's after 2am here).
Meanwhile, can anyone provide a backtrace or other sorts of trace data that indicates why java is being broken by the fix to this security issue? Might help in narrowing down which of the five security patches caused the problem...
Bryce