I was watching the videos and really helped me a lot. I learned how to install a server (CentOS 6.7) with Bahmni projects. I learned how to install the dcm4chee project from the repository Bahmni. I did tests and I could see that dcm4chee working properly.
Then in the section Setup PACS Integration module there is not much information on how to integrate these two projects (Bahmni MRS and DCM4CHEE). Analyzing the installation guide and I concluded that these commands would be sufficient.
yum install -y dcm4chee pacs-integration
I do some tests and found that there is no conflict, if you use ports other than 8080 and 8083. For my case, Iâm using DCM4CHEE ports in 8088 and 8089, and now works perfect.
According to the installation guide, you should have access to this URL: http://ipaddress:8080/pacs-integration, but when I try to enter the URL, I have no answer. I checked the PostgreSQL database, can not find the tables Modality, Order Type and Markers.
Iâm sorry for not answer quickly. I was testing the installation process of pacs-integration. I could see that after installing pacs-integration, bahmni_pacs data base is created, but it does not contain tables. Can you help me to create these tables? I mean, do you have a script to create the tables (Modality, Order_Type and Markers)?
I had another observation, the bahmni-pacs service does not start. I start the service manually with the command:
sudo service bahmni-pacs start
The terminal shows: Starting bahmni-pacs
But, if I run the command:
sudo service bahmni-pacs status
The terminal shows: Service bahmni-pacs is not running
Is there a log file, to see if there is an error during the service start?.
I hope you can help me. I will be grateful with you.
After testing With pacs/dcm4chee, I found that this works perfectly but independently. I have not tested with bamhni, pacs-integration and pacs. I will review the log generated by the pacs-integration and I will share this.
I have not attempted the data setup section in the postgres database. Working on that now.
Opening ip:8001/dcm4chee-web3 and ip:8001/oviyam2 gives issues.
ip:8001/dcm4chee-web3 shows:
Internal error Throwable: ITab.getPanel() returned null. TabbedPanel [0:modules] ITab index [0] Page: class org.apache.wicket.Page
Choosing âDesktopâ or âReading roomâ on the page gives:
Internal error Throwable: Attempt to set model object on null model of component: modules:cssSelect Page: class org.apache.wicket.Page
and ip:8001/oviyam2 gives me 404.
Quick question: Wouldnât dcm4chee and oviyam still work independently without data setup for the pacs integration?
Hi Daniel Ng,
The errors you are seeing are probably because dcm4chee (JBoss) hasnât started up properly. I was recently seeing this error wherein another service that dcm4chee was trying to start up wasnât starting up due to a port conflict in the new Ansible setup that we are trying
Can you check in the logs to find the cause?
You would find the logs here : /var/lib/bahmni/dcm4chee-2.18.1-psql/server/default/log/server.log
Once started properly, both dcm4chee and oviyam2 would work independently without data setup of pacs-integration.
Yes. the screenshots are from postgresql. Those are the tables where you have to add rows to
Map the modality/PACS to which pacs-integration would send ORM message
Map the order type to modality
set the markers table for the atom feed reader to pick up latest entries.
You might have to look a little up in the logs.
For me doing the vi shows up this as a first line when the issue exists
2016-04-04 14:44:04,424 WARN -> (main) [org.jboss.system.ServiceController] Problem starting service jboss:service=WebService
java.lang.Exception: Port 8083 already in use.
I am not sure if its the same issue for you. But you can check for it to confirm.
If the issue is about port conflict, you can alternatively confirm what port dcm4chee is trying to start in this file /var/lib/bahmni/dcm4chee-2.18.1-psql/server/default/conf/jboss-service.xml and iptables or netstat will tell you anything else is running on that port
When i faced the issue i noticed both dcm4chee webservice and bahmni-reports were configured to run on 8083.
The workaround that i am applying for now, till the time the team fixes it properly, is to stop the bahmni-reports service and then restart dcm4chee.
But i am trying out the latest Ansible that is not yet completely QAed and released.
Yes, I do have the same issue:
2016-04-03 17:21:01,918 WARN -> (main) [org.jboss.system.ServiceController] Problem starting service jboss:service=WebServicejava.lang.Exception: Port 8083 already in use.
Regarding the xml file, there are these lines of code that seem to denote port 8083âs use:
http://pastebin.com/M0HyJKHJ
Unfortunately, iptables -L doesnât show me any rules. I am running on Googleâs Cloud Platform so Iâm not sure if that has a role.
Noted about the workaround, maybe I will try it later. Hope itâll be solved soon!
I have been trying to setup bahmni-pacs without success.
When i start the service manually with the command:
sudo service bahmni-pacs start
The terminal shows: Starting bahmni-pacs
But, if I run the command:
sudo service bahmni-pacs status
The terminal shows: Service bahmni-pacs is not running
After checking my bahmni-pacs.log, i found this.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaAutoConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: javax.persistence.spi.PersistenceUnitInfo.getValidationMode()Ljavax/persistence/ValidationMode;
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1574)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:303)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:299)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:956)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:747)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:480)
at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:118)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:686)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:320)
at org.springframework.boot.context.web.SpringBootServletInitializer.run(SpringBootServletInitializer.java:117)
at org.springframework.boot.context.web.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:108)
at org.springframework.boot.context.web.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:68)
at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:175)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5164)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoSuchMethodError: javax.persistence.spi.PersistenceUnitInfo.getValidationMode()Ljavax/persistence/ValidationMode;
at org.hibernate.jpa.boot.internal.PersistenceUnitInfoDescriptor.getValidationMode(PersistenceUnitInfoDescriptor.java:99)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.mergePropertySources(EntityManagerFactoryBuilderImpl.java:569)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:214)
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.<init>(EntityManagerFactoryBuilderImpl.java:188)
at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider$1.<init>(SpringHibernateJpaPersistenceProvider.java:49)
at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:49)
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:343)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:318)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1633)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
... 24 common frames omitted
I have been stuck with this for days. Can you please help.
Hi @shobhab,
Not sure why should you get this error. Are these the full error logs? Also, can you describe a little more as to how you went about installing this and what is the version of bahmni-pacs installed?
Actually we are very close to doing 0.81 release, in which bahmni-pacs has been renamed to pacs-integration and setup made a bit easier. If you can wait for about a week and then take the new release, it would be bit easier to support.
@shobhab I have the same problem, the file pacs-integration.log showâs this.
pacs-integration.txt (32.1 KB)
Do you could solve this problem? Someone knows, why have that problem?
