A fix is available
APAR status
Closed as program error.
Error description
Error Message: N/A . Stack Trace: N/A . N/A
Local fix
N/A
Problem summary
When two different JVMs connect to the same shared class cache and the first one uses -Xnoaot, it's sometimes possible that the startup time for the second JVM be somewhat (5-15%) longer. A typical scenario is WebSphere Application Server when used in conjunction with a NodeAgent. The problem is more pronounced on systems with limited number of CPUs (1-2).
Problem conclusion
The JIT compiler has been fixed to eliminate this intermittent startup performance issue . This APAR will be fixed in the following Java Releases: 7 R1 SR1 FP1 (7.1.1.1) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, Java maintenance is available from: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IV61564
Reported component name
JIT
Reported component ID
620700124
Reported release
130
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-06-16
Closed date
2014-06-19
Last modified date
2014-07-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JIT
Fixed component ID
620700124
Applicable component levels
R130 PSY
UP
[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130"}]
Document Information
Modified date:
01 October 2021