Can we stop it just by keeping track of the processes and then killing them? I'm assuming cargo doesn't have some sort of standard shutdown thing that each container that it controls can implement.
On Sep 27, 2007, at 8:40 AM, Eugene Kuleshov wrote: > Steve, > > I forgot to mention that I've been using Cargo 1.0-SNAPSHOT build > from > its svn trunk. > > Also note, that I am not yet satisfied with the current > configuration > and still not sure if we should keep it in tc:run and process > configuration. It is kinda neat to start multiple containers and plain > Java processes at the same time, but it is unclear how to stop cargo > processes in that case. > > regards, > Eugene > > > Steven Harris wrote: >> This is really cool. I'm going to try to play with it either later >> today or tomorrow. >> Cheers, >> Steve >> >> On Sep 26, 2007, at 1:38 PM, Eugene Kuleshov wrote: >> >> >>> I've just committed some experimental support for cargo to >>> tc-maven-plugin. >>> >>> There are still some issues that are getting into the way of using >>> this stuff. See jira CDV-435 for more details >>> >>> To workaround those issues before CDV-435 is resolved, I've >>> renamed >>> module jars in my local maven repository, so they actually match >>> expected versions and DSO can be started from Maven. >>> >>> There is a new example project >>> \tc-maven-plugin\examples\tc-maven-webapp that is illustrating how >>> tc:run goal could start tomcat with DSO enabled (I haven't tested >>> with >>> other containers yet, but there is also profile for Jetty 6x). For >>> example: >>> >>> mvn -Ptomcat5x clean package tc:run >>> >>> that will download, install, configure, deploy tc-maven-webapp and >>> start two tomcat servers with Terracotta clustering enabled. After >>> they >>> started you can check web app at http://localhost:8080/tc-maven- >>> webapp/ >>> >>> The issue I hit into is that web app containers started this way >>> can't >>> be stopped. I am planning add new goals to deal with that: >>> tc:container-start and tc:container:stop will be practically a >>> clustered >>> equivalent of Cargo's cargo:start and cargo:stop goals. Then you >>> could >>> wire them up like this: >>> >>> <plugin> >>> <groupId>org.terracotta.maven.plugins</groupId> >>> <artifactId>tc-maven-plugin</artifactId> >>> >>> <numberOfNodes>2</numberOfNodes> >>> >>> <configuration> >>> <wait>false</wait> >>> </configuration> >>> >>> <executions> >>> <execution> >>> <id>start</id> >>> <phase>pre-integration-test</phase> >>> <goals> >>> <goal>container-start</goal> >>> </goals> >>> </execution> >>> <execution> >>> <id>stop</id> >>> <phase>post-integration-test</phase> >>> <goals> >>> <goal>container-stop</goal> >>> </goals> >>> </execution> >>> </executions> >>> </plugin> >>> >>> Any thoughts or comments are very welcome. >>> >>> regards, >>> Eugene >>> >>> >>> > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
