[
https://issues.redhat.com/browse/WFLY-13234?page=com.atlassian.jira.plugi...
]
Scott Marlow commented on WFLY-13234:
-------------------------------------
[~daniel.wehrle] the change was made for [WFLY-10638]
{quote}
Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from
NON_XA to NONE (default) and what are the implications?
{quote}
The NON_XA was being ignored, except that a warning would be logged. So, there should be
zero impact from this change.
{quote}
Can this lead to performance problems?
{quote}
There shouldn't be any, the Infinispan internal code was updated, to not need/support
the NON_XA mode anymore.
WF17 vs. WF18: org.infinispan.hibernate-cache
---------------------------------------------
Key: WFLY-13234
URL:
https://issues.redhat.com/browse/WFLY-13234
Project: WildFly
Issue Type: Task
Components: JPA / Hibernate
Affects Versions: 18.0.1.Final
Reporter: Daniel Wehrle
Assignee: Scott Marlow
Priority: Major
Hi.
Why has the entity cache transaction in org.infinispan.hibernate-cache been changed from
NON_XA to NONE (default) and what are the implications? Can this lead to performance
problems?
WF17
{code}
<cache-container name="hibernate"
module="org.infinispan.hibernate-cache">
<local-cache name="entity">
<transaction mode="NON_XA"/>
<object-memory size="10000"/>
<expiration max-idle="100000"/>
</local-cache>
{code}
WF18
{code}
<cache-container name="hibernate"
module="org.infinispan.hibernate-cache">
<local-cache name="entity">
<object-memory size="10000"/>
<expiration max-idle="100000"/>
</local-cache>
{code}
Best regards,
Daniel
--
This message was sent by Atlassian Jira
(v7.13.8#713008)