process and form fields and memory issue

Post any question regarding setting up, running or configuring Verj.io Workflow

Moderators: Jon, Steve, Ian, Dave

xren
Ebase User
Posts: 272
Joined: Fri Dec 14, 2012 2:55 pm
Location: Ottawa

process and form fields and memory issue

#1

Postby xren » Fri Jul 22, 2016 6:41 pm

Hello,

I had a process and a form for it. these two pass some fields between some.
one of the fields is really big.
I experience java heap out of memory issue. I wonder if the above is the reason.

Are all form fields exist in the sever memory during a client session is up?

Are all process fields exist in the server memory all the time during before a job is completed?

Where are the process fields are saved in the database? such that a job can be resumed after a server restart?

Thanks,
Xiaoli
0 x

Ian
Ebase Staff
Posts: 26
Joined: Wed Oct 10, 2007 9:40 am
Location: Ebase HQ
Contact:

re:process and form fields memory issue

#2

Postby Ian » Mon Jul 25, 2016 1:00 pm

Hi,

Can you let me know how much memory has been defined for you environment?
If you are running the system as a service you can find this information in the following file:
For a windows system
look in UfsServer/tomcat/bin/service.bat
Almost at the end of the file there a line that begins with "%EXECUTABLE%" //US//%SERVICE_NAME% ++JvmOptions".
Move to the very end of that line and you will see the memory settings.
These will look like this:
--JvmMs nnn --JvmMx nnnn (where nnn will be the value of your system)
The --JvmMs is the amount of memory that the server will start with and the
--jvmMx is the maximum amount of memory that the server can use.

If you are running the system in a Linux environment then depending on how you start your environment the memory settings can be found here:

If you are using the ebaseXi command file (found in UfsServer and also in /etc/init.d)
Memory setting are defined in the OPTS array.
OPTS[1]=' -Djava.awt.headless=true'
OPTS[2]=' -Dderby.system.home='$DERBY_HOME
OPTS[3]=' -server'
OPTS[4]=' -Xms128m'
OPTS[5]=' -Xmx2048m'

OPTS[6]=' -XX:+UseG1GC'
OPTS[7]=' -Dhttp.nonProxyHosts="localhost|127.0.0.1"'
OPTS[8]=' -Dfile.encoding=UTF-8'
OPTS[9]=' -Dmail.mime.charset=ISO-8859-1'
JAVA_OPTS=${OPTS[@]}

If you are using the start.sh file (found in UfsServer) the memory settings are found in the JAVA_OPTS line:
JAVA_OPTS='-Xmx512m


Regarding your question about could it be one of the fields that is causing the out-of-memory issue this will very much depend on just how much data you are storing in that field and also how much memory you have given to the system.

Regarding your question about where is the data stored in the case of a server restart (so that the job can continue).
There is no automatic saving of application data. This must be build into your application.
Ebase provides utilities to help you in this process.
Please have a look at the help on Save and Restore for a more detailed explanation on how to use these utilities.

Regards

Ian
0 x


Who is online

Users browsing this forum: No registered users and 2 guests