atg.repository.search.indexing.IndexingException: Session should not be committed, most likely because too many errors (1) occurred, canceling

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by atg_tech, 1 year ago
Session should not be committed, most likely because too many errors (1) occurred, canceling
via Oracle Community by 878033, 1 year ago
Session should not be committed, most likely because too many errors (1) occurred, canceling
via Oracle Community by 979230, 1 year ago
Session should not be committed, most likely because too many errors (1) occurred, canceling
via Oracle Community by Rohan Dekate, 1 year ago
Session should not be committed, most likely because too many errors (1) occurred, canceling
via Oracle Community by 3148285, 1 year ago
Session should not be committed, most likely because too many errors (1) occurred, canceling
atg.repository.search.indexing.IndexingException: Session should not be committed, most likely because too many errors (1) occurred, canceling
at atg.repository.search.indexing.LoaderImpl.processItem(LoaderImpl.java:879)
at atg.repository.search.indexing.LoaderImpl.processItem(LoaderImpl.java:725)
at atg.repository.search.indexing.threading.ProcessItemJob.invoke(ProcessItemJob.java:145)
at atg.common.util.ThreadDispatcherThread.run(ThreadDispatcherThread.java:178)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago

Know the solutions? Share your knowledge to help other developers to debug faster.