Persistence unit not shown in JON when custom region_prefix is specified
Environment
- Red Hat JBoss Operations Network
- 3.3.0
Issue
JON 3.3.0GA update 02 shows only some persistence unit configured on EAP 6.3.3
This is happening after resizing infinispan second level cache
Resolution
An upstream workaround has been backported.
The workaround, as stated in WFLY-5478, means that instead of a user specifying
<property name="hibernate.cache.region_prefix"
value="database_cache_postgres_webtng"/>
They will now specify:
<property name="jboss.as.jpa.scopedname"
value="database_cache_postgres_webtng"/>
Or:
<property name="hibernate.cache.region_prefix"
value="database_cache_postgres_webtng"/>
<property name="jboss.as.jpa.scopedname"
value="database_cache_postgres_webtng"/>
Where scopedname and region_prefix must be the same if both are specified.
A consequence of this workaround is that when a user specfies a scopedname value it changes the naming scheme used by wildfly for the persistence unit. Therefore this fix requires the web console to be updated to support the new naming scheme introduced by scopedname (see [1], [2]).
This has been fixed with BZ1273382 This content is not included.Update JPA Subsystem to respect "jboss.as.jpa.scopedname" property
[1] Content from issues.jboss.org is not included.https://issues.jboss.org/browse/HAL-882
[2] This content is not included.https://bugzilla.redhat.com/show_bug.cgi?id=1273382
Root Cause
The fix for Content from issues.jboss.org is not included.AS7-4441 was preventing the PU from being exposed in the management console when the region_prefix property is specified. This is causing issues in JON, as JON is unable to communicate with the PU (only when region_prefix is set).
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.