Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The auto-configured reactiveNeo4jTransactionManager may cause a failure due to multiple TransactionManager beans #40953

Closed
wilkinsona opened this issue May 30, 2024 · 1 comment
Closed

The auto-configured reactiveNeo4jTransactionManager may cause a failure due to multiple TransactionManager beans #40953

wilkinsona opened this issue May 30, 2024 · 1 comment
Labels
status: forward-port An issue tracking the forward-port of a change made in an earlier branch type: regression A regression from a previous release
Milestone
3.3.1

Comments

@wilkinsona
Copy link
Member

Forward port of issue #40895 to 3.3.x.
@wilkinsona wilkinsona added status: forward-port An issue tracking the forward-port of a change made in an earlier branch type: regression A regression from a previous release labels May 30, 2024
@wilkinsona wilkinsona added this to the 3.3.1 milestone May 30, 2024
@mhalbritter mhalbritter changed the title In 3.2.3+ , the auto-configured reactiveNeo4jTransactionManager may caused a failure due to multiple TransactionManager beans The auto-configured reactiveNeo4jTransactionManager may cause a failure due to multiple TransactionManager beans Jun 20, 2024
@Netyyyy Netyyyy mentioned this issue Jun 22, 2024
Merged
@wilkinsona wilkinsona mentioned this issue Jun 30, 2024
Closed
@yangyaofei
Copy link

please see this issue spring-projects/spring-data-neo4j#2931

the transactionManager in neo4j Neo4jDataAutoConfiguration.java will not create when using spring-data-jpa because in JpaBaseConfiguration the transactionManager for jpa will be created and then pop out error in neo4j show in issue below.

If I create a transactionManager for neo4j, the jpa will throw error when using like saveAndFlush.

I think (may not right or elegant) maybe disable Neo4jTransactionManager bean and make it in Neo4jTemplate bean is a way, or warp Neo4jTransactionManager into some container to prevent it extend from TransactionManager.

@yangyaofei yangyaofei mentioned this issue Aug 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: forward-port An issue tracking the forward-port of a change made in an earlier branch type: regression A regression from a previous release
Projects
None yet
Milestone
3.3.1
Development

No branches or pull requests
2 participants
@wilkinsona @yangyaofei