Details
Description
OS : Solaris 2.7, win32
The following test suite fails to run against kestrel.
/net/anybodys/export2/ejb-test/ejb-MASTER-test
Steps to reproduce :
1.Download and install J2EE bundle from /usr/local/java/j2sdkee1.2/bundles
2.Run J2EE Server : set JAVA_HOME to JDK (kestrel build R or P) root and J2EE_HOME to the root of the installation directory.
3.Checkout Test Workspace from /net/anybodys/export2/ejb-test/ejb-MASTER-test
4.Set TEST_HOME to <TestWorkSpaceRoot>/test
5.set JAVA_HOME to JDK root(kestrel build R or P) in file :
<TestWorkSpaceRoot>/test/unixDefs.mk or
<TestWorkSpaceRoot>/test/win32Defs.mk for windows
6.Go to the corresponding run request directory
cd <TestWorkSpaceRoot>/work/webAutomation/runReqs/j2ee
7.Run corresponding Web Tests Setup file
. ./setMe.sh for Solaris
setMe.bat for windows
8.Run runWebTests script
sh runWebTests
(See http://javaweb/~rameshm/J2EE/webAutomation.html for detailed instructions).
These tests run fine with cricket jdk (1.2.2 w), hence the problem is expected to be with kestrel and not with the test-suite/ tests. The tests fail in the same way with kestrel build R as well as build P (previous).
Output :
Exception in thread "main" java.lang.OutOfMemoryError
<<no stack trace available>>
###@###.### 2000-01-19
Bug is verified to be fixed in jdk1.3 build S on both Solaris and win32 platforms.
The following test suite fails to run against kestrel.
/net/anybodys/export2/ejb-test/ejb-MASTER-test
Steps to reproduce :
1.Download and install J2EE bundle from /usr/local/java/j2sdkee1.2/bundles
2.Run J2EE Server : set JAVA_HOME to JDK (kestrel build R or P) root and J2EE_HOME to the root of the installation directory.
3.Checkout Test Workspace from /net/anybodys/export2/ejb-test/ejb-MASTER-test
4.Set TEST_HOME to <TestWorkSpaceRoot>/test
5.set JAVA_HOME to JDK root(kestrel build R or P) in file :
<TestWorkSpaceRoot>/test/unixDefs.mk or
<TestWorkSpaceRoot>/test/win32Defs.mk for windows
6.Go to the corresponding run request directory
cd <TestWorkSpaceRoot>/work/webAutomation/runReqs/j2ee
7.Run corresponding Web Tests Setup file
. ./setMe.sh for Solaris
setMe.bat for windows
8.Run runWebTests script
sh runWebTests
(See http://javaweb/~rameshm/J2EE/webAutomation.html for detailed instructions).
These tests run fine with cricket jdk (1.2.2 w), hence the problem is expected to be with kestrel and not with the test-suite/ tests. The tests fail in the same way with kestrel build R as well as build P (previous).
Output :
Exception in thread "main" java.lang.OutOfMemoryError
<<no stack trace available>>
###@###.### 2000-01-19
Bug is verified to be fixed in jdk1.3 build S on both Solaris and win32 platforms.