On Mon, Mar 26, 2012 at 11:09 AM, Afkham Azeez <[email protected]> wrote:

>
>
> 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 !
>>>
>>
>> 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.
>>
>
> DeploymentInterceptor should check for AdminServices & HiddenServices, and
> refrain from serializing & deserializing metadata of such services.
>

Exactly. I think we found a bug in the DeploymentInterceptor that was there
before the new changes. I checked the contents of the meta files of these
services. These services are marked as Admin, and Hidden services as the
relevant parameters are there. I'm working on this today.

<parameter name="adminService" locked="true">true</parameter>
<parameter name="hiddenService" locked="true">true</parameter>



>
>> 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* <http://blog.kasunbg.org>
>>
>> *
>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
>>
>> *
>> *
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*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* <http://blog.kasunbg.org>

*
twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>

*
*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to