[jboss-dev] Help fix the testsuite or we rollback to r79434
Kabir Khan
kabir.khan at jboss.com
Mon Oct 20 15:32:05 EDT 2008
I have profiled AS startup, and can't see anything taking unusually
huge amounts of memory here.
On 20 Oct 2008, at 20:20, Scott Stark wrote:
> Ok, so we need to know what the minimal memory for a baseline
> default type of config is and update the testsuite/imports/server-
> config.xml if we are not going to have 128M be a baseline we cannot
> move above.
>
> If I go back to rev 79434 and update the tomcat-webctx to use -
> Xmx156m, the test is passing.
>
> [server:start] /System/Library/Frameworks/JavaVM.framework/Versions/
> 1.5.0/Home/bin/java -cp /Users/svn/JBossHead/jboss-head/build/output/
> jboss-5.0.0.GA/bin/run.jar:/Library/Java/Home/lib/tools.jar -
> Xmx156m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -
> Djava.endorsed.dirs=/Users/svn/JBossHead/jboss-head/build/output/
> jboss-5.0.0.GA/lib/endorsed org.jboss.Main -c tomcat-webctx -b
> localhost
> [mkdir] Created dir: /Users/svn/JBossHead/jboss-head/testsuite/
> output/log
> [echo] Starting patternset=tomcat.webctx.includes config=tomcat-
> webctx
> [junit] Running org.jboss.test.web.test.VirtualHostTestCase
> [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.751
> sec
> [junit] Running org.jboss.test.web.test.WebCtxLoaderTestCase
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.388
> sec
> [server:stop] Shutting down server: tomcat-webctx
> [server:stop] Shutting down server: /System/Library/Frameworks/
> JavaVM.framework/Versions/1.5.0/Home/bin/java -cp /Users/svn/
> JBossHead/jboss-head/build/output/jboss-5.0.0.GA/bin/shutdown.jar:/
> Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.GA/client/
> jbossall-client.jar:/Users/svn/JBossHead/jboss-head/build/output/
> jboss-5.0.0.GA/client/jboss-common.jar org.jboss.Shutdown --server
> jnp://localhost:1099 --shutdown
> [server:stop] shutdownTimeout will be=45
>
> BUILD SUCCESSFUL
> Total time: 1 minute 23 seconds
>
> Kabir Khan wrote:
>> The CR18 upgrade switches to the MC based deployers. All the AOP
>> stuff is now deployed into the AspectManager via MC beans,
>> previously it pushed it directly into the AspectManager. ejb3-
>> interceptors-aop.xml becomes 288 MC beans with A LOT of
>> dependencies between them.
>>
>> On 20 Oct 2008, at 19:47, Dimitris Andreadis wrote:
>>
>>> My feeling too is the degradation started with the AOP CR17 (AS5
>>> CR2) -> CR18 upgrade (starting Oct/3rd), so we need to understand
>>> what was the major change there.
>>>
>>> Scott Stark wrote:
>>>> I had to roll back to r78602 to get the tomcat-webctx config to
>>>> startup. This points to a memory problem introduced in one of the
>>>> following commits:
>>>> r79434 | scott.stark at jboss.org | 2008-10-13 19:16:28 -0700 (Mon,
>>>> 13 Oct 2008) | 1 line
>>>> JBAS-5358, Move the deployers/profileservice-jboss-beans.xml to
>>>> deploy/profileservice-jboss-beans.xml
>>>> ------------------------------------------------------------------------
>>>> r79096 | kabir.khan at jboss.com | 2008-10-03 08:25:59 -0700 (Fri,
>>>> 03 Oct 2008) | 1 line
>>>> [JBAS-5894] Upgrade to AOP 2.0.0.CR18 while waiting for GA
>>>> ------------------------------------------------------------------------
>>>> r78961 | jhalliday | 2008-09-30 08:24:03 -0700 (Tue, 30 Sep 2008)
>>>> | 2 lines
>>>> Upgraded JBossTS to 4.4.0.GA, adding JTS elements in the process.
>>>> JBAS-5919
>>>> ------------------------------------------------------------------------
>>>> Note that I could not build the r78961 rev due to a bunch of aop
>>>> related version problems in thirdparty, so its either AOP
>>>> 2.0.0.CR18 or the deploy/profileservice-jboss-beans.xml, but
>>>> since that is not deployed by default. I'll call it on AOP
>>>> 2.0.0.CR18.
>>>> Scott Stark wrote:
>>>>> Rolling back to rev 79747 still does not allow the tomcat-webctx
>>>>> config to startup. It does get a little bit further along, but
>>>>> still fails to startup in 2 mins due to memory problems.
>>>>>
>>>>>
>>>>> 2008-10-20 10:55:26,423 DEBUG
>>>>> [org
>>>>> .jboss
>>>>> .aop.asintegration.jboss5.BeansDeploymentAopMetaDataDeployer]
>>>>> (main) Extracting aop bean metadata factories for
>>>>> AbstractVFSDeploymentContext at 6202695{vfsfile:/Users/svn/
>>>>> JBossHead/jboss-head/build/output/jboss-5.0.0.GA/server/tomcat-
>>>>> webctx/deploy/jbossweb.sar/}
>>>>> 2008-10-20 10:55:55,823 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> Exception in thread "ZipFile Lock Reaper"
>>>>> 2008-10-20 10:55:55,824 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> java.lang.OutOfMemoryError: Java heap space
>>>>> 2008-10-20 10:55:55,826 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> at
>>>>> java
>>>>> .util
>>>>> .concurrent
>>>>> .ConcurrentLinkedQueue.iterator(ConcurrentLinkedQueue.java:369)
>>>>> 2008-10-20 10:55:55,827 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> at org.jboss.virtual.plugins.context.zip.ZipFileLockReaper
>>>>> $ReaperTimerTask.run(ZipFileLockReaper.java:158)
>>>>> 2008-10-20 10:55:55,828 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> at java.util.TimerThread.mainLoop(Timer.java:512)
>>>>> 2008-10-20 10:55:55,829 ERROR [STDERR] (ZipFile Lock Reaper)
>>>>> at java.util.TimerThread.run(Timer.java:462)
>>>>>
>>>>>
>>>>> Richard Opalka wrote:
>>>>>> Was this problem visible before Dimitris rollback too Scott?
>>>>>> Or you can see it for the first time?
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>> Scott Stark wrote:
>>>>>>> The current rolled back trunk still fails to run through the
>>>>>>> validate-server-configs test target. It fails on the startup
>>>>>>> of the tomcat-webctx
>>>>>>>
>>>>>>> [server:start] Starting server "tomcat-webctx", with command
>>>>>>> (start timeout is 120 seconds ):
>>>>>>> [server:start] /System/Library/Frameworks/JavaVM.framework/
>>>>>>> Versions/1.5.0/Home/bin/java -cp /Users/svn/JBossHead/jboss-
>>>>>>> head/build/output/jboss-5.0.0.GA/bin/run.jar:/Library/Java/
>>>>>>> Home/lib/tools.jar -XX:MaxPermSize=512m -
>>>>>>> Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/Users/svn/
>>>>>>> JBossHead/jboss-head/build/output/jboss-5.0.0.GA/lib/endorsed
>>>>>>> org.jboss.Main -c tomcat-webctx -b localhost
>>>>>>> [server:start] Failed to start server "tomcat-webctx" before
>>>>>>> timeout. Destroying the process.
>>>>>>>
>>>>>>> BUILD FAILED
>>>>>>> /Users/svn/JBossHead/jboss-head/testsuite/build.xml:3389:
>>>>>>> Error starting server "tomcat-webctx": Server failed to start;
>>>>>>> see logs.
>>>>>>>
>>>>>>> Total time: 23 minutes 59 seconds
>>>>>>>
>>>>>>> This is due to memory problems. This config starts fine when
>>>>>>> run using the default run.sh/run.conf memory settings. If this
>>>>>>> config was starting correctly in rev r79434, its one of these
>>>>>>> changes applied after Dimitris' rollback:
>>>>>>>
>>>>>>>
>>>>>>> r79748 | richard.opalka at jboss.com | 2008-10-20 07:10:29 -0700
>>>>>>> (Mon, 20 Oct 2008) | 1 line
>>>>>>>
>>>>>>> [JBAS-6004][JBWS-2360] svn merge -r 79731:79737 https://svn.jboss.org/repos/jbossas/branches/ropalka-jbossws304
>>>>>>> ------------------------------------------------------------------------
>>>>>>> r79749 | kabir.khan at jboss.com | 2008-10-20 07:58:52 -0700
>>>>>>> (Mon, 20 Oct 2008) | 1 line
>>>>>>>
>>>>>>> [JBAOP-5894] Reapply fix following rollback
>>>>>>> ------------------------------------------------------------------------
>>>>>>> r79750 | kabir.khan at jboss.com | 2008-10-20 07:58:56 -0700
>>>>>>> (Mon, 20 Oct 2008) | 1 line
>>>>>>>
>>>>>>> [JBAOP-6062] Reapply fix following rollback
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [611][valkyrie: jboss-head]$
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jboss-development mailing list
>>>>>>> jboss-development at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
More information about the jboss-development
mailing list