After the long investigation I found the issue. If i start the app using
/etc/init.d/cloudstack-management start I could see error as catalina.out
as Can't start up: not enough memory if I do the same using
/etc/init.d/tomcat.sh start I able to start the app. But @ the same time
when I check the b
Hi Keerthiraja,
I saw the issue you opened and closed recently (CLOUDSTACK-8404), looks like
the jdk-1.8 caused the issue? I guess the requirement we’ve in cloud.spec is >=
java 1.7.0 so if java 1.8 is available it would get installed.
> On 27-Apr-2015, at 8:59 am, Keerthiraja SJ wrote:
>
> Af
Hi Keerthiraja,
We are on 4.3.0.2 - So I am not sure it the tomcat6-nonssl.conf differs. I
looked at your JAVA_OPTS line and mine,
Your Line:
JAVA_OPTS="-Djava.awt.headless=true -Dcom.sun.management.jmxremote=false -Xmx2g
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/var/log/cloudstack/m
Hi there :)
You didn't mention if you were running 32 or 64 bit OS... 32 bit JVM can't
scale over 1.4/1.6Gb Heap size, no matter what you put in the -Xmx option ;)
RF
On Mon, Apr 27, 2015 at 3:44 PM, Timothy Lothering <
tlother...@datacentrix.co.za> wrote:
> Hi Keerthiraja,
>
> We are on 4.3.0.
perhaps we need to patch and hard set java to = 1.7 (vs =>1.7) with arch
type of x86_64 - until we are ready with 1.8..
On 4/27/15 7:01 AM, Rafael Fonseca wrote:
Hi there :)
You didn't mention if you were running 32 or 64 bit OS... 32 bit JVM can't
scale over 1.4/1.6Gb Heap size, no matter wh
Hi,
Fixed on 4.5 now:
https://github.com/apache/cloudstack/commit/031d7a9c43c5082913064a39829ecefb2239c5ab
Latest 4.5 testing repo: http://packages.bhaisaab.org/cloudstack/testing
> On 27-Apr-2015, at 6:09 pm, ilya wrote:
>
> perhaps we need to patch and hard set java to = 1.7 (vs =>1.7) with
That won't fix it.. if the java-1.8.0-openjdk that will just install
java-1.7.0-openjdk next to it.. alternatives will probably still be
configured to run with 1.8.0.
If you actually want to be sure that it will run on java 7 you also need to
add a Conflicts: java-1.8.0-openjdk to the spec file so
