You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2012/02/01 06:33:15 UTC
Ideas for some integration tests
Would be great to get an integration test that creates a webapp with say 10 or 20mb of jars. Then measure that startup time and keep track of it over time.
As well we could actually start testing specific libraries inside the webapp to see if there are issues. Spring comes to mind.
Likely some others we can do.
I personally would be interested to see if Confluence and Jira run without issues (would likely be library conflicts if there are issues).
We could set these up in buildbot (or jenkins) and run them regularly.
-David
Re: Ideas for some integration tests
Posted by Romain Manni-Bucau <rm...@gmail.com>.
we are still using a tree as classloader and we don't manage exclude list
between app classloader and common classloader so we can find conflicts.
- Romain
2012/2/2 Alan D. Cabrera <li...@toolazydogs.com>
>
> On Jan 31, 2012, at 9:33 PM, David Blevins wrote:
>
> > Would be great to get an integration test that creates a webapp with say
> 10 or 20mb of jars. Then measure that startup time and keep track of it
> over time.
> >
> > As well we could actually start testing specific libraries inside the
> webapp to see if there are issues. Spring comes to mind.
> >
> > Likely some others we can do.
> >
> > I personally would be interested to see if Confluence and Jira run
> without issues (would likely be library conflicts if there are issues).
>
> Why would one be worried about library conflicts if the war's jar's are
> loaded in their own classloader? Is this a special kind of testing?
>
>
> Regards,
> Alan
>
Re: Ideas for some integration tests
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Jan 31, 2012, at 9:33 PM, David Blevins wrote:
> Would be great to get an integration test that creates a webapp with say 10 or 20mb of jars. Then measure that startup time and keep track of it over time.
>
> As well we could actually start testing specific libraries inside the webapp to see if there are issues. Spring comes to mind.
>
> Likely some others we can do.
>
> I personally would be interested to see if Confluence and Jira run without issues (would likely be library conflicts if there are issues).
Why would one be worried about library conflicts if the war's jar's are loaded in their own classloader? Is this a special kind of testing?
Regards,
Alan
Re: Ideas for some integration tests
Posted by Romain Manni-Bucau <rm...@gmail.com>.
so maybe jira is a bad example it is pretty big (100M)
but scanning should really be enhanced.
- Romain
2012/2/1 David Blevins <da...@gmail.com>
> Great. In this pretend app though we should have it setup so none of the
> app jars are in the excludes list so we are tracking our actual startup
> time with a decent sized app.
>
> If we need to rename all the jars to superbiz-*.jar when we add them to
> the war, that'd be one way to do it.
>
> In the worst case scenario where we have to actually scan a jar
> completely, I suspect there's plenty of room to do that faster. I know we
> don't scan only once, so that's definitely another area where we can focus
> on getting better.
>
>
> -David
>
>
> On Feb 1, 2012, at 1:36 AM, Romain Manni-Bucau wrote:
>
> > for jira i needed to tweak conf/exclusions.list file (some can be
> > duplicated since i didn't clean it):
> >
> > google-
> > saxon-
> > joda-time-
> > wstx-asl
> > crowd-
> > mail-
> > xstream-
> > osworkflow-
> > javacvs-
> > org.apache.felix
> > glue-
> > xalan-
> > jai_
> > bcvprov-
> > axis-
> > jfreechart-
> > xercesImpl-
> > js-
> > atlassian-
> > crowd-
> > entity
> > jira-
> > lucene-
> > spring-
> > ApacheJMeter
> > XmlSchema-
> > aether-
> > activeio-
> > activemq-
> > antlr-
> > aopalliance-
> > avalon-framework-
> > axis-
> > axis2-
> > bcprov-
> > bval-core
> > bval-jsr
> > catalina-
> > cglib-
> > commons-beanutils
> > commons-cli-
> > commons-codec-
> > commons-collections-
> > commons-digester-
> > commons-dbcp
> > commons-dbcp-all-1.3-
> > commons-discovery-
> > commons-httpclient-
> > commons-io-
> > commons-lang-
> > commons-lang3-
> > commons-logging-
> > commons-logging-api-
> > commons-net-
> > commons-pool-
> > cssparser-
> > cxf-
> > deploy.jar
> > derby-
> > dom4j-
> > geronimo-
> > gragent.jar
> > guice-
> > hibernate-
> > howl-
> > hsqldb-
> > htmlunit-
> > icu4j-
> > idb-
> > idea_rt.jar
> > jasypt-
> > javaee-
> > javaee-api
> > javassist-
> > javaws.jar
> > javax.
> > jaxb-
> > jaxp-
> > jboss-
> > jbossall-
> > jbosscx-
> > jbossjts-
> > jbosssx-
> > jcommander-
> > jetty-
> > jettison-
> > joda-time-
> > jmdns-
> > jsp-api-
> > jsr299-
> > jsr311-
> > juli-
> > junit-
> > kahadb-
> > log4j-
> > logkit-
> > maven-
> > mbean-annotation-api-
> > myfaces-api
> > myfaces-impl
> > neethi-
> > nekohtml-
> > openejb-api
> > openejb-cxf-bundle
> > openejb-javaagent
> > openejb-jee
> > openejb-loader
> > openjpa-
> > opensaml-
> > openwebbeans-
> > openws-
> > ops4j-
> > org.eclipse.
> > org.junit.
> > org.osgi.core-
> > pax-
> > plexus-
> > quartz-
> > rmock-
> > saaj-
> > sac-
> > scannotation-
> > serializer-
> > serp-
> > servlet-api-
> > slf4j-
> > spring-
> > stax-api-
> > swizzle-
> > testng-
> > wagon-
> > webbeans-ee
> > webbeans-ejb
> > webbeans-impl
> > webbeans-spi
> > wsdl4j-
> > wss4j-
> > wstx-asl-
> > xalan-
> > xbean-
> > xercesImpl-
> > xml-apis-
> > xml-resolver-
> > xmlrpc-
> > xmlsec-
> > xmlunit-
> >
> > if you don't do it it is complicated to start because of memory,
> > classloading time etc...
> >
> > - Romain
> >
> >
> > 2012/2/1 Jean-Louis MONTEIRO <je...@gmail.com>
> >
> >> BcProv is another one which cause long startup delay.
> >>
> >> Jean-Louis
> >>
> >> 2012/2/1 David Blevins <da...@gmail.com>
> >>
> >>> Would be great to get an integration test that creates a webapp with
> say
> >>> 10 or 20mb of jars. Then measure that startup time and keep track of
> it
> >>> over time.
> >>>
> >>> As well we could actually start testing specific libraries inside the
> >>> webapp to see if there are issues. Spring comes to mind.
> >>>
> >>> Likely some others we can do.
> >>>
> >>> I personally would be interested to see if Confluence and Jira run
> >> without
> >>> issues (would likely be library conflicts if there are issues).
> >>>
> >>> We could set these up in buildbot (or jenkins) and run them regularly.
> >>>
> >>>
> >>> -David
> >>>
> >>>
> >>
>
>
Re: Ideas for some integration tests
Posted by David Blevins <da...@gmail.com>.
Great. In this pretend app though we should have it setup so none of the app jars are in the excludes list so we are tracking our actual startup time with a decent sized app.
If we need to rename all the jars to superbiz-*.jar when we add them to the war, that'd be one way to do it.
In the worst case scenario where we have to actually scan a jar completely, I suspect there's plenty of room to do that faster. I know we don't scan only once, so that's definitely another area where we can focus on getting better.
-David
On Feb 1, 2012, at 1:36 AM, Romain Manni-Bucau wrote:
> for jira i needed to tweak conf/exclusions.list file (some can be
> duplicated since i didn't clean it):
>
> google-
> saxon-
> joda-time-
> wstx-asl
> crowd-
> mail-
> xstream-
> osworkflow-
> javacvs-
> org.apache.felix
> glue-
> xalan-
> jai_
> bcvprov-
> axis-
> jfreechart-
> xercesImpl-
> js-
> atlassian-
> crowd-
> entity
> jira-
> lucene-
> spring-
> ApacheJMeter
> XmlSchema-
> aether-
> activeio-
> activemq-
> antlr-
> aopalliance-
> avalon-framework-
> axis-
> axis2-
> bcprov-
> bval-core
> bval-jsr
> catalina-
> cglib-
> commons-beanutils
> commons-cli-
> commons-codec-
> commons-collections-
> commons-digester-
> commons-dbcp
> commons-dbcp-all-1.3-
> commons-discovery-
> commons-httpclient-
> commons-io-
> commons-lang-
> commons-lang3-
> commons-logging-
> commons-logging-api-
> commons-net-
> commons-pool-
> cssparser-
> cxf-
> deploy.jar
> derby-
> dom4j-
> geronimo-
> gragent.jar
> guice-
> hibernate-
> howl-
> hsqldb-
> htmlunit-
> icu4j-
> idb-
> idea_rt.jar
> jasypt-
> javaee-
> javaee-api
> javassist-
> javaws.jar
> javax.
> jaxb-
> jaxp-
> jboss-
> jbossall-
> jbosscx-
> jbossjts-
> jbosssx-
> jcommander-
> jetty-
> jettison-
> joda-time-
> jmdns-
> jsp-api-
> jsr299-
> jsr311-
> juli-
> junit-
> kahadb-
> log4j-
> logkit-
> maven-
> mbean-annotation-api-
> myfaces-api
> myfaces-impl
> neethi-
> nekohtml-
> openejb-api
> openejb-cxf-bundle
> openejb-javaagent
> openejb-jee
> openejb-loader
> openjpa-
> opensaml-
> openwebbeans-
> openws-
> ops4j-
> org.eclipse.
> org.junit.
> org.osgi.core-
> pax-
> plexus-
> quartz-
> rmock-
> saaj-
> sac-
> scannotation-
> serializer-
> serp-
> servlet-api-
> slf4j-
> spring-
> stax-api-
> swizzle-
> testng-
> wagon-
> webbeans-ee
> webbeans-ejb
> webbeans-impl
> webbeans-spi
> wsdl4j-
> wss4j-
> wstx-asl-
> xalan-
> xbean-
> xercesImpl-
> xml-apis-
> xml-resolver-
> xmlrpc-
> xmlsec-
> xmlunit-
>
> if you don't do it it is complicated to start because of memory,
> classloading time etc...
>
> - Romain
>
>
> 2012/2/1 Jean-Louis MONTEIRO <je...@gmail.com>
>
>> BcProv is another one which cause long startup delay.
>>
>> Jean-Louis
>>
>> 2012/2/1 David Blevins <da...@gmail.com>
>>
>>> Would be great to get an integration test that creates a webapp with say
>>> 10 or 20mb of jars. Then measure that startup time and keep track of it
>>> over time.
>>>
>>> As well we could actually start testing specific libraries inside the
>>> webapp to see if there are issues. Spring comes to mind.
>>>
>>> Likely some others we can do.
>>>
>>> I personally would be interested to see if Confluence and Jira run
>> without
>>> issues (would likely be library conflicts if there are issues).
>>>
>>> We could set these up in buildbot (or jenkins) and run them regularly.
>>>
>>>
>>> -David
>>>
>>>
>>
Re: Ideas for some integration tests
Posted by Romain Manni-Bucau <rm...@gmail.com>.
for jira i needed to tweak conf/exclusions.list file (some can be
duplicated since i didn't clean it):
google-
saxon-
joda-time-
wstx-asl
crowd-
mail-
xstream-
osworkflow-
javacvs-
org.apache.felix
glue-
xalan-
jai_
bcvprov-
axis-
jfreechart-
xercesImpl-
js-
atlassian-
crowd-
entity
jira-
lucene-
spring-
ApacheJMeter
XmlSchema-
aether-
activeio-
activemq-
antlr-
aopalliance-
avalon-framework-
axis-
axis2-
bcprov-
bval-core
bval-jsr
catalina-
cglib-
commons-beanutils
commons-cli-
commons-codec-
commons-collections-
commons-digester-
commons-dbcp
commons-dbcp-all-1.3-
commons-discovery-
commons-httpclient-
commons-io-
commons-lang-
commons-lang3-
commons-logging-
commons-logging-api-
commons-net-
commons-pool-
cssparser-
cxf-
deploy.jar
derby-
dom4j-
geronimo-
gragent.jar
guice-
hibernate-
howl-
hsqldb-
htmlunit-
icu4j-
idb-
idea_rt.jar
jasypt-
javaee-
javaee-api
javassist-
javaws.jar
javax.
jaxb-
jaxp-
jboss-
jbossall-
jbosscx-
jbossjts-
jbosssx-
jcommander-
jetty-
jettison-
joda-time-
jmdns-
jsp-api-
jsr299-
jsr311-
juli-
junit-
kahadb-
log4j-
logkit-
maven-
mbean-annotation-api-
myfaces-api
myfaces-impl
neethi-
nekohtml-
openejb-api
openejb-cxf-bundle
openejb-javaagent
openejb-jee
openejb-loader
openjpa-
opensaml-
openwebbeans-
openws-
ops4j-
org.eclipse.
org.junit.
org.osgi.core-
pax-
plexus-
quartz-
rmock-
saaj-
sac-
scannotation-
serializer-
serp-
servlet-api-
slf4j-
spring-
stax-api-
swizzle-
testng-
wagon-
webbeans-ee
webbeans-ejb
webbeans-impl
webbeans-spi
wsdl4j-
wss4j-
wstx-asl-
xalan-
xbean-
xercesImpl-
xml-apis-
xml-resolver-
xmlrpc-
xmlsec-
xmlunit-
if you don't do it it is complicated to start because of memory,
classloading time etc...
- Romain
2012/2/1 Jean-Louis MONTEIRO <je...@gmail.com>
> BcProv is another one which cause long startup delay.
>
> Jean-Louis
>
> 2012/2/1 David Blevins <da...@gmail.com>
>
> > Would be great to get an integration test that creates a webapp with say
> > 10 or 20mb of jars. Then measure that startup time and keep track of it
> > over time.
> >
> > As well we could actually start testing specific libraries inside the
> > webapp to see if there are issues. Spring comes to mind.
> >
> > Likely some others we can do.
> >
> > I personally would be interested to see if Confluence and Jira run
> without
> > issues (would likely be library conflicts if there are issues).
> >
> > We could set these up in buildbot (or jenkins) and run them regularly.
> >
> >
> > -David
> >
> >
>
Re: Ideas for some integration tests
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
BcProv is another one which cause long startup delay.
Jean-Louis
2012/2/1 David Blevins <da...@gmail.com>
> Would be great to get an integration test that creates a webapp with say
> 10 or 20mb of jars. Then measure that startup time and keep track of it
> over time.
>
> As well we could actually start testing specific libraries inside the
> webapp to see if there are issues. Spring comes to mind.
>
> Likely some others we can do.
>
> I personally would be interested to see if Confluence and Jira run without
> issues (would likely be library conflicts if there are issues).
>
> We could set these up in buildbot (or jenkins) and run them regularly.
>
>
> -David
>
>