The 188.8.131.52 build of Saxon has been in place for almost
2 weeks and we have not seen any ArrayIndexOutOfBoundsException being thrown
since. I do have a could of questions:
1. Was there any changes to the code which was involved
in the ArrayIndexOutOfBoundsException - aside from the debugging output should
this error happen?
2. Is this version of Saxon a stable release? We
will likely continue to use this version, even though I am a bit nervous since I
cannot purposly cause this error to happen with the older versions of saxon...
This has been an interesting bug (most likely
with the JVM not Saxon)... :)
Yes, it did occur to me that if this is a JVM bug, then
adding the diagnostic code may cause the bug to disappear. (A Heisenbug, I
like that term).
I haven't done anything else that could cause the bug to
disappear, so I think this would be fairly solid confirmation that it's the
JVM. Not sure what we do then. If there's solid evidence of a JVM bug I'm
prepared to put in a circumvention to avoid it, but I'm reluctant to do it on
the basis of a wild guess.
The 184.108.40.206 build of Saxon has been installed and the
application has been running for 3 days without running into this
"ArrayIndexOutOfBoundsException" exception. I'll let you know if it
happens and what the debugging output looks like. Typically, by now
the problem has occurred. I'm wondering if the JVM does some
optimization of the loop which iterates through the hash and if putting
this try/catch in this code possibly caused the JVM to not do the
optimization - but really this is just a very weak hypothesis on my
part. Just because it hasn't happened yet doesn't mean it
wont. Time will tell.
I'll keep you updated.
Thanks for all your help thus