issues getting 1.7 data to 1.8
Hi
I have 1.8 running and it seems to work fine with the sample data, i have updated all references of the database from 'openvpms-1_8' to 'openvpms'. The data is currently working with 1.7, i have run the 1.7-1.8 update script located at
\openvpms-release\src\update\db\
but when i try to run i get the following error:
Error creating bean with name 'hl7Connectors' defined in ServletContext resource [/WEB-INF/openvpms-hl7.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.openvpms.hl7.impl.ConnectorsImpl]: Constructor threw exception; nested exception is org.openvpms.component.business.service.archetype.ArchetypeServiceException: Failed to execute query: ArchetypeQuery[firstResult=0,maxResults=25,count=false,constraints=ShortNameConstraint[constraints={},alias=<null>,state=ACTIVE,primaryOnly=true,shortNames={entity.HL7Sender*,entity.HL7Receiver*}]].
Caused by: org.openvpms.component.business.dao.hibernate.im.query.QueryBuilderException: Could not find any matching archetypes for short names {entity.HL7Sender*,entity.HL7Receiver*}
It must be something else im doing, i ran a database comparison tool and it is the same structure.
Re: issues getting 1.7 data to 1.8
might be data related? i setup the data from scratch using mvn, it ran fine but couldnt login as there is no data. I then used mysql workbench to import the data, i only selected to import the data no structure changes and it no longer works.
Re: issues getting 1.7 data to 1.8
Did you reload the archetypes from the 1.8 installer
Re: issues getting 1.7 data to 1.8
If the data was 1.7 data then it doesnt have the correct archetypes ...update he sql run archload and then try and fire up the webapp
Re: issues getting 1.7 data to 1.8
i ran the following, which worked, and it seemed liked its running but im getting a 404 page.
25 Jun 2015 08:15:03,530 ERROR MessageDispatcherImpl,localhost-startStop-1:706 - - Missing party.organisationPractice serviceUser. Messages cannot be sent until this is configured
25 Jun 2015 08:15:03,541 INFO MessageDispatcherImpl,localhost-startStop-1:328 - - HL7 message dispatcher initialised
25 Jun 2015 08:15:03,555 DEBUG MessageDispatcherImpl,localhost-startStop-1:512 - - No service user. Schedule request ignored
25 Jun 2015 08:15:04,691 INFO StyleSheetCache,localhost-startStop-1:135 - - Loading stylesheet style/default.stylesheet
25 Jun 2015 08:15:04,756 INFO StyleSheetCache,localhost-startStop-1:97 - - No style overrides found for: style/site.properties
25 Jun 2015 08:15:04,778 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 480x320 from style/default-480x320.properties
25 Jun 2015 08:15:04,779 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 640x480 from style/default-640x480.properties
25 Jun 2015 08:15:04,811 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 768x1024 from style/default-768x1024.properties
25 Jun 2015 08:15:04,811 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 1280x800 from style/default-1280x800.properties
25 Jun 2015 08:15:04,812 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 800x600 from style/default-800x600.properties
25 Jun 2015 08:15:04,812 INFO StyleSheetCache,localhost-startStop-1:192 - - Adding resolution 1024x768 from style/default-1024x768.properties
25 Jun 2015 08:15:04,904 INFO SessionMonitor,localhost-startStop-1:94 - - Using default session auto-lock time=5 minutes
25 Jun 2015 08:15:04,904 INFO SessionMonitor,localhost-startStop-1:95 - - Using default session auto-logout time=30 minutes
Re: issues getting 1.7 data to 1.8
Nothing untoward shown in that portion of the log. The "Missing party.organisationPractice serviceUser. Messages cannot be sent until this is configured" is coming from the HL7 service and won't affect startup.
What URL are you using? By default, OpenVPMS will be running at http://localhost:8080/openvpms/login
Is there any other errors prior to that in openvpms-full.log? If you're running using maven, the logs are under openvpms-web/openvpms-web-app/target/tomcat/logs.
Note that if you migrate data, you need to restart tomcat.
Re: issues getting 1.7 data to 1.8
didnt think anything looked wrong with it, im using the address http://localhost:8080/openvpms/
which does seem to work with the sample data that i load just not with migrated data. That was the full log from the main openvpms log file.
Im might re-initialise the data, so steps should be
1. import data from backup
2. run 1.7 - 1.8 sql update
3. Run archetype commands and run tomcat
Re: issues getting 1.7 data to 1.8
http://localhost:8080/openvpms/ should redirect to the login page but if it doesn't, try http://localhost:8080/openvpms/login
Re: issues getting 1.7 data to 1.8
My question is why are you using maven and the source to run? Have you made any modifications?
If so what are they?
If not why not just use the beta distribution to get up and running.
I dont typically run my development at all using migrated data...I run development using the controlled sample source to ensure my build is consistent. Once I am happy I generate a release and migrate using that.
Re: issues getting 1.7 data to 1.8
the code is not changed at this point, i have not got it running yet. Its a preference thing, i prefer working with a copy of live data, i know what to expect as i know this data. Also helps me with debugging live data issues in the future.
if i cant get my data running, i will use the default data sample, im just giving it a proper go before moving on. thats all :)
Re: issues getting 1.7 data to 1.8
If working with live data, you should ensure that some of the automated features like ESCI are disabled.
See http://www.openvpms.org/implementors-handbook/anonymising-database for relevant SQL.
Re: issues getting 1.7 data to 1.8
The only reason I do as I do...is that you need to determine what is a workspace issue and what is a data issue.
I have had a number of artifact issues in my workspace overtime where an old artifact in maven was not being removed and replaced with updated builds. Because I was sure my data was the same at all times as it was generated as part of the development using the Load Data goal I could reliably work through the issue and debug it.
I think you can safely say assuming that you pass all tests, that the issue is a data issue.
If you are concerned I would attempt to get the dataset working on a proper installation as opposed to a development environment. You can then debug the live data issues seperately then port that working live data set back to the dev env.
Re: issues getting 1.7 data to 1.8
Ok no worries.
Actually what is the best way to debug issues on live data now that you mention it without a dev environment?
Re: issues getting 1.7 data to 1.8
only just got to try it, but yes you are right the link is wrong, i wasnt being redirected back to http://localhost:8080/openvpms/login
now that im on the right address the data is all good, thanks for all the help everyone much appreciated.