Sqlgrammarexception error performing isolated work

JBossDeveloper

We are in process of upgrading to 7.1 from 4.2.3a. During this excersize I did few changes to my hibernate.cfg.xml. Attached hibernate.cfg.xml

As well as here is standalone.xml entries:

And I am getting following error:

12:00:26,470 WARN [org.hibernate.util.JDBCExceptionReporter] (http—127.0.0.1-8080-2) SQL Error: 0, SQLState: null

12:00:26,471 ERROR [org.hibernate.util.JDBCExceptionReporter] (http—127.0.0.1-8080-2) You cannot commit during a managed transaction!

12:00:26,472 ERROR [yyy_common.yyyUserActivityException] (http—127.0.0.1-8080-2) [yyyUserActivity][yyyUserActivityException][myBean][createConnection] Failed to create connection: org.hibernate.exception.GenericJDBCException: error performing isolated work

at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.transaction.Isolater$JdbcDelegate.delegateWork(Isolater.java:207) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:43) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:51) [hibernate3.jar:3.2.6.ga]

at org.hibernate.id.TableGenerator.generate(TableGenerator.java:94) [hibernate3.jar:3.2.6.ga]

Attached full log. Any pointer would be really appreciated.

Источник

issue when creating new person #14

for example when the birthday is 11/11/88 very strange

org.springframework.dao.InvalidDataAccessResourceUsageException: error performing isolated work; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: error performing isolated work at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:240)

[spring-orm-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:223)

[spring-orm-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.translateExceptionIfPossible(AbstractEntityManagerFactoryBean.java:527)

[spring-orm-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.dao.support.ChainedPersistenceExceptionTranslator.translateExceptionIfPossible(ChainedPersistenceExceptionTranslator.java:61)

[spring-tx-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:242)

[spring-tx-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:153)

[spring-tx-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor$CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:135)

[spring-data-jpa-2.0.10.RELEASE.jar:2.0.10.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.data.repository.core.support.SurroundingTransactionDetectorMethodInterceptor.invoke(SurroundingTransactionDetectorMethodInterceptor.java:61)

[spring-data-commons-2.0.10.RELEASE.jar:2.0.10.RELEASE] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)

[spring-aop-5.0.9.RELEASE.jar:5.0.9.RELEASE] at com.sun.proxy.$Proxy112.save(Unknown Source)

[na:na] at crud.vaadin.PersonForm.lambda$new$da1cf436$1(PersonForm.java:41)

The text was updated successfully, but these errors were encountered:

Источник

Error performing isolated work

Hibernate version: 3.2 RC3

Full stack trace of any exception that occurs:
Caused by: java.rmi.RemoteException: ; nested exception is:
org.hibernate.HibernateException: error performing isolated work
at org.hibernate.engine.transaction.Isolater$JtaDelegate.delegateWork(Isolater.java:142)
at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:40)
at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:51)
at com.generali.ruby.utils.persistance.RubyPIDGenerator.generate(RubyPIDGenerator.java:146)
at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:98)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186)
at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175)
at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27)
at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70)
at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:535)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:523)
at org.hibernate.impl.SessionImpl.save(SessionImpl.java:519)
at com.generali.ruby.bo.BusinessObject.save(BusinessObject.java:67)
at com.generali.ruby.workflow.BusinessProcessManager.createBusinessProcess(BusinessProcessManager.java:202)
at com.generali.ruby.services.workflow.WorkflowFacadeBean.createBusinessProcess(WorkflowFacadeBean.java:128)
at com.generali.ruby.services.workflow.EJSRemoteStatelessWorkflowFacade_e9815e81.createBusinessProcess(EJSRemoteStatelessWorkflowFacade_e9815e81.java:175)
at com.generali.ruby.services.workflow._WorkflowFacade_Stub.createBusinessProcess(_WorkflowFacade_Stub.java:309)
. 39 more
Caused by: org.hibernate.HibernateException: error performing isolated work
. 57 more

Name and version of the database you are using: DB2 V 7.2.005

[b] App server : WAS 6.0.2.15[b/]

We have implemented our own id generator. The doWorkInIsolation() method throws up the above error when it tries to suspend the JTA transaction and open a JDBC connection.

JBossDeveloper

We are in process of upgrading to 7.1 from 4.2.3a. During this excersize I did few changes to my hibernate.cfg.xml. Attached hibernate.cfg.xml

As well as here is standalone.xml entries:

And I am getting following error:

12:00:26,470 WARN [org.hibernate.util.JDBCExceptionReporter] (http—127.0.0.1-8080-2) SQL Error: 0, SQLState: null

12:00:26,471 ERROR [org.hibernate.util.JDBCExceptionReporter] (http—127.0.0.1-8080-2) You cannot commit during a managed transaction!

12:00:26,472 ERROR [yyy_common.yyyUserActivityException] (http—127.0.0.1-8080-2) [yyyUserActivity][yyyUserActivityException][myBean][createConnection] Failed to create connection: org.hibernate.exception.GenericJDBCException: error performing isolated work

at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) [hibernate3.jar:3.2.6.ga]

at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.transaction.Isolater$JdbcDelegate.delegateWork(Isolater.java:207) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:43) [hibernate3.jar:3.2.6.ga]

at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:51) [hibernate3.jar:3.2.6.ga]

at org.hibernate.id.TableGenerator.generate(TableGenerator.java:94) [hibernate3.jar:3.2.6.ga]

Attached full log. Any pointer would be really appreciated.

Источник

org.hibernate.exception.SQLGrammarException when saving object with Many-to-Many and many-to-one relationships #2137

Comments

pacu commented Oct 12, 2015

I have this simple model.

Course 1—> * Level * ——- * Excercise

I tried to use both jhipster-uml and yeoman generators getting the same results
I can create a Course without problems.
I can create an Exercise as well
But I can’t create a Level for some reason.
This is the error shown in the browser

this is part of the log and trace that I got

This is how I created the entities using yeoman (I swear I read the docs and googled a lot before posting this)
yo jhipster:entity course

yo jhipster:entity exercise

yo jhipster:entity level

The text was updated successfully, but these errors were encountered:

ErickSanVal commented Oct 12, 2015

Well, somebody correct me if I’m wrong but it seems that the REST request is missing the ‘course_id’ parameter. Does it have to do with that?

pacu commented Oct 12, 2015

could it be because «order» is a reserved keyword on postgres?

ErickSanVal commented Oct 12, 2015

Oh, yeah, have you tried changing the name of the field?

pacu commented Oct 13, 2015

I’m having other kind of problems. I’ve created a new project with the same
models but the NavBar is not working and localhost:8080/#/courses is
redirecting me to the home page.

On Mon, Oct 12, 2015 at 8:18 PM, Erick notifications@github.com wrote:

Oh, yeah, have you tried changing the name of the field?

—
Reply to this email directly or view it on GitHub
#2137 (comment)
.

IEEE Member# 91130670
Home:+5411 5032 3615
Mobile: +5411 6096 2879

jdubois commented Oct 13, 2015

@pacu if you have another problem, please open another ticket.

Yes I’m 99% sure this issue is because your field is called «order»:

• Your ticket is really good (which is unusual!), but you missed the most important thing, the SQL request! As you have an SQL grammar exception, that was the most important part.
• We have lists of reserved keywords for many things, but not for Postgresql, as I couldn’t find a good list (the official list has lots and lots of reserved keywords, which you can in fact use without any issue, and that’s annoying because a lot of «good» names are reserved)

-> Maybe we should do our own reserved keywords list? Wouldn’t be perfect, but better than nothing

I’m closing this as you seem to moved on to another issue, and as I’m pretty sure this is this reserved keyword issue: if you still have the issue, please add a comment and I’ll reopen it.

Источник

Common Hibernate Exceptions Every Developer Must Know

Get access to all my video courses, 2 monthly Q&A calls, monthly coding challenges, a community of like-minded developers, and regular expert sessions.

Every framework has a set of exceptions that indicate common error scenarios. Understanding them will help you turn a task that could drag along for days into a quickly-implemented feature. When working with Hibernate, they tell you about issues with your database queries, mapping mistakes, and problems during write operations.

In this article, I want to show you the most common exceptions and explain how you can avoid or fix them.

Query-Related Exceptions

These are the most common Hibernate exceptions. Sometimes, they are caused by a simple typo in your statement or because you called the wrong Query interface method. However, they can also indicate potential performance issues or data inconsistencies.

NonUniqueResultException

All JPA implementations throw the NonUniqueResultException if you call the getSingleResult method on a Query interface and the executed query returns more than one record.

The NonUniqueResultException most often occurs because:

• You intentionally wrote a query that returns multiple records and tried executing it by calling the getSingleResult() instead of the getResultList() method. To be honest, that happens to me quite regularly. Luckily, it’s very quick and easy to fix by calling the getResultList() method.
• You wanted to create a query that returns only one record, but the WHERE clause isn’t as restrictive as you thought. In that case, please check my Guide to JPQL. It tells you everything you need to know to improve your query.
• You wrote a query that was supposed to return only one record and you stumbled upon inconsistent data. If that happens, then it’s hopefully just some artificially created test data. But, in any case, you should double-check your business logic and add a unique constraint to your table model.

QuerySyntaxException

If Hibernate throws a QuerySyntaxException, you have made a mistake in your JPQL query. In most cases, the mistake will be a simple typo in one of JPQL’s reserved keywords.

As you can see in the following log message, Hibernate tells you which part of the query it didn’t understand. In this example, I misspelled the word LEFT in my LEFT JOIN clause.

SQLGrammarException

An SqlGrammarException is very similar to a QuerySyntaxException. It indicates a mistake in a native SQL statement.

Unfortunately, Hibernate’s exception doesn’t provide a lot of information about the actual error. It only tells you that it was unable to extract the ResultSet. But, if you take a look at the end of the stack trace, you should find the exception thrown by your JDBC driver. It usually tells you why the query failed.

LazyInitializationException

The LazyInitializationException might not look like a query-related exception because it happens much later. Hibernate throws it if you try to initialize a lazily fetched association without an active Hibernate Session. This usually happens in your UI layer after your backend committed the transaction and closed the Session. Even though it might not look like it, it’s caused by a query that didn’t fetch the required association.

As you can see in the message below, Hibernate tells you which association it wasn’t able to initialize.

You can fix this exception in multiple ways. The easiest and most commonly used solution is a JOIN FETCH clause. You can use it in your JPQL query to tell Hibernate to initialize the referenced association.

MultipleBagFetchException

If you model your to-many associations as java.util.Lists and try to initialize a number of them using a JOIN FETCH clause, Hibernate will throw a MultipleBagFetchException.

As I explained in more detail in a previous article, you can fix this exception in two ways:

1. You can change the attribute type to a java.util.Set.

2. You can use multiple queries that use only one JOIN FETCH clause each. This approach works because Hibernate ensures that a Session contains only one entity object for each database record. If you select the same one with different fetching behavior, Hibernate will merge them in memory.

Mapping-Related Exceptions

I will keep this section short because mapping-related exceptions are rare. That’s mostly because mapping is defined once and used during the entire project.

MappingException: The Increment Size of the [author_seqence] Sequence Is Set to [50] in the Entity Mapping While the Associated Database Sequence Increment Size Is [1]

If you use a database sequence to generate your primary key values and define a @SequenceGenerator, you might get the following exception:

Hibernate throws this exception because it provides an optimization based on the default allocationSize of the @SequenceGenerator. Based on that default setting, the database sequence should get incremented by 50 every time you request a new value. Hibernate then uses the value from the sequence and increments it 49 times internally before requesting another value. This drastically reduces the number of executed JDBC statements.

