[ http://jira.jboss.com/jira/browse/JBAS-1275?page=history ]
Clebert Suconic updated JBAS-1275:
----------------------------------
Attachment: CorrectAnalysis-jvm14.permanentCapacity.txt
Due to a problem during the execution of the testcases I was getting wrong
results.
Here is a more accurate analysis for JVM1.4.2
Note:
I marked where the PC (Permanent capacity) had the most significant changes I
could notice. Here is a synchronization between the JUnit test which was
running and the PC measure:
Running org.jboss.test.jmsra.test.RaSyncRecUnitTestCase First hit to 37M
Running org.jboss.test.jmx.test.JMXInvokerProxyUnitTestCase 39M
(decreased to 35M after a while)
Running org.jboss.test.lock.test.SpinUnitTestCase - 36M
Running org.jboss.test.mdb.test.MDBUnitTestCase - 37M
Running org.objectweb.jtests.jms.conform.topic.TemporaryTopicTest = 39M
Running org.jboss.test.security.test.EJBSpecUnitTestCase = 40M
Running org.jboss.test.security.test.LoginModulesUnitTestCase = 41M
(Decreased to 38912 after a while)
Running org.jboss.test.jbossmx.compliance.standard.InfoTortureTestCa = 40448
> JDK 1.3 OME running the testsuite
> ---------------------------------
>
> Key: JBAS-1275
> URL: http://jira.jboss.com/jira/browse/JBAS-1275
> Project: JBoss Application Server
> Type: Bug
> Components: Test Suite
> Versions: JBossAS-3.2.7 Final
> Environment: [EMAIL PROTECTED] bin]$ $JAVA_HOME/bin/java -version
> java version "1.3.1_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_14-b03)
> Java HotSpot(TM) Client VM (build 1.3.1_14-b03, mixed mode)
> Reporter: Scott M Stark
> Assignee: Clebert Suconic
> Fix For: JBossAS-3.2.7 Final
> Attachments: CorrectAnalysis-jvm14.permanentCapacity.txt,
> jboss-all-config-tests_gc.log, jboss-testsuite-analysis.txt
>
> Time Spent: 1 day, 1 hour
> Remaining: 0 minutes
>
> When running the jboss-all-config-tests I have been seeing OutOfMemoryErrors
> well into the tests, but -verbose:gc clearly shows that there is plenty of
> memory. The process views also show that the handle/thread count is fine.
> That pretty much only left the MaxPermSize as becoming full, and I was able
> to run the tests using:
> JAVA_OPTS="-verbose:gc -XX:MaxPermSize=70m -Xmx128m"
> This seems like an excessive amount of perm heap memory so I would like to
> look into this further. This does not happen when running JDK 1.4.2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
