[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-647) StorageState seem to get left over druing debug/test cycles and hot deployment

[Thomas Diesler (JIRA)]

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

Thomas Diesler edited comment on JBOSGI-647 at 5/3/13 1:57 AM:
---------------------------------------------------------------

Duplicates JBOSGI-613

Should be fixed in wildly-8.0.0.Alpha1
                
      was (Author: thomas.diesler):
    Duplicates JBOSGI-613
                  
> StorageState seem to get left over druing debug/test cycles and hot deployment
> ------------------------------------------------------------------------------
>
>                 Key: JBOSGI-647
>                 URL: https://issues.jboss.org/browse/JBOSGI-647
>             Project: JBoss OSGi
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Core Framework
>         Environment: EAP 6.1-beta
>            Reporter: Darryl Miles
>            Assignee: Thomas Diesler
>            Priority: Minor
>
> When developing for JBoss EAP 6.1-beta under Eclipse IDE after a number of deploys the number of StorageState seem to get left over for the same bundle names, but with unique instance/deployment id's.
> Also I don't believe the the OSGi bundles made any use of the storage API directly so I am thinking that the setup/provisioning of such data areas could be delayed until first use and also be cleaned up entirely if no write access was made into the area.
> This is an example of what is occurring after a number of published and JBoss AS restarts, some of which will be when the OSGi aware bundle maybe deployed.
> 17:42:33,740 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=26,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]
> 17:42:33,743 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=28,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]
> 17:42:33,745 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=34,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]
> 17:42:33,747 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=36,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]
> 17:42:33,748 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=38,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]
> 17:42:33,751 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-1) Created storage state: StorageState[id=40,rev=0,startlevel=1,started=true,location=com-domain-jpa-0.0.1-SNAPSHOT.jar]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira