IV58794: JAVA JIT - EXCESSIVE COMPILATION REQUESTS FOR A SINGLE METHOD.
Closed as program error.
Error Message: The JIT verbose log shows several compilation requests for the same method, in comes cases the number of requests can be in the hundreds of thousands. . Stack Trace: N/A . The problem exists, but it has never shown to be a problem for any customers. There is a small overheard for handling the compilation requests but it seems that the overhead is not enough to be noticeable. We fixed this as a precaution more then out of any belief that it has any significant effect on performance.The problem only exists on x86 and z architectures. The PPC architecture is not effected by this issue.The issue only effects performance, it is NOT a functional issue.
The JIT will queue for compilation any previously compiled method that shows a runtime history of taking exception paths. We do this so we can try and better optimize the exception paths. If for some reason the method is unable to be re-compiled in a timely manor (i.e. code cache is full or there is already a long compile queue) then each execution of the exception path will result in a compilation request.
This APAR will be fixed in the following Java Releases: 7 SR7 (184.108.40.206) 6 R1 SR8 (220.127.116.11) 6 SR16 (18.104.22.168) 7 R1 SR1 (22.214.171.124) . The JIT was modified such that only one attempt to queue a method for compilation will be made one exception paths.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels