We are running OpneMRS Platform on Tomcat, and are using a set of modules available in openmrs-2.2-modules.zip downloaded from Sourceforge. All modules except appointmentschedulingui module work fine. Version of appointmentschedulingui module is 1.0.2. Problem is that module can’t be started. The error that is displayed in the openmrs.log file I pasted to pastebin here
It seems that root cause is Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry ‘c1bf0730-e69e-11e3-ac10-0800200c9a66’ for key ‘serialized_object_uuid_index’. However, I’m not sure what caused this and how to resolve it. Any help would be appreciated.
No, just trying to start the platform with Appointment scheduling module included. All the modules with listed versions are successfully working in our other environments except this one. Therefore, I am sure the problem is not related to the versions of the platform or the module.
The exception in the log (com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException) seems to be confirming that. The question is how did it happen that a duplicate entry with key “c1bf0730-e69e-11e3-ac10-0800200c9a66” is trying to be inserted into DB, and most important, how to resolve it?
Hi Everyone,
can it contain a feature that scheduling is linked to (sun beam inside the
clinic or examination room)? I think this can be derived from the early
ancestors of medicine who used to relate what they do to the (light and
movement of stars in the galaxy)
Yes, it works. However the issue will happen again after every restart.
Any idea why it happens in the first place? I mean why the id is created and tried to be recreated on every restart?
It is exactly same exception as in the first post, see the link to pastebin in the first post. Basically module is trying to insert a record into serialized_object table with already existing UUID. Question is, why does this module keep trying to insert this record each time OpenMRS is restarted?
I am running into the same issue. I can start the module through the new/owa “Manage Modules” interface once the rest of the application is started. I haven’t found the entry yet, but will try that as well. Has anyone found a “fix” that does not require additional action before or after every restart?
