Hi Ruwan,

Did we manage to fix this?

Cheers,
Prabath

On Wed, Jul 15, 2015 at 7:54 PM, Ruwan Abeykoon <ruw...@wso2.com> wrote:

> Hi All,
> Yet another update on $subject
> The intermittent classloader issue could not be resolved yet. Here are few
> observations.
>
> The jaggery application calls the CarbonWebappClassloader to lookup a
> class in governance API bundle. This fails.
> However the same class is properly loaded via different bundle (Say
> WebappManagment) classloader which is not initially loaded via
> Tomcat/Jaggary app.
> No issue found in "launch.ini". No apparent conflicting bundles or
> unsatisfied dependencies. There were few duplicate packaged exported by
> different bundles, but seems they are not causing the issue.
>
> I am working with Sameera  to find the underlying cause.
>
> I am unable to create a PR with the version change due to above issue.
>
> Cheers,
> Ruwan
>
> On Wed, Jul 8, 2015 at 11:28 AM, Ruwan Abeykoon <ruw...@wso2.com> wrote:
>
>> Hi Team,
>> I would like to update you on $subject
>>
>> 1. All the module versions are bumped up to 1.1.0-SNAPSHOT
>> 2. Removed all the carbon 4.2.0 and related features which depend on C
>> 4.2.0 and added Carbon 4.4.0 kernel and other features compatible with
>> Carbon 4.4.0 (registry, governance, mediation, Jaggery, etc).
>> 3. Forked ES for C 4.4.0 version bump up, upgraded the dependencies, Had
>> to change few classes in ES to be able to get it compatible with governance
>> 4.5.1.
>> 4. Changed few classes and jaggery files which needed to be changed due
>> to method signature changes in registry
>> (e.g. GenericArtifact.invokeAction(...)).
>>
>> Current Status with Carbon 4.4.0
>> 1. AppM builds and starts successfully
>> 2. Can create web applications, publish and subscribe.
>>
>> Present Issues which I am working on.
>> 1. Intermittent, Classloader or similar issue in loading
>> org.wso2.carbon.governance.api.generic [1]
>> 2. Need to test most of other areas(mobile apps, policy, throttling)
>> 3. At the moment, update synapse config to the gateway is failing.
>> 4. Clean up the code which had experimental/debug code
>> 5. Remove unwanted/duplicate jaggery modules [2]
>>
>> None of the changes are committed to any public repository yet.
>>
>>
>> [1] Mail thread "[Dev]Class Loading issue in Jaggery, Carbon 4.4.0"
>> [2] Mail thread  "[Dev][AppM] Removing multiple "modules" directories"
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Architect,*
>> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
>> *lean.enterprise.middleware.*
>>
>> email: ruw...@wso2.com
>> phone:(+94) 777739736
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Architect,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
> phone:(+94) 777739736
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to