[jboss-jira] [JBoss JIRA] (WFLY-13566) Ensure that Jandex indexes are released from JPA deployment memory after deployment completes

Ilia Vassilev (Jira) issues at jboss.org
Thu Jun 11 13:19:40 EDT 2020


     [ https://issues.redhat.com/browse/WFLY-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilia Vassilev updated WFLY-13566:
---------------------------------
    Labels: downstream_dependency  (was: )


> Ensure that Jandex indexes are released from JPA deployment memory after deployment completes
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFLY-13566
>                 URL: https://issues.redhat.com/browse/WFLY-13566
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: JBoss AS7 7.2.0.Final
>            Reporter: Scott Marlow
>            Assignee: Scott Marlow
>            Priority: Major
>              Labels: downstream_dependency
>             Fix For: 21.0.0.Beta1
>
>
> org.jboss.as.jpa.service.PersistenceUnitServiceImpl#start() needs to always call pu.setAnnotationIndex(null) to clear the deployment reference to the Jandex Indexes.  
> Currently without the fix, the Jandex Index will be released at application undeployment time.  With the fix, the Jandex Index memory will be released after application deployment is complete.  Note that the Jandex Index contains metadata for the application deployment classes and are not needed after deployment is complete.
> Note that this problem shouldn't occur when persistence.xml contains:
> {code}
> <property name="wildfly.jpa.twophasebootstrap" value="false"/>
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list