-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
P1
-
Affects Version/s: 1.4.2_18
-
Component/s: hotspot
-
x86
-
windows_nt
Dear all,
SAP is currently facing a critical issue from JDK 1.4.2_18. This affects the mainstream development and test environment. The problem is the limited stack size of 256KB, despite the command line options passed to the JVM with a magnitude of 2MB using the -Xss2m flag. The JVM is started via a native application (jlaunch.exe), which startes the JVM with the parameters which you could observe from the JVM crash log file. SAP reports these issues using an internal bug reporting system (CSN) and over the last 1 week, there has been several issues reported on exactly the same problem. The earlier version of JDK 1.4.2_17 was void of this bug, which seems to have crept in the latest release 1.4.2_18.
Though 1.4.2 is EOLed by Sun, SAP is a special customer for this product and we earn revenue for the support. So, I'd like to request you to process this issue with some exigency to avoid further delays. I have been able to confirm that this is a JDK specific bug and not an issue from the SAP application in the meantime. I've included the JVM crash log to this bug report. Please let me know if you need any additional information and provide me with an evaluation at the earliest to keep SAP on the loop and to avoid any escalations.
Thanks,
MS
SAP is currently facing a critical issue from JDK 1.4.2_18. This affects the mainstream development and test environment. The problem is the limited stack size of 256KB, despite the command line options passed to the JVM with a magnitude of 2MB using the -Xss2m flag. The JVM is started via a native application (jlaunch.exe), which startes the JVM with the parameters which you could observe from the JVM crash log file. SAP reports these issues using an internal bug reporting system (CSN) and over the last 1 week, there has been several issues reported on exactly the same problem. The earlier version of JDK 1.4.2_17 was void of this bug, which seems to have crept in the latest release 1.4.2_18.
Though 1.4.2 is EOLed by Sun, SAP is a special customer for this product and we earn revenue for the support. So, I'd like to request you to process this issue with some exigency to avoid further delays. I have been able to confirm that this is a JDK specific bug and not an issue from the SAP application in the meantime. I've included the JVM crash log to this bug report. Please let me know if you need any additional information and provide me with an evaluation at the earliest to keep SAP on the loop and to avoid any escalations.
Thanks,
MS