Reporting module on local instance

1 view
Skip to first unread message

Myles Barros

unread,
Mar 25, 2014, 1:27:36 AM3/25/14
to d...@openmrs.org
I have set up a local instance of OpenMRS on a machine for development using the guide on the wiki. I have also installed Demo data 1.9, the Serialization XStream module 0.2.7, the HTML Widgets module 1.6.6, the Calculation module 1.1, and the Reporting module 0.8.2.

The Reporting module adds a tab to the OpenMRS page however when I attempt to access that tab it causes Tomcat to crash.

Does anyone know what might be causing this issue and how I can make use of the Reporting module on my local instance?

Michael Seaton

unread,
Mar 25, 2014, 6:26:35 AM3/25/14
to d...@openmrs.org
Myles,

Sorry you are having issues getting reporting running.  Can you please send along more details as to the exact nature of the error?  Simply installing and accessing the reporting modules pages should not cause any particular problem.

Mike
--
OpenMRS Developers: http://go.openmrs.org/dev
Post: d...@openmrs.org | Unsubscribe: dev+uns...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@openmrs.org.

Myles Barros

unread,
Mar 26, 2014, 1:57:43 PM3/26/14
to d...@openmrs.org
I don't experience an explicit error when attempting to access the reporting module. Accessing the module causes Apache Tomcat to become unresponsive until the server is restarted.

In addition to the details described in the first post, I am running Tomcat 7.0.52.0 on a fresh install of Mac OS 10.7.4 (Desktop). The JVM is version 1.6.0_33-b03-424-11M3720.

Let me know if there are any additional details that would help determine the cause of the problem.

Darius Jazayeri

unread,
Mar 26, 2014, 2:01:05 PM3/26/14
to dev
Have you increased the available JVM memory settings per https://wiki.openmrs.org/x/gxAz ?

-Darius

Myles Barros

unread,
Mar 28, 2014, 10:28:12 AM3/28/14
to d...@openmrs.org
I've increased the JVM memory settings in excess of a gigabyte based on the instructions provided and the behavior persists. I'm sure I would have run up against memory issues inevitably, though, so thank you for the assistance none the less.

Are there any other possible causes for the issue? Are there any known idiosyncrasies with the module installation or its dependencies?

While adding several of the modules to the OpenMRS instance I experienced similar problems wherein, after uploading, the tomcat server would similarly become non-responsive and require a restart. Is it possible that this could have done damage to the modules or hint at the underlying cause?
Reply all
Reply to author
Forward
0 new messages