During the deployment of your persistence layer, Hibernate checks if the referenced database sequence gets incremented by the defined allocationSize. If that’s not the case, it throws a MappingException.

I recommend fixing this exception by increasing the step size on your database sequence. It enables you to use Hibernate’s optimization to improve the performance of your insert operations. If you cannot change the database sequence, you need to set the allocationSize of the @SequenceGenerator to one.

Update-Related Exceptions

Hibernate throws this kind of exception to inform you about problems during write operations. The two most common ones are the OptimisticLockException and the PersistentObjectException. While the first one is expected to occur at runtime, the second one is always an implementation error.

OptimisticLockException

JPA and Hibernate provide two build-in mechanisms to manage concurrent updates. One of them is called optimistic locking. It causes an OptimisticLockException whenever two or more transactions try to update the same database record at the same time. That lets all except the first transaction fail and prevents the concurrent modification of the record.

Optimistic and pessimistic locking are easy and complex at the same time, but that’s a whole other topic. If you want to learn more about it, please join my Hibernate Performance Tuning Online Training.

Technically, there are a few options for fixing an OptimisticLockException. But realistically, all of them require you to merge the operations performed in the parallel transactions. The best and most reliable way to do that is to show an error message to the user when the exception occurs. The user can then find the differences between both changes, resolve errors or inconsistencies, and perform another update.

PersistentObjectException: Detached Entity Passed to Persist

There are two main scenarios in which Hibernate throws this exception.

The first happens when you configure a primary key generation strategy for an entity and set the primary key value programmatically before persisting a new entity. You can easily fix that by removing the code that sets the primary key value. If you’re using field-based access, you should also remove the setter method for the primary key attribute. This prevents you from accidentally setting that attribute in the future.

The second scenario happens when you call the persist method of the EntityManager with a detached entity.

This is usually the case because you got an entity object from a client application and tried to persist it. In this case, you can fix the exception by calling the merge method on the EntityManager.

Conclusion

If you’re using a framework to implement your application, you should be familiar with its most common exceptions. Hibernate is a complex and powerful framework. So, it’s no surprise that you need to be familiar with a bunch of exceptions.

Most of them are query-related because querying data is highly flexible and the most used part of the framework. The good news is that all of these exceptions include a good description of the error so that you can easily fix it.

Источник

Caused by org hibernate exception sqlgrammarexception error performing isolated work

Опытный

Профиль
Группа: Участник
Сообщений: 253
Регистрация: 27.3.2006

Репутация: нет
Всего: нет

ochnev	Дата 16.6.2008, 16:34 (ссылка) | (нет голосов) Загрузка .

На 2-й строке получаю SQLGrammarException:

Таблица пустая, но не из-за этого же оно падает. Мэппинг проверил — вроде всё нормально.

Всё раньше работало, вдруг сломалось на ровном месте. Я базу переделывал, но нужная таблица на месте.
Что происходит? Как найти реальную причину SQLGrammarException при таком stack trace, в котором нет ни малейших подробностей о проблеме?

AntonSaburov	Дата 16.6.2008, 17:22 (ссылка) | (нет голосов) Загрузка .
Штурман Профиль Группа: Модератор Сообщений: 5658 Регистрация: 2.7.2002 Где: Санкт-Петербург Репутация: 8 Всего: 118 Добавь в hibernate.cfg.xml Тогда можно будет посмотреть реальный SQL — ну и увидишь. Возможно

necromancer	Дата 16.6.2008, 17:25 (ссылка) | (нет голосов) Загрузка .
Опытный Профиль Группа: Участник Сообщений: 317 Регистрация: 26.7.2006 Где: Москва Репутация: 6 Всего: 7

Zlatogorov	Дата 16.6.2008, 17:40 (ссылка) | (нет голосов) Загрузка .
Шустрый Профиль Группа: Участник Сообщений: 117 Регистрация: 18.12.2007 Где: BW,Stuttgart Репутация: нет Всего: 1 , тип должен стоять java.lang.Double , ну и т.д. А просто double не существует. Ну и timestamp должен быть java.util.Date. Это сообщение отредактировал(а) Zlatogorov — 16.6.2008, 17:44

