Reading the catalina\build.xml, mbeans is excluded UNLESS compile.jmx.
Compile.jmx is true if jmx.jar is present.  If you download a jmx
implementation, and update your build.properties, it should allow you to
build and start Tomcat.

But I do see the issue you are pointing out.  You might try pulling the
admin webapp from your Tomcat build and see if Tomcat starts without it.
(maybe webdav and manager too.  Those may be reliant on JMX).  There
does seem to be a bug in the build process concerning JMX and the
services that use it.  I would post a bug report concerning this issue,
but unless you include a patch it probably won't get fixed quickly.


Also, if you don't have all the optional libraries, you are not building
a full version of Tomcat.  

- Andrew

> -----Original Message-----
> From: Dev Zero G Ltd team [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, August 28, 2002 12:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Tomcat 4 nightly build doesn't starts
> 
> 
> The problem is that Tomcat build finishes successfully.
> 
> The procedure how I built is following:
> 
> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic 
> checkout jakarta-tomcat-4.0 install via ports: 
> /usr/ports/devel/jakarta-ant/
> 
> checkout then build (may need to copy build.properties.sample to
> build.properties):
> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic 
> checkout -r tomcat_4_branch jakarta-tomcat-jasper cvs -d 
> :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout 
> jakarta-tomcat-connectors cvs -d 
> :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout 
> jakarta-servletapi-4
> 
> fetch and unzip: 
> http://jakarta.apache.org/builds/jakarta-commons/release/commo
> ns-beanutils/v
> 1.4/commons-beanutils-1.4.tar.gz 
> http://jakarta.apache.org/builds/jakarta-commons/release/commo
> ns-collections
> /v2.0/commons-collections-2.0.tar.gz
> http://jakarta.apache.org/builds/jakarta-commons/release/commo
> ns-digester/v1
> .2/commons-digester-1.2.tar.gz 
> http://jakarta.apache.org/builds/jakarta-commons/release/commo
> ns-logging/v1.
> 0.1/commons-logging-1.0.1.tar.gz
> http://jakarta.apache.org/builds/jakarta-regexp/release/v1.2/j
akarta-regexp-
> 1.2.tar.gz
> 
> fetch, unzip, then copy xalan.jar to 
> /usr/local/jakarta-ant-1.5.0/lib/ 
> http://xml.apache.org/dist/xalan-j/xalan-j_2_4_D1-bin.tar.gz
> 
> Then I ran ant dist. The build completed successfully. But I 
> had the mentioned exception when I was trying to run Tomcat 
> from dist folder. I found that in catalina/build.xml package 
> mbeans is exluded. But the exception says that 
> org.apache.catalina.mbeans.ServerLifecycleListener
> not fould during the start Tomcat.
> 
> 
> 
> 
> 
> >How are you trying to build tomcat?
> >
> >You should be building using 'ant dist'.  Also, did you 
> include all the 
> >optional libraries.  Not having an implementation of JMX 1.0 may be 
> >causing this problem, although I don't know for sure.  See 
> step 14 of 
> >Building.txt for options.  I use mx4j myself
> >
> >Andrew Conrad
> >
> >> -----Original Message-----
> >> From: Dev Zero G Ltd team [mailto:[EMAIL PROTECTED]]
> >> Sent: Wednesday, August 28, 2002 10:19 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: Tomcat 4 nightly build doesn't starts
> >>
> >>
> >> I have built Tomcat from jakarta-tomcat-4.0 cvs module and all 
> >> necessary subprojects.
> >>
> >> When I am trying to start it raises an exception:
> >
> > Catalina.start: java.lang.ClassNotFoundException: 
> > org.apache.catalina.mbeans.ServerLifecycleListener
> > java.lang.ClassNotFoundException: 
> > org.apache.catalina.mbeans.ServerLifecycleListener
> >
> > And I really can't find it in catalina.jar
> >
> >
> > --
> > Best regards,
> > Dev Zero G Ltd team http://devzerog.com 
> > mailto:[EMAIL PROTECTED]
> >
> >
> >
> >
> >
> > --
> > To unsubscribe,
> > e-mail:   <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail: 
> > <mailto:[EMAIL PROTECTED]>
> >
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:[EMAIL PROTECTED]>
> For 
> additional commands, e-mail: 
> <mailto:[EMAIL PROTECTED]>
> 


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to