DO NOT REPLY [Bug 19509] New: - Can't run Cactus with Tomcat 5

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19509>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19509

Can't run Cactus with Tomcat 5

           Summary: Can't run Cactus with Tomcat 5
           Product: Cactus
           Version: 1.4.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Ant Integration
        AssignedTo: cactus-dev@jakarta.apache.org
        ReportedBy: edburns@acm.org


I'm trying to run Cactus 13-1.4.1 [1] with the Tomcat 5 nightly from 20030424.

My build-tests.xml file, which works fine when running with Tomcat 4.x, has this
taskdef:

        <taskdef name="runservertests"
            classname="org.apache.cactus.ant.RunServerTestsTask">
            <classpath>
                <pathelement location="${cactus.ant.jar}"/>
                <pathelement path="${java.class.path}"/>
            </classpath>
        </taskdef>

Which is used from this target:

    <target name="test.tomcat.50" depends="prepare.test.tomcat.50">

        <!-- Start the servlet engine, wait for it to be started, run the
             unit tests, stop the servlet engine, wait for it to be stopped.
             The servlet engine is automatically stopped if the tests fail for
             any reason.-->

        <runservertests testURL="http://localhost:8080/test"
            startTarget="start.tomcat.50"
            stopTarget="stop.tomcat.50"
            testTarget="run.cactus.test"/>

    </target>

Which calls this target

    <target name="start.tomcat.50">

        <echo message="${out.tomcat.50.dir}"/>

        <java classname="org.apache.catalina.startup.Bootstrap" fork="yes">
            <jvmarg value="-Dcatalina.home=${tomcat.home.50}"/>
            <jvmarg value="-Dcatalina.base=${tomcat.home.50}"/>
            <jvmarg value="-Djava.endorsed.dirs=${tomcat.home.50}"/>
            <jvmarg value="-Djava.io.tmpdir=${tomcat.home.50}/temp"/>
            <arg value="-config"/>
            <arg value="${out.tomcat.50.dir}/conf/server.xml"/>
            <!-- uncomment this to attach the debugger to the tomcat vm -->
            <jvmarg line="${debug.jvm.args}"/>


<!--            <arg value="-config"/>
            <arg value="${out.tomcat.50.dir}/conf/server.xml"/> -->
            <arg value="start"/>
            <classpath refid="tomcat.50.classpath"/>
        </java>

    </target>

Now, the "start.tomcat.50" target should start and return, so the "testTarget"
can run, but it doesn't return.  

Using ant -verbose reveals that the java VM invocation line for starting tomcat
is as in the first attachment to this bug.  And indeed, when I run this java vm
invocation line from the command line, it does not return.

I think this is a bug.







[1]
http://jakarta.apache.org/builds/jakarta-cactus/release/v1.4.1/jakarta-cactus-13-1.4.1.zip

---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org