RE: [jboss-dev] RE: ejb3-4.2-testsuite Build Failed
by Dimitris Andreadis
Update and rebuild, it's probably fixed.
> -----Original Message-----
> From: Carlo de Wolf [mailto:carlo.dewolf@jboss.com]
> Sent: Friday, January 19, 2007 7:47 PM
> To: JBoss.org development list
> Cc: QA; QA; wolfc(a)jboss.com
> Subject: Re: [jboss-dev] RE: ejb3-4.2-testsuite Build Failed
>
> jmx-console doesn't come up, because of deployment issues.
> I think it's because jbossweb was introduced.
>
> See
> http://cruisecontrol.jboss.com/cc/artifacts/ejb3-4.2-testsuite
> /20070118231717/build/output/jboss-4.2.0.CR1-ejb3/server/node1
> /log/server.log
> at the end.
>
> It appears there is no WebServer available.
>
> Carlo
>
> On Fri, 2007-01-19 at 01:31 -0600, Dimitris Andreadis wrote:
> > Can somebody check what's wrong with this particular configuration
> > that timeouts?
> >
> > modify-ejb3-repl_sync:
> > [echo] Replacing the cache mode to REPL_SYNC in
> >
> /services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/output/
> >
> jboss-4.2.0.CR1/server/node1/deploy/ejb3-clustered-sfsbcache-service.x
> > ml [replaceregexp] The following file is missing:
> >
> '/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/buil
> d/output/jboss-4.2.0.CR1/server/node1/deploy/ejb3-clustered-sf
> sbcache-service.xml'
> > [echo] Will start the jboss instance
> build01.dmz.inap.jboss.com
> > with node1,
> >
> dist=/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/ou
> > tput/jboss-4.2.0.CR1-ejb3
> >
> > [echo]
> >
> /services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/output/
> > jboss-4.2.0.CR1-ejb3
> >
> > tests-clustering-wait:
> > [echo] Waiting for nodes to start...
> >
> > BUILD FAILED
> >
> /services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/
> build-test.xml:2863: The following error occurred while
> executing this line:
> >
> /services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/
> build-test.xml:3179: The following error occurred while
> executing this line:
> >
> /services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/build-te
> > st.xml:3348: Timeout waiting for nodes to start
> >
> > Total time: 60 minutes 23 seconds
> >
> >
> >
> >
> ______________________________________________________________
> > From: qa(a)jboss.com [mailto:qa@jboss.com]
> > Sent: Friday, January 19, 2007 7:42 AM
> > To: jboss-development(a)lists.jboss.org; QA; wolfc(a)jboss.com
> > Subject: ejb3-4.2-testsuite Build Failed
> > Importance: High
> >
> >
> >
> > View results here ->
> >
> >
> http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.2-testsuite?log=
> > log20070118231717
> >
> > BUILD FAILED
> > Ant Error
> > Message:
> /services/cruisecontrol/work/scripts/build-ejb3-4.2-testsuite.
> xml:87: Exit code: 1 See tests.log in Build Artifacts for details.
> > Date of build: 01/18/2007 23:17:17
> > Time to build: 83 minutes 27 seconds
> > Last changed: 01/18/2007 09:48:45
> > Last log entry: Set -Xmx128m to counter OutOfMemoryError
> >
> >
>
> > Unit Tests: (0) Total Errors and Failures: (0)
> >
> >
> >
> > Modifications since last build: (first 50 of 1)
> > 59780
> > modified
> > wolfc
> > //branches/Branch_4_2/ejb3/build-test.xml
> > Set -Xmx128m
> > to counter
> > OutOfMemoryError
> >
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
>
>
19 years, 2 months
RE: ejb3-4.2-testsuite Build Failed
by Dimitris Andreadis
Can somebody check what's wrong with this particular configuration that
timeouts?
modify-ejb3-repl_sync:
[echo] Replacing the cache mode to REPL_SYNC in
/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/output/jb
oss-4.2.0.CR1/server/node1/deploy/ejb3-clustered-sfsbcache-service.xml
[replaceregexp] The following file is missing:
'/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/output/j
boss-4.2.0.CR1/server/node1/deploy/ejb3-clustered-sfsbcache-service.xml'
[echo] Will start the jboss instance build01.dmz.inap.jboss.com
with node1,
dist=/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/outp
ut/jboss-4.2.0.CR1-ejb3
[echo]
/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/build/output/jb
oss-4.2.0.CR1-ejb3
tests-clustering-wait:
[echo] Waiting for nodes to start...
BUILD FAILED
/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/build-test
.xml:2863: The following error occurred while executing this line:
/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/build-test
.xml:3179: The following error occurred while executing this line:
/services/cruisecontrol/work/checkout/ejb3-4.2-testsuite/ejb3/build-test
.xml:3348: Timeout waiting for nodes to start
Total time: 60 minutes 23 seconds
________________________________
From: qa(a)jboss.com [mailto:qa@jboss.com]
Sent: Friday, January 19, 2007 7:42 AM
To: jboss-development(a)lists.jboss.org; QA; wolfc(a)jboss.com
Subject: ejb3-4.2-testsuite Build Failed
Importance: High
View results here ->
http://cruisecontrol.jboss.com/cc/buildresults/ejb3-4.2-testsuite?log=lo
g20070118231717
BUILD FAILED
Ant Error Message:
/services/cruisecontrol/work/scripts/build-ejb3-4.2-testsuite.xml:87:
Exit code: 1 See tests.log in Build Artifacts for details.
Date of build: 01/18/2007 23:17:17
Time to build: 83 minutes 27 seconds
Last changed: 01/18/2007 09:48:45
Last log entry: Set -Xmx128m to counter OutOfMemoryError
Unit Tests: (0) Total Errors and Failures: (0)
Modifications since last build: (first 50 of 1)
59780 modified wolfc
//branches/Branch_4_2/ejb3/build-test.xml Set -Xmx128m to counter
OutOfMemoryError
19 years, 2 months
RE: [jboss-dev] org.jboss.web.tomcat.tc5.StatusServlet
by Dimitris Andreadis
I think I've managed to fix this, so no need for another jbossws release
for now :)
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Dimitris Andreadis
> Sent: Friday, January 19, 2007 2:28 PM
> To: Thomas Diesler; Jason T. Greene
> Cc: jboss-development(a)lists.jboss.org; Remy Maucherat
> Subject: [jboss-dev] org.jboss.web.tomcat.tc5.StatusServlet
>
> Another glitch of the Branch_4_2 - jboss-web update is the
> moving of StatusServlet to:
>
> org.jboss.web.tomcat.service.StatusServlet
>
> 13:06:45,773 WARN [DeployerInterceptorJSE] Cannot load servlet class:
> org.jboss.web.tomcat.tc5.StatusServlet
>
> I guess a jbossws 1.2.0.CR3 is needed?
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
19 years, 2 months
org.jboss.web.tomcat.tc5.StatusServlet
by Dimitris Andreadis
Another glitch of the Branch_4_2 - jboss-web update is the moving of
StatusServlet to:
org.jboss.web.tomcat.service.StatusServlet
13:06:45,773 WARN [DeployerInterceptorJSE] Cannot load servlet class:
org.jboss.web.tomcat.tc5.StatusServlet
I guess a jbossws 1.2.0.CR3 is needed?
19 years, 2 months
Branch_4_2 - deploy/jboss-web.sar
by Dimitris Andreadis
I've changed deploy/jboss-web.sar to deploy/jboss-web.deployer, so it
starts before .sar's
This solves http://jira.jboss.com/jira/browse/JBAS-3398
I've noticed also the initial name change from jbossweb-tomcat55.sar to
jboss-web.sar broke the clustering server setup tests (below), so I
fixed that as well.
modify-cluster-stack:
[server:start] Starting server "cluster-UDP-0" with command:
[server:start] /opt/jrockit-jdk1.5.0_06/bin/java -cp
/services/cruisecontrol/checkout/jboss-4.2-testsuite-1.5/build/output/jb
oss-4.2.0.CR1/bin/run.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar
-Dresolve.dns=false -Djgroups.udp.ip_ttl=1 org.jboss.Main -c
cluster-UDP-0 -b localhost
BUILD FAILED
/services/cruisecontrol/checkout/jboss-4.2-testsuite-1.5/testsuite/build
.xml:721: The following error occurred while executing this line:
/services/cruisecontrol/checkout/jboss-4.2-testsuite-1.5/testsuite/build
.xml:958: The following error occurred while executing this line:
/services/cruisecontrol/checkout/jboss-4.2-testsuite-1.5/testsuite/build
.xml:978: Error starting server "cluster-UDP-0": Server failed to start;
see logs.
Total time: 109 minutes 28 seconds
19 years, 2 months
