-
Bug
-
Resolution: Fixed
-
P1
-
1.3.0_03, 1.3.1
-
05
-
sparc
-
solaris_8
The customer is currently seeing a problem with iPlanet Web Server 6.0sp2 stability when using the JDK1.3.1_02 and JDK1.3.1_03. Their test case and pre-production application both crash the ns-httpd process when using JDK 1.3.1, but not with JDK1.2.2 or with JDK1.4.0. Customer needs to be on JDK1.3.1 due to slower performance when using JDK1.2.2 and also with some problems with CORBA implementation with socket handling.
We've been able to isolate the problem down to a difference in JDK versions that affect stability of the application running on iWS6.0sp2. Without any application changes or iWS configuration changes, the application runs stable on JDK1.2.2_08 in the customer's environment, but when they go to JDK1.3.1_03, the ns-httpd process is crashing on a consistent basis.
When running Apache/Tomcat with JDK1.3.1, the customer is also seeing stability issues, but not with JDK1.2.2 and JDK1.4.0. The error messages and crashes are similar.
The customer believes that the problem is primarily with JDK1.3.1's JVM.
Mon Jun 17 18:58:03 MDT 2002 rn104575
Mon Jun 17 18:59:20 MDT 2002 rn104575
We've been able to isolate the problem down to a difference in JDK versions that affect stability of the application running on iWS6.0sp2. Without any application changes or iWS configuration changes, the application runs stable on JDK1.2.2_08 in the customer's environment, but when they go to JDK1.3.1_03, the ns-httpd process is crashing on a consistent basis.
When running Apache/Tomcat with JDK1.3.1, the customer is also seeing stability issues, but not with JDK1.2.2 and JDK1.4.0. The error messages and crashes are similar.
The customer believes that the problem is primarily with JDK1.3.1's JVM.
Mon Jun 17 18:58:03 MDT 2002 rn104575
Mon Jun 17 18:59:20 MDT 2002 rn104575
- duplicates
-
JDK-4739594 JVM_handle_solaris_signal calling unknown userland routine when handling SIGPIPE
- Closed