[
https://issues.jboss.org/browse/WFLY-6127?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on WFLY-6127:
------------------------------------
Please create a new [WFLY
jira|https://issues.jboss.org/browse/WFLY] to discuss the
proposed (extension) patch [
https://github.com/argustelecom/wildfly/tree/WFLY-6127]. I
have questions to ask about the change and whether you could instead use an
application-managed entity manager instead (which is similar to extended persistence
context except the app controls it. Please include the above two comments as well.
Throw IllegalStateException if JTA tx has an unsynchronized
persistence context and the target is synchronized persistence context
----------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-6127
URL:
https://issues.jboss.org/browse/WFLY-6127
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 9.0.2.Final
Reporter: Mazen Mahmoud
Assignee: Scott Marlow
Priority: Blocker
Fix For: 10.1.0.CR1, 10.1.0.Final
Attachments: server-log.txt
SPEC: If a component is called and the JTA transaction is propagated into that
component:
If there is a persistence context of type SynchronizationType.UNSYNCHRONIZED
associated with the JTA transaction and the target component specifies a persistence
context of type SynchronizationType.SYNCHRONIZED, the IllegalStateException is thrown by
the container
We have a stateful session bean (SFB1) / PC: TRANSACTION/UNSYNCHRONIZED)
stateful session bean (SFB2) / PC: TRANSACTION/SYNCHRONIZED)
SFB1 method M1 (REQUIRED) calls SFB2 Method 2 (REQUIRED):
PC is propagated from SFB1 to SFB2 without any exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)