9:44 a.m.
While I can start up revision 79434 in JProfiler, when I try to do the
same for trunk it takes forever. I gave up twice after about 20 minutes.
Instead, I tried current AS trunk with the current AOP 2.0.0.CR20, AOP
2.0.0.CR19( (upgrade earlier this week) and also 2.0.0.CR18 (the
version used in 79434). I restarted each of these configurations a few
times, and the times seem pretty identical across aop versions.
I will try the same for javassist 3.9.0.GA and javassist 3.8.2.GA
On 17 Oct 2008, at 13:57, Kabir Khan wrote:
ok, for me the default config boots in 27s for revision 79434, and
in 42s for current trunk. I'll attach a profiler and see if I can
find out what is causing it
On 17 Oct 2008, at 12:13, Dimitris Andreadis wrote:
> I can't tell because the testsuite was broken for other reasons
> (minimal config not booting).
>
> Looking in the testsuite history it must have been due to changes
> after Oct/14th (build #987)
>
>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>
>
> Kabir Khan wrote:
>> I will take a look. Slower compared to when?
>> On 17 Oct 2008, at 11:50, Dimitris Andreadis wrote:
>>> I looked a bit more into that and it seems the tests times out
>>> because the server boots very slowly in the tomcat-sso config
>>> (takes more than 120 secs).
>>>
>>> And locally my default & all configs now take 60% more time to
>>> boot.
>>>
>>> The usually culprit is AOP, so we need to investigate what changed:
>>>
>>> https://jira.jboss.org/jira/browse/JBAS-6105
>>>
>>> 2008-10-17 03:58:26,791 DEBUG
>>> [org.jboss.deployment.OptAnnotationMetaDataDeployer] (main)
>>> Deployment is metadata-complete, skipping annotation processing,
>>> ejbJarMetaData=null, jbossWebMetaData=org.jboss.metadata.web.spec.Web
>>> 24MetaData@1f, jbossClientMetaData=null,
>>> metaDataCompleteIsDefault=false
>>> 2008-10-17 03:58:26,823 DEBUG
>>> [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer]
>>> (main) vfsfile:/qa/services/hudson/hudson_workspace/workspace/
>>> JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/
>>> server/tomcat-sso/deploy/jbossws.sar/ endpoint mappings:
>>>
>>> 2008-10-17 03:58:26,823 DEBUG
>>> [org.jboss.deployment.MappedReferenceMetaDataResolverDeployer]
>>> (main) Processing unit=jbossws-management.war, structure:
>>> jbossws.sar
>>>
>>> +FastInfoset.jar
>>>
>>> +jboss-jaxb-intros.jar
>>>
>>> +jbossws-management.war
>>>
>>> +jbossws-native-core.jar
>>>
>>> +jettison.jar
>>>
>>> +policy.jar
>>>
>>> +wsdl4j.jar
>>>
>>> +xmlsec.jar
>>>
>>>
>>> 2008-10-17 03:59:47,704 INFO
>>> [org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown
>>> Hook) Runtime shutdown hook called, forceHalt: true
>>> 2008-10-17 03:59:47,705 DEBUG
>>> [org.jboss.deployers.plugins.main.MainDeployerImpl] (JBoss
>>> Shutdown Hook) Remove deployment context: vfsfile:/qa/services/
>>> hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/
>>> trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso/deploy/
>>> management/console-mgr.sar/
>>> 2008-10-17 03:59:47,705 DEBUG
>>> [org.jboss.deployers.plugins.main.MainDeployerImpl] (JBoss
>>> Shutdown Hook) Scheduling undeployment: vfsfile:/qa/services/
>>> hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/
>>> trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso/deploy/
>>> management/console-mgr.sar/ parent=null
>>>
>>>
>>> Dimitris Andreadis wrote:
>>>> It's been a few runs now that the tomcat-sso configuration
>>>> doesn't start properly:
>>>> tomcat-sso-tests:
>>>> [echo] creating tomcat-sso config
>>>> [copy] Copying 374 files to /qa/services/hudson/
>>>> hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/
>>>> build/output/jboss-5.0.0.GA/server/tomcat-sso [copy] Copied
>>>> 73 empty directories to 2 empty directories under /qa/services/
>>>> hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15/
>>>> trunk/build/output/jboss-5.0.0.GA/server/tomcat-sso [echo]
>>>> Overwriting config descriptors
>>>> [copy] Copying 4 files to /qa/services/hudson/hudson_workspace/
>>>> workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/
>>>> jboss-5.0.0.GA/server/tomcat-sso [server:start] Starting server
>>>> "tomcat-sso", with command (start timeout is 120 seconds ):
>>>> [server:start] /qa/tools/opt/jdk1.5.0_15/bin/java -cp /qa/
>>>> services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-
>>>> TestSuite-sun15/trunk/build/output/jboss-5.0.0.GA/bin/run.jar:/
>>>> qa/tools/opt/jdk1.5.0_15/lib/tools.jar -Xmx128m -
>>>> XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -
>>>> Djava.endorsed.dirs=/qa/services/hudson/hudson_workspace/
>>>> workspace/JBoss-AS-5.0.x-TestSuite-sun15/trunk/build/output/
>>>> jboss-5.0.0.GA/lib/endorsed org.jboss.Main -c tomcat-sso -b
>>>> 10.18.94.175 -u 227.43.0.134 [server:start] Failed to start
>>>> server "tomcat-sso" before timeout. Destroying the process.
>>>>> From the log, I can't tell what's wrong:
>>>>
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test...
>>>> Whoever is changing the tomcat configs can you please make sure
>>>> the tomcat testsuite configs are in synch?
>>>> Cheers
>>>> /D
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development