SUPPORT / SAMPLES & SAS NOTES
Problem Note 68464: Elasticsearch indexing in SAS® Visual Investigator fails with an IllegalTransactionStateException error
 |  |  |  |  |
While indexing an entity, the Jobs tab reports that the indexing job for the entity has failed. There are a number of indications that help you determine whether you have this issue.
When you select the job on the Jobs tab, you can see a list of records that have been read. But the number of records written is 0.
In the svi-indexer log, you see an exception that is similar to the following:
2020-09-23 16:25:18.834 INFO 95968 --- [ctTypeExecutor2] o.s.b.c.l.support.SimpleJobLauncher : service@@__default__ [ee46199ee49ca3f1] Job: [FlowJob: [name=objectTypeChildJob]] completed with the following parameters: [{reindexJobType=REINDEX_ONE, jobId=c895e2cf-12bb-4a51-a193-81b5e80a0f29, reindexAllSystemLinks=false, operation=LOAD, reindexAllSystemTransactions=false, tenant=__default__, objectTypeJobType=METAMODEL, objectTypeName=VI___VI_ADM, taskId=0e3c31de-9fe8-4a13-9c8d-7fe8979cbb07, metadataType=LINK}] and the following status: [FAILED]
2020-09-23 16:25:18.834 ERROR 95968 --- [ctTypeExecutor2] o.s.batch.core.step.AbstractStep : service@@__default__ [ee46199ee49ca3f1] Encountered an error executing step objectTypeSlaveStep in job indexerJob
org.springframework.batch.core.UnexpectedJobExecutionException: Step failure: the delegate Job failed in JobStep.
at org.springframework.batch.core.step.job.JobStep.doExecute(JobStep.java:125)
...
2020-09-23 16:25:18.834 ERROR 95968 --- [ctTypeExecutor2] o.s.batch.core.step.AbstractStep : service@@__default__ [ee46199ee49ca3f1] Encountered an error executing step objectTypeSlaveStep in job indexerJob
org.springframework.batch.core.UnexpectedJobExecutionException: Step failure: the delegate Job failed in JobStep.
at org.springframework.batch.core.step.job.JobStep.doExecute(JobStep.java:125)
...
In the datahub log, you might see an exception like the following:
com.sas.fcs.datahub.DataHubException: The cache could not be updated.
at com.sas.fcs.datahub.cache.TenantAwareCache.getValuesAndCommit(TenantAwareCache.java:308)
...
Caused by: org.springframework.transaction.IllegalTransactionStateException: Pre-bound JDBC Connection found! JpaTransactionManager does not support running within DataSourceTransactionManager if told to manage the DataSource itself. It is recommended to use a single JpaTransactionManager for all transactions on a single DataSource, no matter whether JPA or JDBC access.
at com.sas.fcs.datahub.cache.TenantAwareCache.getValuesAndCommit(TenantAwareCache.java:308)
...
Caused by: org.springframework.transaction.IllegalTransactionStateException: Pre-bound JDBC Connection found! JpaTransactionManager does not support running within DataSourceTransactionManager if told to manage the DataSource itself. It is recommended to use a single JpaTransactionManager for all transactions on a single DataSource, no matter whether JPA or JDBC access.
In the datahub log, there also might be a number of messages similar to the following that fill up the log:
2020-11-25 09:19:52.107 ERROR 33871 --- [itionExecutor37] c.s.fcs.datahub.cache.TenantAwareCache : service [8ad4efb25c4e5d28] Failed to reload cache
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Investigator | Linux for x64 | 10.7 | Viya | ||