I am running Bahmni on a stand-alone CentOS box.Updates take place between OpenMRS and OpenElis but OpenERP is not getting updated.
Service openmrs is running with pid: 2633 and Service bahmni-erp-connect is running with pid: 2226. All I see for openERP is " openerp-server is running… " there is no pid assigned to it.
From the openerp database, customerFeedJobTrigger ‘enabled value = true’ and saleOrderFeedJobTrigger ‘enabled value = true’ .
The “markers” table of OpenERP is totally blank. It has no data at all.
When I do ‘select from markers’ this is what I get:
id | create_uid | create_date | write_date | write_uid | last_read_entry_id | f eed_uri_for_last_read_entry | feed_uri ----±-----------±------------±-----------±----------±-------------------±- ----------------------------±--------- (0 rows)
This is what i see on my machine when I run “ps -ef | grep erp” command:
I could see the initialization error while starting openerp-atomfeed-service. Can you restart the erp connect service?
You can do it by using “sudo service bahmni-erp-connect restart”
I have done that but the markers table is still empty. I have removed & re-installed both bahmni-erp-connect and bahmni-erp (openerp server) but the situation is still the same.
What puzzles me a bit though is when I do service -status-all, I see two (2) instances of openerp-server running concurrently, and both have no pid assigned to them.
Could that be a pointer to where the challenge is coming from?
====================================================
2016-02-05 13:31:30,536 WARN [openerp-atomfeed-service] [org.springframework.web.context.support.XmlWebApplicationContext] Exception thrown from ApplicationListener handling ContextClosedEvent
java.lang.IllegalStateException: ApplicationEventMulticaster not initialized - call ‘refresh’ before multicasting events via the context: Root WebApplicationContext: startup
After analyse the log, It is spring framework throwing the exception. This is because of java 1.8 version. Once we changed to java version 1.7 and restarted the machine, it works fine.
There were multiple java version installed in that machine. The following
command will help to choose the required Java version.
sudo update-alternatives --config java
The command will list all the installed java versions in that machine and
ask for choose the alternate version. After the version has been selected,
we can verify the java version again (using java -version) to make sure
that it is indeed selected properly.
Although I feel this is a workaround. In future, Bahmni should use the JAVA it needs, and not change the default system Java, because this can break other applications. Or, if some other application changed the system default JAVA, it will break Bahmni.
@bharatak suggested that a better approach will be that the “bahmni” user on the machine, should set its own JAVA_HOME, and maybe PATH variable, so that Bahmni service uses the right JAVA, and other components on the machine remain unaffected. We may need to put this in Mingle so that someone picks this up in future.