rhc ssh -a app
rhc app-stop testappname --namespace domainname
rhc app --help
rhc tail -a pagemonitor -f jbosseap/standalone/log/server.log
https://github.com/openshift/wordpress-example/tree/master/.openshift/action_hooks
http://openshift.github.io/documentation/oo_user_guide.html#the-openshift-directory
https://www.openshift.com/forums/openshift/how-to-increase-the-max-heap-size-for-jboss
This value is calculated in bin/standalone.conf in the jbosseap cartridge, based on how much memory is allocated to your gear (512MB for small gears). I think you might be able to set JAVA_OPTS in your own way in a pre-start hook, but be aware that doing so will greatly increase the probably that your app will run out of memory (and be killed). If you switch to a medium gear, the value will automatically be set higher.
rhc app-stop testappname --namespace domainname
rhc app --help
rhc tail -a pagemonitor -f jbosseap/standalone/log/server.log
https://github.com/openshift/wordpress-example/tree/master/.openshift/action_hooks
http://openshift.github.io/documentation/oo_user_guide.html#the-openshift-directory
https://www.openshift.com/forums/openshift/how-to-increase-the-max-heap-size-for-jboss
This value is calculated in bin/standalone.conf in the jbosseap cartridge, based on how much memory is allocated to your gear (512MB for small gears). I think you might be able to set JAVA_OPTS in your own way in a pre-start hook, but be aware that doing so will greatly increase the probably that your app will run out of memory (and be killed). If you switch to a medium gear, the value will automatically be set higher.
No comments:
Post a Comment