This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
···
Hello everyone,
I am a new user of DHIS2. I am working with a DHIS2 application that has already been installed last year inside an Amazon cloud web server. The version that we have is DHIS2 2.19. The Tomcat version is 1.7. All the data elements, organization unit and questionnaires have been integrated into the system.
We are observing odd situation such as Tomcat is crashing each time a couple of users (15+) are accessing DHIS2 simultaneously, especially when they are using the DHIS2 Data Capture within tablets. DHIS2 is only back after restarting Tomcat.
Do you know the Server and JVM memory specifications that are recommended to expect about 300 concurrent DHIS2 users?
Here are some Java environment variables and server caracteristics that we are using:
Please include the logs of the server when it crashes as this will help to diagnose what the issue might be.
Regards,
Jason
···
On Fri, Mar 18, 2016 at 12:43 PM, Raminosoa Rabemanantsoa, Tantely traminosoa@mikolo.org wrote:
Hello everyone,
I am a new user of DHIS2. I am working with a DHIS2 application that has already been installed last year inside an Amazon cloud web server. The version that we have is DHIS2 2.19. The Tomcat version is 1.7. All the data elements, organization unit and questionnaires have been integrated into the system.
We are observing odd situation such as Tomcat is crashing each time a couple of users (15+) are accessing DHIS2 simultaneously, especially when they are using the DHIS2 Data Capture within tablets. DHIS2 is only back after restarting Tomcat.
Do you know the Server and JVM memory specifications that are recommended to expect about 300 concurrent DHIS2 users?
Here are some Java environment variables and server caracteristics that we are using:
Server memory: Mem Total in JVM: 1243 Free in JVM: 547 Max Limit: 1820
CPU cores: 2
Server RAM: 3.75 G
Thank you for your support!
Tantely.
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
As Jason say, we need a bit more information. Also I would recommend upgrading to Java 8 (as Java 7 is end-of-line, and not supported anymore), at the same time upgrading Tomcat to the latest would probably be a good idea.
Including the server log at the time of crash is a good start (I would guess it’s memory related if it’s tomcat itself that crashes…)
On Fri, Mar 18, 2016 at 12:43 PM, Raminosoa Rabemanantsoa, Tantely traminosoa@mikolo.org wrote:
Hello everyone,
I am a new user of DHIS2. I am working with a DHIS2 application that has already been installed last year inside an Amazon cloud web server. The version that we have is DHIS2 2.19. The Tomcat version is 1.7. All the data elements, organization unit and questionnaires have been integrated into the system.
We are observing odd situation such as Tomcat is crashing each time a couple of users (15+) are accessing DHIS2 simultaneously, especially when they are using the DHIS2 Data Capture within tablets. DHIS2 is only back after restarting Tomcat.
Do you know the Server and JVM memory specifications that are recommended to expect about 300 concurrent DHIS2 users?
Here are some Java environment variables and server caracteristics that we are using:
Server memory: Mem Total in JVM: 1243 Free in JVM: 547 Max Limit: 1820
CPU cores: 2
Server RAM: 3.75 G
Thank you for your support!
Tantely.
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
···
On Fri, Mar 18, 2016 at 2:58 PM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Tantely
As Jason say, we need a bit more information. Also I would recommend upgrading to Java 8 (as Java 7 is end-of-line, and not supported anymore), at the same time upgrading Tomcat to the latest would probably be a good idea.
Including the server log at the time of crash is a good start (I would guess it’s memory related if it’s tomcat itself that crashes…)
On Fri, Mar 18, 2016 at 12:43 PM, Raminosoa Rabemanantsoa, Tantely traminosoa@mikolo.org wrote:
Hello everyone,
I am a new user of DHIS2. I am working with a DHIS2 application that has already been installed last year inside an Amazon cloud web server. The version that we have is DHIS2 2.19. The Tomcat version is 1.7. All the data elements, organization unit and questionnaires have been integrated into the system.
We are observing odd situation such as Tomcat is crashing each time a couple of users (15+) are accessing DHIS2 simultaneously, especially when they are using the DHIS2 Data Capture within tablets. DHIS2 is only back after restarting Tomcat.
Do you know the Server and JVM memory specifications that are recommended to expect about 300 concurrent DHIS2 users?
Here are some Java environment variables and server caracteristics that we are using:
Server memory: Mem Total in JVM: 1243 Free in JVM: 547 Max Limit: 1820
CPU cores: 2
Server RAM: 3.75 G
Thank you for your support!
Tantely.
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
On Fri, Mar 18, 2016 at 2:58 PM, Morten Olav Hansen <morten@dhis2.org> > wrote:
Hi Tantely
As Jason say, we need a bit more information. Also I would recommend
upgrading to Java 8 (as Java 7 is end-of-line, and not supported anymore),
at the same time upgrading Tomcat to the latest would probably be a good
idea.
Including the server log at the time of crash is a good start (I would
guess it's memory related if it's tomcat itself that crashes....)
On Fri, Mar 18, 2016 at 6:50 PM, Jason Pickering >> <jason.p.pickering@gmail.com> wrote:
Hi Tantely,
Please have a look at our guidelines for reporting a problem.
Please include the logs of the server when it crashes as this will help
to diagnose what the issue might be.
Regards,
Jason
On Fri, Mar 18, 2016 at 12:43 PM, Raminosoa Rabemanantsoa, Tantely >>> <traminosoa@mikolo.org> wrote:
Hello everyone,
I am a new user of DHIS2. I am working with a DHIS2 application that has
already been installed last year inside an Amazon cloud web server. The
version that we have is DHIS2 2.19. The Tomcat version is 1.7. All the data
elements, organization unit and questionnaires have been integrated into the
system.
We are observing odd situation such as Tomcat is crashing each time a
couple of users (15+) are accessing DHIS2 simultaneously, especially when
they are using the DHIS2 Data Capture within tablets. DHIS2 is only back
after restarting Tomcat.
Do you know the Server and JVM memory specifications that are
recommended to expect about 300 concurrent DHIS2 users?
Here are some Java environment variables and server caracteristics that
we are using:
Server memory: Mem Total in JVM: 1243 Free in JVM: 547 Max Limit:
1820
CPU cores: 2
Server RAM: 3.75 G
Thank you for your support!
Tantely.
This message and its attachments are confidential and solely for the
intended recipients. If received in error, please delete them and notify the
sender via reply e-mail immediately.
_______________________________________________
Mailing list: DHIS 2 Users in Launchpad
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : DHIS 2 Users in Launchpad
More help : ListHelp - Launchpad Help
--
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
This message and its attachments are confidential and solely for the
intended recipients. If received in error, please delete them and notify the
sender via reply e-mail immediately.
--
Jason P. Pickering
email: jason.p.pickering@gmail.com
tel:+46764147049
This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.
