Can I get a log of what errors you are experiencing
Let me try to compile again. In the meantime, just for troubleshooting purposes, try replacing auto wiring and see if it helps. That is, replace the autowired annotations with setting these dependencies in the spring application context file.
Alright. Trying that right now
Man it worked. You are a life saver man. It worked perfectly. Ran in about 2 minutes
The only challenge I am facing right now is that the I cant seem to be able to inject the “DbSessionFactory” bean. How do I do this?
Are you looking for something like this? https://github.com/openmrs/openmrs-module-chartsearch/blob/8678820a29a299564ccfeb6197fd926634a8ef4e/api/src/main/resources/moduleApplicationContext.xml#L78
Most definetly. Thanks alot.
@dkayiwa @ibacher This is happening again. and the culprit module is ugandaemrsync I have followed several posts and replicated the solutions they offer. Including this very post in this PR USM-24: Cleanup ugandaemrsync to reduce on then startup time of the application by slubwama · Pull Request #144 · METS-Programme/openmrs-module-ugandaemr-sync · GitHub. However, the system still is too slow. on start and Initializing EhCache CacheManager seems to be the place where it hangs. In the PR,
-
I have removed all wildcard imports.
-
I have removed all autowire except for DbSessionFactory.
-
Stopped all Scheduled tasks in ugandaemr to run on start.
I need your help checking this out to determine what I am doing wrong.
Thanks
In summary, how can i locally reproduce this problem?
- Setp-1: mvn openmrs-sdk:setup -Ddistro=org.openmrs.module:ugandaemr:4.0.0-SNAPSHOT to set up the server
- Setp-2: run this sql script to align the concept dictionary with the base as a base
- Setp-3: mvn openmrs-sdk:run to run the server
@slubwama do you also get this error in the logs? WARN - ModuleFactory.startModuleInternal(783) |2024-03-13T16:36:18,154| Error wh - Pastebin.com
@dkayiwa This error is coming from a this change set which i suspect changed without the ID changing. Before it had a runalways=true. and was causing lots of things to break especially on the reporting side.
Given that UgandaEMRSync requires reporting, also makes it fail to start the module since reporting won’t start with that error.
I am opting @dbaluku and @amugume in this conversation to help solve this.
Just like my suspicions here is the change to that Fixing mamba breaking (#354) · METS-Programme/openmrs-module-ugandaemr-reports@8cf5f59 · GitHub
@slubwama I think this is going to break the way mamba works especially on restoring databases or server migration . We rather break the dependency of out modules and find ways to achieve the dependency functionality