Sorry for lack of detail in this post - am posting from a remote location to where ocurred so don't have stack traces handy.
This problem occured in both 2.2.1 RC1 and last night when i upgraded to RC2. The effect is the failure to start of the MBean: portal:policy=PortalPolicyConfigStore,type=Component In both cases I have found that I can circumvent the problem by changing the MBean config from | <depends optional-attribute-name="CacheProvider" proxy-type="attribute">portal:service=TreeCacheProvider,type=transient</depends> | to | <depends optional-attribute-name="CacheProvider" proxy-type="attribute">portal:service=TreeCacheProvider,type=persistent</depends> | The MBean then deploys and I can see the portal. Setting it to persistent seems to match the config for the similar MBeans just above this one in the jboss-service.xml file. Why is this one set to be different? What is the effect of my change? If anyone iterested can post further info later. Am using JBossAS 4.0.3SP1 with Derby 10.1.2.1 backing db. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920361#3920361 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920361 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
