[jboss-jira] [JBoss JIRA] (AS7-2419) Provide management use cases and operations of the JPA subsystem

[Scott Marlow (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641138#comment-12641138 ] 

Scott Marlow commented on AS7-2419:
-----------------------------------

Hi, I attached some examples to AS7-2419.  As you can see from the https://issues.jboss.org/secure/attachment/12348545/entity2lc.txt attachment, the jpa statistics (Hibernate 4 is the only persistence provider currently supported) are added dynamically under deployments:

cd deployment
cd jpa_SecondLevelCacheTestCase.jar
cd subsystem
cd jpa

At this level, the only supported provider is Hibernate.  Its possible that other entries will show up at this level but I don't think you should worry about them today (I tried to pick a format that won't change in the future).  

cd hibernate-persistence-unit

At this level is a list of all deployed persistence units (one per persistence unit in a persistence.xml)

cd jpa_SecondLevelCacheTestCase.jar#mypc

At this level, statistics are disabled by default but can be enabled via a property setting in the persistence.xml or operation ":write-attribute(name=enabled,value=true)".  Other operations at this level are {clear, summary}.  Clear clears the statistics and summary logs the statistics to the AS server.log.

At this level are the Hibernate jpa statistics.

Also at this level, are sub-levels { entity-cache, query-cache, collection, entity}

entity-cache contains statistics for each entity class in the second level cache.  Each entity class name is a separate sub-address.

entity contains statistics for each entity class.  Each entity class is a separate sub-address.  The address should be meaningful as the identifying name and shown in the ui I think.

collection contains statistics for each collection.  Each collection is a separate sub-address (the address should be meaningful as the identifying name and shown in the ui I think).

query-cache contains statistics for each query in the second level query-cache. 

I think that we will also want to add (at the persistence unit level, e.g. jpa_SecondLevelCacheTestCase.jar#mypc) a way to clear the second level cache.  Lets call that operation evictall, when we add it later.  If you want me to add evictall before you get started, assign this jira back to me. :)


                
> Provide management use cases and operations of the JPA subsystem 
> -----------------------------------------------------------------
>
>                 Key: AS7-2419
>                 URL: https://issues.jboss.org/browse/AS7-2419
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Console, Domain Management
>            Reporter: Heiko Braun
>            Assignee: Scott Marlow
>             Fix For: 7.1.0.CR1
>
>         Attachments: entity2lc.txt, read-resource-description.txt
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira