running test project kills hudson

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

running test project kills hudson

Nigel Magnay
One of my project modules is an 'integration' test. This uses the maven-ant plugin to run a number of scripts, bringing up an app server (using cargo), and a few other things.

It all runs fine, but at the end of the tests, the shutting down of the ant/maven process seems to kill off the entire JVM (tomcat comes down with it)

This obviously isn't right... is there any simple way to fix it?

Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Gregory Kick-2
Remove the line that says System.exit()?  :-)

I would say that if you're having problems running cargo via ant, use
the cargo maven plugin and invoke the cargo:stop goal instead.  It'll
probably be safer for maven execution.

On 4/19/07, Nigel Magnay <[hidden email]> wrote:

> One of my project modules is an 'integration' test. This uses the maven-ant
> plugin to run a number of scripts, bringing up an app server (using cargo),
> and a few other things.
>
> It all runs fine, but at the end of the tests, the shutting down of the
> ant/maven process seems to kill off the entire JVM (tomcat comes down with
> it)
>
> This obviously isn't right... is there any simple way to fix it?
>
>


--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Nigel Magnay
Can't - the integration test is very involved and the server goes up and down 3 or 4 times...

On 19/04/07, Gregory Kick <[hidden email]> wrote:
Remove the line that says System.exit()?  :-)

I would say that if you're having problems running cargo via ant, use
the cargo maven plugin and invoke the cargo:stop goal instead.  It'll
probably be safer for maven execution.

On 4/19/07, Nigel Magnay <[hidden email] > wrote:
> One of my project modules is an 'integration' test. This uses the maven-ant
> plugin to run a number of scripts, bringing up an app server (using cargo),
> and a few other things.
>
> It all runs fine, but at the end of the tests, the shutting down of the
> ant/maven process seems to kill off the entire JVM (tomcat comes down with
> it)
>
> This obviously isn't right... is there any simple way to fix it?
>
>


--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Gregory Kick-2
Could you split it into multiple tests?

On 4/19/07, Nigel Magnay <[hidden email]> wrote:

> Can't - the integration test is very involved and the server goes up and
> down 3 or 4 times...
>
>
> On 19/04/07, Gregory Kick < [hidden email]> wrote:
> >
> > Remove the line that says System.exit()?  :-)
> >
> > I would say that if you're having problems running cargo via ant, use
> > the cargo maven plugin and invoke the cargo:stop goal instead.  It'll
> > probably be safer for maven execution.
> >
> > On 4/19/07, Nigel Magnay <[hidden email] > wrote:
> > > One of my project modules is an 'integration' test. This uses the
> maven-ant
> > > plugin to run a number of scripts, bringing up an app server (using
> cargo),
> > > and a few other things.
> > >
> > > It all runs fine, but at the end of the tests, the shutting down of the
> > > ant/maven process seems to kill off the entire JVM (tomcat comes down
> with
> > > it)
> > >
> > > This obviously isn't right... is there any simple way to fix it?
> > >
> > >
> >
> >
> > --
> > Gregory Kick
> > http://kickstyle.net/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Nigel Magnay
Don't think it'd help - the tests use ant, running ant is killing hudson...

I don't see why this should kill everything - mvn reactor builds run fine without the ant plugin stopping the JVM (which seems to shutdown gracefully..)

On 19/04/07, Gregory Kick <[hidden email]> wrote:
Could you split it into multiple tests?

On 4/19/07, Nigel Magnay <[hidden email]> wrote:

> Can't - the integration test is very involved and the server goes up and
> down 3 or 4 times...
>
>
> On 19/04/07, Gregory Kick < [hidden email]> wrote:
> >
> > Remove the line that says System.exit()?  :-)
> >
> > I would say that if you're having problems running cargo via ant, use
> > the cargo maven plugin and invoke the cargo:stop goal instead.  It'll
> > probably be safer for maven execution.
> >
> > On 4/19/07, Nigel Magnay <[hidden email] > wrote:
> > > One of my project modules is an 'integration' test. This uses the
> maven-ant
> > > plugin to run a number of scripts, bringing up an app server (using
> cargo),
> > > and a few other things.
> > >
> > > It all runs fine, but at the end of the tests, the shutting down of the
> > > ant/maven process seems to kill off the entire JVM (tomcat comes down
> with
> > > it)
> > >
> > > This obviously isn't right... is there any simple way to fix it?
> > >
> > >
> >
> >
> > --
> > Gregory Kick
> > http://kickstyle.net/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Gregory Kick-2
Well, without a better idea of what you're trying to do, I'm out of
ideas.  Would you want to send some snippets of your pom for a better
idea of what might be causing it?  Console output (with -X) might be
good for the point where it dies also.

On 4/19/07, Nigel Magnay <[hidden email]> wrote:

> Don't think it'd help - the tests use ant, running ant is killing hudson...
>
> I don't see why this should kill everything - mvn reactor builds run fine
> without the ant plugin stopping the JVM (which seems to shutdown
> gracefully..)
>
>
> On 19/04/07, Gregory Kick <[hidden email]> wrote:
> >
> > Could you split it into multiple tests?
> >
> > On 4/19/07, Nigel Magnay <[hidden email]> wrote:
> > > Can't - the integration test is very involved and the server goes up and
> > > down 3 or 4 times...
> > >
> > >
> > > On 19/04/07, Gregory Kick < [hidden email]> wrote:
> > > >
> > > > Remove the line that says System.exit()?  :-)
> > > >
> > > > I would say that if you're having problems running cargo via ant, use
> > > > the cargo maven plugin and invoke the cargo:stop goal instead.  It'll
> > > > probably be safer for maven execution.
> > > >
> > > > On 4/19/07, Nigel Magnay <[hidden email] > wrote:
> > > > > One of my project modules is an 'integration' test. This uses the
> > > maven-ant
> > > > > plugin to run a number of scripts, bringing up an app server (using
> > > cargo),
> > > > > and a few other things.
> > > > >
> > > > > It all runs fine, but at the end of the tests, the shutting down of
> the
> > > > > ant/maven process seems to kill off the entire JVM (tomcat comes
> down
> > > with
> > > > > it)
> > > > >
> > > > > This obviously isn't right... is there any simple way to fix it?
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Gregory Kick
> > > > http://kickstyle.net/
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail:
> > > [hidden email]
> > > > For additional commands, e-mail: [hidden email]
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Gregory Kick
> > http://kickstyle.net/
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>


--
Gregory Kick
http://kickstyle.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: running test project kills hudson

Kohsuke Kawaguchi
Administrator
In reply to this post by Nigel Magnay
Nigel Magnay wrote:
> One of my project modules is an 'integration' test. This uses the maven-ant
> plugin to run a number of scripts, bringing up an app server (using cargo),
> and a few other things.
>
> It all runs fine, but at the end of the tests, the shutting down of the
> ant/maven process seems to kill off the entire JVM (tomcat comes down with
> it)

Could you elaborate on what you mean by "the entire JVM"? There are more
than one JVMs involved here. At least the one for Hudson, one that runs
Ant, then another that runs the container.

Which JVMs are shut down when which one goes down?

Is this the freestyle project or the alpha m2 support?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment