[jira] Closed: (CACTUS-41) Can't run Cactus with Tomcat 5

[ji...@apache.org]

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/CACTUS-41

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CACTUS-41
    Summary: Can't run Cactus with Tomcat 5
       Type: Bug

     Status: Closed
   Priority: Blocker
 Resolution: CANNOT REPRODUCE

    Project: Cactus
 Components: 
             Ant Integration
   Fix Fors:
             1.5-beta1
   Versions:
             1.4.1

   Assignee: Christopher Lenz
   Reporter: Ed Burns

    Created: Thu, 1 May 2003 4:07 AM
    Updated: Sat, 17 Apr 2004 8:38 AM
Environment: Operating System: Windows NT/2K
Platform: PC

Description:
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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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