|
|
|
Re: Virgo automatically stops [message #999096 is a reply to message #997831] |
Fri, 11 January 2013 10:33 |
|
Hi,
Did you see any increase in the memory after running over night. For what it is worth, I run the Virgo build and integration tests with '-Xms256M -Xmx2048M -XX:PermSize=256M -XX:MaxPermSize=1024M' or something similar.
Chris
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
Re: Virgo automatically stops [message #999103 is a reply to message #999096] |
Fri, 11 January 2013 10:53 |
Miguel Salinas Gancedo Messages: 8 Registered: October 2012 |
Junior Member |
|
|
Hi,
I think that the memory is not he problem, because with develop with this configuration in my mac and ubuntu local OS and also we have a production virgo instance in other AWS VM with this memory configuration, and we don't have any problem, but with this AWS instance yes we have problems. The only unique difference is that the AWS instance with the problem is Ubuntu 10.04 and the other one is 12.04, we have the same JDK the Oracle JDK, the same amount memory, CPU and Hard Disk, but I take this account your porpouse. Thanks.
I hope that the problem would be that I start the Virgo process from ssh shell and don't use any daemon to start the virgo process. Today, I just create a daemon script in my AWS instance and start virgo like a daemon process, I'll wait all the day to obtain any result, i hope this resolve the ghost problem . Normally the virgo process only is up during two hours and a half, always the same amount of time more and less, so is like a timeout inside OS that stop my virgo process. I hope that a virgo process daemon resolve this problem, if not I don't have any idea about what happend with my virgo process in AWS ;(
Waiting for any result ....
Best regards.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03789 seconds