Describe the bug
In the opal log I see man warnings like this:
WARN org.obiba.opal.search.IndexSynchronizationManager - Error while checking indexable
org.hibernate.HibernateException: Unable to locate current JTA transaction
at org.hibernate.context.internal.JTASessionContext.currentSession(JTASessionContext.java:92) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
at org.hibernate.internal.SessionFactoryImpl.getCurrentSession(SessionFactoryImpl.java:1014) ~[hibernate-core-4.3.11.Final.jar:4.3.11.Final]
at org.obiba.magma.datasource.hibernate.HibernateValueTable.getValueTableState(HibernateValueTable.java:258) ~[magma-datasource-hibernate-2.0.1.jar:2.0.1]
at org.obiba.magma.datasource.hibernate.HibernateValueTable.getTimestamps(HibernateValueTable.java:167) ~[magma-datasource-hibernate-2.0.1.jar:2.0.1]
at org.obiba.magma.support.AbstractValueTableWrapper.getTimestamps(AbstractValueTableWrapper.java:123) ~[magma-api-2.0.1.jar:2.0.1]
at org.obiba.magma.support.Timestampeds$1.compare(Timestampeds.java:28) ~[magma-api-2.0.1.jar:2.0.1]
at org.obiba.magma.support.Timestampeds$1.compare(Timestampeds.java:20) ~[magma-api-2.0.1.jar:2.0.1]
at org.obiba.es.opal.support.ESIndexManager$ESValueTableIndex.isUpToDate(ESIndexManager.java:335) ~[opal-search-es-1.0.0.jar:na]
at org.obiba.opal.search.IndexSynchronizationManager$SyncProducer.run(IndexSynchronizationManager.java:129) ~[opal-search-2.15.1.jar:na]
at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120) [shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108) [shiro-core-1.4.0.jar:1.4.0]
at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:395) [shiro-core-1.4.0.jar:1.4.0]
at org.obiba.opal.search.IndexSynchronizationManager.synchronizeIndices(IndexSynchronizationManager.java:81) [opal-search-2.15.1.jar:na]
at sun.reflect.GeneratedMethodAccessor112.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_222]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_222]
at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65) [spring-context-4.3.19.RELEASE.jar:4.3.19.RELEASE]
at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.3.19.RELEASE.jar:4.3.19.RELEASE]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_222]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_222]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_222]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_222]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_222]
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug In the opal log I see man warnings like this:
But the system looks like working normal.
OS: CentOS 7.6 opal-server-2.15.1-1.noarch