On Sun, Mar 25, 2012 at 9:28 PM, Kasun Gajasinghe <[email protected]> wrote: > > > On Sun, Mar 25, 2012 at 1:06 PM, Muhammed Shariq <[email protected]> wrote: >> >> Hi, >> >> In the latest Stratos Manger trunk build, there is a weird issue when >> deploying some admin services. Once you extract the pack the very 1st time >> all the admin services gets deployed properly and can access the dashboard, >> but once you down the server and start again some of the services are not >> found at the endpoint !! osgi console suggest that all bundles are active >> .. >> >> When I do a listAdminServices on osgi console I see that the problematic >> services doesn't have an EPR (attach the output here with). Most of these >> admin services are stratos specific, but I don't think we have done many >> changes to those service recently. >> >> AmilaJ brought this issue up last week. After a quick look we were fairly >> convinced that the issue was caused by a change in core (we tried by >> replacing some old carbon core jars from my local distro and the issue went >> away). Any ideas what could be causing this issue, or at least where I >> should be looking to get to the root cause ? I am kinda lost at the moment !
It was difficult for us to narrow down the issue as there were no error or any other type of log messages. Server starts fine, but services are missing. I am not sure why there aren't any indication about, "why those admin services are not deployed". It will be really great to have some sort of an indication (log message, exception etc ...) to say that, certain admin services were not deployed. Thanks AmilaJ > > > Did some testing with help from Shariq. Apparently, the issue is with the > recent changes to the persistence layer. Apparently, some of the Admin > services are also persisted which shouldn't happen. Persistence layer > blindly persist the services it receive, as it should be. Wonder why > deployment interceptor passes this down for persistence. > > Just to make sure, services > like org.wso2.carbon.account.mgt, org.wso2.carbon.bam.core, org.wso2.carbon.issue.tracker.mgt > are admin services, and are hidden servces, right? I've noticed some issues > due to a similar case previously. > > Thanks, > --KasunG > > >> >> >> -- >> Thanks, >> Shariq. >> Phone: +94 777 202 225 >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > > -- > Kasun Gajasinghe > Software Engineer; WSO2 Inc.; http://wso2.com > > , > email: kasung AT spamfree wso2.com cell: +94 (77) 678-0813 > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://blog.kasunbg.org > > > twitter: http://twitter.com/kasunbg > > > -- Mobile : +94773330538 _______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
