I am trying to import this packaged metadata into platform 1.11.5. Initially it appears as though everything is working fine until it stops with the exception shown below.
org.openmrs.module.metadatasharing.task.TaskException: Task failed
at org.openmrs.module.metadatasharing.task.Task.log(Task.java:125)
at org.openmrs.module.metadatasharing.task.TaskEngine$RunnableTask.run(TaskEngine.java:127)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.openmrs.module.metadatasharing.task.TaskException: Task failed
… 4 more
Caused by: org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:718)
at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:475)
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:270)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy3483.executeTask(Unknown Source)
at org.openmrs.module.metadatasharing.task.TaskEngine$RunnableTask.run(TaskEngine.java:124)
… 3 more
English (United States) | English (United Kingdom) Last Build: 2016-03-30 08:36 Version: 1.11.5 Build 47f108
Looking into the tomcat logs shows exactly the same thing.
There must be an error somewhere along the import and it isn’t logged properly. Due to that error the transaction has been marked as failed and rolled back.
You will have to run the import with a debugger attached and set some breakpoints in the execute method of the ImportPackageTask class to find out what exception caused rolling back the transaction.
@raff I figured I didn’t need to run the debugger after all because I was trying to import the package exported from 1.9.3 to 1.11.5 which may be the problem, but anyway I didn’t want to find out. Instead I with the help of @wyclif I got hold of the metadata exported from 1.11.5. Unfortunately I am still running into errors as shown in this stack trace
To reproduce this error follow the steps below:
Spawn a 1.11.5 instance of OpenMRS (I am using legacy UI although I doubt if it matters!)
Go to Administration, click “Import Metadata” under “Metadata sharing module” section. You should see a screen as shown below. Download and use this metadata package
At this point when you click next you will see stack trace mentioned above.
I am still investigating the reason for this but it appears the query generator is having issues generating the right query.
Update:
I have no idea what is going on with my server instance I used for this exercise because trying to reproduce the same problem on a standalone reference application 2.3.1 does not work, that is the package is imported successfully!
The stacktrace reveals an actual bug in openmrs-core as “AND” is not escaped in the query and it is a reserved keyword. It needs to be fixed as described here http://stackoverflow.com/a/10757968
But why don’t I experience the same behavior in standalone?!! This is puzzling!
Update: The Lucene error disappeared after changing the offending AND to lower case. However I am still not able to import concepts because the error for which this thread has been created (see first post) has re-surfaced. Nevertheless I realized we don’t actually need to import the package for us to be able to utilize the order entry API which was all along the goal of doing this.
Thanks for reporting back. I think the bug will only reveal itself, if you do not have “AND” in concept stop words, thus it worked on your standalone. Adding “AND” to concept stop words list from the management page should fix it as well.
Hi,@raff, I added both AND and OR as stop words on my Ref App 2.4 standalone today but it still runs into the same issue. A workaround is to replace AND to lower case and as well as to replace OR to lower case or on the metadata.xml file.