tux

Дата 16.6.2008, 20:29 (ссылка) | (нет голосов) Загрузка .

Летатель Профиль Группа: Участник Клуба Сообщений: 1853 Регистрация: 10.2.2005 Где: msk.ru Репутация: 74 Всего: 132 Цитата(ochnev @ 16.6.2008, 16:34 ) Всё раньше работало, вдруг сломалось на ровном месте. Точно работало? Вот, например, в маппинге колонка называется bonus_or_fine, а в таблице bonusOrFine. Цитата(Zlatogorov @ 16.6.2008, 17:40 ) К примеру здесь , тип должен стоять java.lang.Double , ну и т.д. А просто double не существует.

Опытный

Профиль
Группа: Участник
Сообщений: 253
Регистрация: 27.3.2006

Репутация: нет
Всего: нет

Точно.
Каюсь.
Что-то переделывал и в попыхах copy/paste не там сделал.

ochnev	Дата 16.6.2008, 22:01 (ссылка) | (нет голосов) Загрузка .

вопрос:

Сегодня, когда проводится тест проекта Spring Boot, операция сообщается, как показано ниже:

org.springframework.dao.InvalidDataAccessResourceUsageException: error performing isolated work; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: error performing isolated work
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.convertHibernateAccessException(HibernateJpaDialect.java:281)
at org.springframework.orm.jpa.vendor.HibernateJpaDialect.translateExceptionIfPossible(HibernateJpaDialect.java:255)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.translateExceptionIfPossible(AbstractEntityManagerFactoryBean.java:528)
at org.springframework.dao.support.ChainedPersistenceExceptionTranslator.translateExceptionIfPossible(ChainedPersistenceExceptionTranslator.java:61)
at org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:242)
at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.invoke(PersistenceExceptionTranslationInterceptor.java:153)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
at org.springframework.data.jpa.repository.support.CrudMethodMetadataPostProcessor C r u d M e t h o d M e t a d a t a P o p u l a t i n g M e t h o d I n t e r c e p t o r . i n v o k e ( C r u d M e t h o d M e t a d a t a P o s t P r o c e s s o r . j a v a : 178 ) a t o r g . s p r i n g f r a m e w o r k . a o p . f r a m e w o r k . R e f l e c t i v e M e t h o d I n v o c a t i o n . p r o c e e d ( R e f l e c t i v e M e t h o d I n v o c a t i o n . j a v a : 186 ) a t o r g . s p r i n g f r a m e w o r k . a o p . i n t e r c e p t o r . E x p o s e I n v o c a t i o n I n t e r c e p t o r . i n v o k e ( E x p o s e I n v o c a t i o n I n t e r c e p t o r . j a v a : 93 ) a t o r g . s p r i n g f r a m e w o r k . a o p . f r a m e w o r k . R e f l e c t i v e M e t h o d I n v o c a t i o n . p r o c e e d ( R e f l e c t i v e M e t h o d I n v o c a t i o n . j a v a : 186 ) a t o r g . s p r i n g f r a m e w o r k . a o p . f r a m e w o r k . J d k D y n a m i c A o p P r o x y . i n v o k e ( J d k D y n a m i c A o p P r o x y . j a v a : 212 ) a t c o m . s u n . p r o x y . CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:178) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:93) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212) at com.sun.proxy. CrudMethodMetadataPopulatingMethodInterceptor.invoke(CrudMethodMetadataPostProcessor.java:178)atorg.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)atorg.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:93)atorg.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)atorg.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)atcom.sun.proxy.Proxy105.save(Unknown Source)

Причины и решения

После проверки соответствующих вопросов в Интернете я узнал, что это было причиной идентификатора идентификатора идентификатора.
Правильный подход должен быть добавлен в идентификатор:

    @Id
    @GeneratedValue(strategy= GenerationType.IDENTITY)

Как показано ниже: