2014_2_13_warden

2014_2_13修改tuscnay

> Written with [StackEdit](https://stackedit.io/).

错误日志dea.log:
   

        droplet.healthy
        start instance
        InfoResponse
        LinkResponse
        droplet.warden.link.complete
        droplet.instance.uptime
    
解释：
An application is run in a warden container by spawning a "job" (using the warden "spawn" operation). Spawn returns a job id. The result of the job can later be retrieved using the warden "link" operation specifying the job id. There is a brief description of the protocol in the protocol buffer definitions of these operations: spawn, link.

link blocks until a response from the job is available. After link completes, the job is removed.

In  dea.log, the response from link contains an exit_status of 0. I'm not sure why this is 0 unless this is the exit status of the process which launches the JVM rather than of the JVM itself. This is followed by a "copy out" request which copies from the container path /home/vcap/ to /tmp/dea_ng/crashes/47c8fb7b5d35540202c930697d6fa7ef presumably to capture logs before the warden container is destroyed (via the destroy operation).


----------


sudo monit status 用来监考warden server的状态,[参考官网blog/warden][1]

尝试在tuscany-buildpack中，使用一个替代脚本circle.sh来占位。
运行成功后，进入warden-client，手动启动tuscany应用。
根据status来看，不是内存的问题。

tuscany启动的jvm 进程被kill了。是因为程序运行结束了？

继续怀疑，交互式应用？？？
CF可以部署java-main应用，之前写的是一个循环，现在改成一个等待命令行输入的应用。




  [1]: http://docs.cloudfoundry.com/docs/running/troubleshooting/troubleshooting-warden-services.html