Have it fixed now. Increased -Xmx in /etc/cloud/management/tomcat6.conf and restarted services.
Best regards, David Comerford ------------------------ Tel: +353 87 1238295 Email: davest...@gmail.com Website: http://dave.ie GPG key: http://gpg.dave.ie On 23 July 2013 03:23, Dave Dunaway <dave.duna...@gmail.com> wrote: > Dynamically, only because it's not otherwise specified in the options when > starting up the JVM. You can edit the script it calls (check the > /etc/init.d/cloud-usage script for the actual name) and add in some -Xmx > 1024mb or something and see how that works. > > Could also be a ulimit rather than an actual memory allocation issue. Check > that the user running the service can allocate enough resources to the jvm > (virtual, open files, etc) so it can create enough threads. The error you > posted seems like it dies off pretty quickly but that it can at least start > the JVM up, so checking ulimits shed some light. > > hth. > > > On Mon, Jul 22, 2013 at 7:56 PM, David Comerford <davest...@gmail.com > >wrote: > > > If I understand you correctly your saying it's dynamically determined > when > > it starts? > > If that's the case, why is this instance failing to start with ~13GB of > > memory free (including buffers/cache) > > > > > > Best regards, > > David Comerford > > ------------------------ > > Tel: +353 87 1238295 > > Email: davest...@gmail.com > > Website: http://dave.ie > > GPG key: http://gpg.dave.ie > > > > > > On 22 July 2013 21:27, Dave Dunaway <dave.duna...@gmail.com> wrote: > > > > > The mgmt server will get started as a webapp out of Tomcat, so you can > > > check the /etc/cloud/management/tomcat6.conf in which you see it is set > > to > > > use -Xmx1024m . The usage server is not part of tomcat and does not > > specify > > > an -Xmx so it used the runtime determine value based on config and > > > resources. > > > > > > hth. > > > > > > > > > > > > > > > > > > On Mon, Jul 22, 2013 at 2:44 PM, David Comerford <davest...@gmail.com > > > >wrote: > > > > > > > Don't see anything like there in server.xml. > > > > There is some useful JAVA_OPTS in /etc/cloud/tomcat6.conf but I don't > > > know > > > > if that's specific to cloud-management or shared with cloud-usage. > > > > > > > > Any thoughts? > > > > > > > > Best regards, > > > > David Comerford > > > > ------------------------ > > > > Tel: +353 87 1238295 > > > > Email: davest...@gmail.com > > > > Website: http://dave.ie > > > > GPG key: http://gpg.dave.ie > > > > > > > > > > > > On 22 July 2013 15:38, Dean Kamali <dean.kam...@gmail.com> wrote: > > > > > > > > > it should be somewhere in server.xml > > > > > > > > > > > > > > > On Mon, Jul 22, 2013 at 9:20 AM, David Comerford < > > davest...@gmail.com > > > > > >wrote: > > > > > > > > > > > Hi list, > > > > > > > > > > > > Anyone know where the Java heap size is defined for cloud-usage > > > server? > > > > > > And is it a shared heap with cloud-management? > > > > > > > > > > > > I've got an upset usage server that wants more memory. > > > > > > > > > > > > 11:18:39,444 INFO UsageManagerImpl:232 - Starting Usage Manager > > > > > > 2013-07-22 11:18:39,444 INFO [cloud.usage.UsageManagerImpl] > > > > (main:null) > > > > > > Starting Usage Manager > > > > > > Exception in thread "main" java.lang.OutOfMemoryError: unable to > > > create > > > > > new > > > > > > native thread > > > > > > at java.lang.Thread.start0(Native Method) > > > > > > at java.lang.Thread.start(Thread.java:657) > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943) > > > > > > at > > > > > > > > > > > > > > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor.prestartCoreThread(ThreadPoolExecutor.java:1536) > > > > > > ....more exception trimmed.... > > > > > > > > > > > > Best regards, > > > > > > David Comerford > > > > > > ------------------------ > > > > > > Tel: +353 87 1238295 > > > > > > Email: davest...@gmail.com > > > > > > Website: http://dave.ie > > > > > > GPG key: http://gpg.dave.ie > > > > > > > > > > > > > > > > > > > > >
