Persistence Context shares between non-transactional and REQUIRES_NEW transactions unexpectedly

[sedmehdi]

In the following example, when the POST /foo/test1 endpoint is called, the entity will be saved to the database. However, calling POST /foo/test2 will not trigger any updates.

`
@RestController
@RequestMapping("/foo")
public class FooController {

	@Autowired
	BarService barService;

	@PersistenceContext
	EntityManager entityManager;

	@PostMapping("/test1")
	public void post1() {
		System.out.println("\n".repeat(10));
		FileEntity fileEntity = entityManager.find(FileEntity.class, 2L);
		fileEntity.setDescription(fileEntity.getDescription() + "-1");
		barService.bar();
	}

	@Transactional(Transactional.TxType.SUPPORTS)
	@PostMapping("/test2")
	public void post2() {
		System.out.println("\n".repeat(10));
		FileEntity fileEntity = entityManager.find(FileEntity.class, 2L);
		fileEntity.setDescription(fileEntity.getDescription() + "-1");
		barService.bar();
	}
}


@Service
public class BarService {
	@Transactional(Transactional.TxType.REQUIRES_NEW)
	public void bar() {
		System.out.println("log");
	}
}

`
I expect that no updates occur in either call

[mp911de]

Without further context, it's impossible to say what is triggered by the surrounding code. Also, Spring's @Transactional(…) must be used @Transactional(propagation = Propagation.…) indicating @Transactional(Transactional.TxType.REQUIRES_NEW) is a non-Spring Framework annotation.

Generally speaking, since none of the code above calls EntityManager.persist(…), something implicit is going on. I can well imagine that any surrounding component isn't starting a transaction when encountering PROPAGATION_SUPPORTS as that is the default behavior and so you see the effects of this propagation mode. In any case, this is merely a guess.

This issue tracker isn't a general Q&A forum for JPA transactional behavior. Please consult the JPA spec or Stackoverflow for further information. This issue tracker is to track Spring Data bugs and enhancement proposals.