Message:
The following issue has been closed.
Resolver: David Jencks
Date: Sun, 1 Aug 2004 1:36 PM
I have never had this problem and I haven't heard of anyone else having it. If
you are still having it you may need to provide more clues or investigate it
yourself.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-245
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-245
Summary: OutOfMemoryError while running ConnectionManagerStressTest
Type: Task
Status: Closed
Priority: Minor
Resolution: CANNOT REPRODUCE
Project: Apache Geronimo
Components:
buildsystem
connector
Fix Fors:
1.0-M2
Versions:
1.0-M2
Assignee: David Jencks
Reporter: Ralf Barkow
Created: Sat, 12 Jun 2004 2:44 PM
Updated: Sun, 1 Aug 2004 1:36 PM
Environment: Windows 2000 Prof DE (5.00.2195) SP4, Java 1.4.2_04-b05, maven
1.0-rc2
AMD-K6(tm) 3D processor with 384 MB RAM
Description:
Building the current 1.0-SNAPSHOT on my 'thin-chested' Win2kProf DE box with
java v1.4.2_04-b05, there's now an OutOfMemoryError while running the
connector.outbound.ConnectionManagerStressTest. Okay, 384 MB RAM isn't that
much, but obviously no problem if I run this test in Eclipse3M8. Everything's
green there -- test(s) passed.
Setting MAVEN_OPTS=-Xmx<memory_size> didn't help. I tried 512m and -- probably
more realistic -- 256M, which I also use in the comand line arguments for
Eclipse.
Workaround: I build -- successfully btw -- with
"maven -Dmaven.test.failure.ignore=true"
for now.
Is this a maven bug (v. 1.0-rc2) ? Or a problem with the installed JREs?
Eclipse runs under/uses AppServer-jdk-1.4.2_04-b04, which is JAVA_HOME also,
vs. j2re-1.4.2_04-b05 in WINNT/system32/ and programs, which seems to be
launched by maven, shells, etc.
Any ideas?
--
/rgb
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
