This content has been marked as final. Show 5 replies
What you describe smells like a bug to me. But why 1.6._014, that is so old it was still released by Sun! Your problem may well be fixed in any of the dozen releases that came after it.
Unfortunitly our test and release cycle are long and complex so to upgrade would need some justification. One other aspect we are thinking about is what processing is done to the JAR files cached on the PC. Assuming the JAR files are the latest, so the server would not resend them, what processing does the JRE initially with the cached JAR files, remembering we sign the JAR files and have a policy file.
The other angle is that the anti virus software is causing a massive delay by scanning the JAR files or some other set of files. Has anyone had issues in this area?
Need to make an adjustment to the explanation, as we have some more information. We thought the issue was with the upgrade to 1.6.0_14, however, the upgrade coincided with a 25% increase in web sites using JRE, causing a corresponding increase to the content of the policy file. The increase was caused by the web sites moving from Jinitiator to JRE. So we rebuilt a PC using JRE 1.5.0_05, but with the large policy file we released with 1.6.0_14; we found the problem exists in 1.5.0_05 just as it does in 1.6.0_14.
We tried increasing the memory allocations (-Xss, -Xms, -Xmx & -Xmn) but with no improvements. We have also pretty much knocked on the head any adverse anti-virus scanning.
Any ideas would be appreciated.
Yeah, I already gave it. Try a newer version than release 14 as it is still ancient software you are using which is bound to have many flaws that have been fixed already. If the problem persists, report it (if you can, the bug parade is very unstable at the moment unfortunately).
We have now tried the tests with JRE 1.6.0_29 with no change in performance, the issue is still there.
We now have an Oracle SR open, number 3-4964457421. I'll push out the findings when we have some although any other ideas are welcome.