persistenceService.run(upsert) caused Connection must not be in auto-commit mode

[former_member554726]

Hi Cap team,

Could you analyze when we execute an db statement using cap service in java as below:

@Autowired
PersistenceService persistenceService
CqnUpsert upsert = Upsert.into(GTTMetadataStatus_.class).entries(statusList);
persistenceService.run(upsert);

And when run above, it caused an error: Connection must not be in auto-commit mode

Do you know the reason, and how I can resolve this issue?

[former_member554726]

marcbecker,

We did not use PlatformTransactionManager. We just use persistenceService.run(upsert);

And in application.yaml:

spring:
  profiles: cloud
cds:
  dataSource:
    serviceName: ${TARGET_CONTAINER}
    binding: ${TARGET_CONTAINER}

We use that. Do you know the reason?

[yaowl]

May I ask if you have solved this problem? I am encountering the same issue.

[marcbecker]

This usually happens in case CAP Java is not configured with the correct PlatformTransactionManager from Spring. Do you explicitly create (multiple) instances of PlatformTransactionManager in your application? If yes pleae make sure that the primary PlatformTransactionManager manages the primary DataSource, as those are the two instances that are used by CAP Java.

[former_member554726]

Do you mean this in spring config file?

cds:
  dataSource:
    serviceName: ${TARGET_CONTAINER}
    binding: ${TARGET_CONTAINER}

Except this I have not seen any PlatformTransactionManager. Do you have an example for this?

[marcbecker]

No. Do you have usages of these classes in your project?

• https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/Pla...
  
• https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/jdbc/datasource...

Do you have multiple datasource bindings? For example multiple HANA bindings? Or HANA bindings and service-manager bindings?