(a) upgrade to a more recent version of CruiseControl if necessary. The most recent release is 2.5, released April 2006. Are we running that version?
We are not running the most recent version. I am not sure whether our csdl specific extensions are compatible with 2.5 or not. The problem cannot be with CruiseControl, because our builds are started in complete separate processes.
(b) look through our build scripts. if we need to delete certain directories
in order to make cruise control work right, can we just go ahead and do that?
The latest version of tomcat that runs smoothly for me is 5.0. I am always
having this or that problem since we upgraded from 5.0. Though minor, the
problems are really annoying. It seems that I am the only one who can reproduce
the problem with 5.5.20. I'll report back if I have any finding. In the mean
time, I am not sure whether you want to revert back to 5.5.17 on hackydev or
keep CruiseControl stopped.
Cheers,
Cedric
Philip Johnson wrote:
I am not at all worried about Tomcat's future, and I don't see the trend of tomcat becoming a bigger and bigger problem. What I am worried about is our build environment, and the trend that I see is the need to keep all of our various components (Java, Tomcat, Ant, CruiseControl, JUnit) in sync and consistent with our build system. That's a complex maintenance scenario, unfortunately, and each time we upgrade one component, there may be ripple effects.
Here is what I know so far:
(a) I have not experienced any problems with Tomcat 5.5.20 in my local development environment.
(b) Hongbing has reported that he has no problems with Tomcat 5.5.20 running
standalone on hackydev, but it doesn't work with CruiseControl.
If you have the same error on your local machine, that appears to be a confirmation that there is a negative interaction between Tomcat and CruiseControl.
I see a couple of possible next steps:
(a) upgrade to a more recent version of CruiseControl if necessary. The most recent release is 2.5, released April 2006. Are we running that version?
(b) look through our build scripts. if we need to delete certain directories
in order to make cruise control work right, can we just go ahead and do that?
Cheers,
Philip
----- Original Message -----
From: "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
Date: Sunday, October 1, 2006 10:16 am
Subject: Re: [HACKYSTAT-DEV-L] Status report of cruise control service
To: [email protected]
I double-checked. There is nothing wrong with the configuration. I
have
the same error on my local machine. The error does not show up
every
time you try to undeploy Hackystat, but it does show up quite
frequently.
One way you can confirm that CruiseControl is working correctly is to:
(1) Delete tomcat/work/**
(2) Delete tomcat/temp/**
(3) Try to build a configuration.
I haven't figured out what caused the error. The trend is, with
each new
release, tomcat is becoming more and more problematic. Notice that
there
is no road map for tomcat to include updates in JSP and servlet
introduced in J2EE 5, and that Sun has its own open source J2EE
server,
I start doubting tomcat's future.
Cheers,
Cedric
INFO: Undeploying context [/hackystat]
Oct 1, 2006 4:03:10 PM org.apache.catalina.core.StandardContext
processTldsSEVERE: Error reading tld listeners
javax.servlet.ServletException:
Exception pr
ocessing TLD at resource path /WEB-INF/taglibs-input.tld in context
/hackystat
javax.servlet.ServletException: Exception processing TLD at
resource
path /WEB-I
NF/taglibs-input.tld in context /hackystat
at
org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
at
org.apache.catalina.startup.TldConfig.execute(TldConfig.java:301)
at
org.apache.catalina.core.StandardContext.processTlds(StandardContext.
java:4302)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4
139)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:759)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
9)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.ja
va:608)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:493
)
at
org.apache.catalina.startup.HostConfig.check(HostConfig.java:1204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:
503)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
l.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
BeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
)
at
org.apache.catalina.manager.ManagerServlet.check(ManagerServlet.java:
1377)
at
org.apache.catalina.manager.ManagerServlet.deploy(ManagerServlet.java
:814)
at
org.apache.catalina.manager.ManagerServlet.doGet(ManagerServlet.java:
343)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:178)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica
torBase.java:524)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:126)
Hongbing Kou wrote:
Hi, Cedric,
Cruise control server is stopped now because of build problems.
As you might know, there are some problems with cruise control
after
upgrading to
version 5.5.20. I did some investigations but I found a profound
phenomenon. I tested
cruise control using COCOMO configuration because it is the
lightest
one. Below
are two tests I did.
* Test scenario 1
Step 1. I brought up a new DOS windows, set CATALINA_HOME and
ANT_HOME, then
started TOMCAT.
Step 2. Copied hackystat.build.propertites from hackystat-
COCOMO to
source directory on server.
Step 3. In hackyCore_Build folder, I invoked ``ant
freshStart".
Hackystat was deployed successfully.
With this test, I am very confident that tomcat 5.5.20 should
work
well on hackydev server. Then
I tested cruise control.
* Test scenario 2
Step 1. Started cruise control service
Step 2. Manually built hackystat-COCOMO configuration, but it
failed
on hackystat deployment.
Can you login into to hackydev server to check changes I made for
tomcat upgrade? Maybe I miss
some configuration settings.
Thanks,
Hongbing
