Cubewise Application Server Issues


#1

Hi All

We intermittently experience issues with our Cubewise Application Server service on our development server. Today, for example, the service is constantly using around 20% CPU for no apparent reason. There are no other users using it.

This means Canvas is just failing to respond via a browser - not loading pages, not saving actions, etc.

After restarting the service Canvas will respond for a minute or two, but then starts churning the CPU and failing to respond again.

Any suggestions?

Thanks
David


#2

Hi David,

What is your Canvas and TM1 version?

How many Canvas application do you have on this server (How many folders inside webapps folder)?

Cheers,

Vincent


#3

Hi Vincent

We are on TM1 version 10.2.2. Not sure which Canvas version we have, how can I check?

We have 10 Canvas applications in the webapps folder.

The issue has arisen today after creating a new application, not sure if it’s related to that or not. I have been developing off and on for the last two weeks with no issues.

Thanks
David


#4

Hi David,

Yes it is related, the more application folder you have, the more memory Canvas needs (the Java Virtual Machine needs). If you create a new folder under webapps, you need to increase the Java Virtual Machine memory.

A general recommendation is to have 500MB per application. Each folder that is created in the webapps directory has its own context which means resources aren’t shared, i.e. the ROOT and samples directories.
The amount of memory required will also be increased depending on the number of users and size of requests.

Once the JVM (Java Virtual Machine) of the Cubewise Application Server has reached this value, it will slow down because it has to make some spaces for the new objects by deleting unused objects in order to keep the memory below 1024 MB, this is called garbage collector.

Steps to update the JVM maximum memory are explained in this article:

To check the Canvas version, you can go to the About page:
http://:8080//#/about

Cheers,


#5

Hi Vincent

That has helped the problem for now, however, despite setting the maximum memory to 6000mb the service is still limiting itself to just over 1000mb. Is there any other setting we should change? It crashed once soon after applying the changes but has been running fine since.

Our development Canvas version is 1.2.1.

Thanks
David


#6

Hi David,

When you set the maximum memory to 6000MB, it does not mean that Canvas will use it. It will use it only if it needs.

The Cubewise Application Server should not crash. If the crash happens again, send the logs to your Cubewise Local contact.

Cheers,


#7

Hi Vincent

Thanks for your help, it has been running fine since the last post.

Cheers
David