Re: [Dev] Introducing 'blocking' attribute to the Call mediator of DevS ESB Graphical Tool

[Rajeevan Vimalanathan]

Hi All,

This has been fixed now and will be available from Developer Studio 3.8.0
Beta.

Thanks,
Rajeevan

On Thu, Sep 10, 2015 at 4:41 PM, Rajeevan Vimalanathan 
wrote:

> Thanks Kathees for the info, will do the implementation accordingly.
>
> Thanks,
> Rajeevan
>
> On Thu, Sep 10, 2015 at 4:35 PM, Kathees Rajendram 
> wrote:
>
>> Hi Rajeevan,
>>
>> The blocking attribute should be in the call mediator.
>> In the blocking calls, the attribute' value should be true.
>> 
>>
>> In the non blocking calls,The blocking attribute is not mandatory.
>> 
>>
>> Thanks,
>> Kathees
>>
>> On Thu, Sep 10, 2015 at 4:07 PM, Rajeevan Vimalanathan <
>> rajeev...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We found that ESB has introduced a new attribute 'blocking=true/false'
>>> (Enable Blocking Calls) to the Call mediator from ESB 4.9.0 when testing.
>>> So we will add the same to Call mediator at ESB Graphical tool [1] of
>>> Developer Studio.
>>>
>>> http://ws.apache.org/ns/synapse"/>
>>>
>>> [1] https://wso2.org/jira/browse/TOOLS-3134
>>>
>>> Thanks,
>>> Rajeevan
>>>
>>> --
>>> Vimalanathan Rajeevan
>>> Software Engineer,
>>> WSO2, Inc. *http://wso2.com* 
>>> Lean.Enterprise.Middleware
>>>
>>> Mobile:
>>> *+94 773090875 <%2B94%20773090875>*
>>> LinkedIn:
>>> *https://www.linkedin.com/in/RajeevanVimalanathan
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>
>
>
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* 
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> *
>



-- 
Vimalanathan Rajeevan
Software Engineer,
WSO2, Inc. *http://wso2.com* 
Lean.Enterprise.Middleware

Mobile:
*+94 773090875*
LinkedIn:
*https://www.linkedin.com/in/RajeevanVimalanathan
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting the profile which WSO2 server has started with

[Harsha Thirimanna]

Hi Sameera,

Yes, we will discuss this with the team and will provide a meaningful name
according to the feature group. We just prepared IS for profiling and not
finalized yet. Thanks for prompting this.


*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

*Lean . Enterprise . Middleware*


On Fri, Sep 11, 2015 at 11:53 AM, Sameera Jayasoma  wrote:

> profile=all doesn't makes sense to me :)
>
> Can we have proper name for this profile?
>
> On Fri, Sep 11, 2015 at 11:51 AM, Chamila Wijayarathna 
> wrote:
>
>> Hi Sameera,
>>
>> In IS 5.1.0 we are supporting workflow for user management operations.
>> There we have added BPEL and Human Task components of BPS to IS.
>> But in default profile we don't enable those features and they are only
>> enabled in "profile=all".
>>
>> Thanks
>>
>> On Fri, Sep 11, 2015 at 11:45 AM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Chamila,
>>>
>>> What do you mean by profile=all?
>>>
>>> On Fri, Sep 11, 2015 at 11:00 AM, Chamila Wijayarathna >> > wrote:
>>>
 Hi all,

 We start WSO2 IS using following profiles.

 ./wso2server.sh
 ./wso2server.sh -Dprofile=all

 Is it possible to check from java code, for which profile server
 started from?

 Thank You

 --
 *Chamila Dilshan Wijayarathna,*
 Software Engineer
 Mobile:(+94)788193620
 WSO2 Inc., http://wso2.com/

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Sameera Jayasoma,
>>> Software Architect,
>>>
>>> WSO2, Inc. (http://wso2.com)
>>> email: same...@wso2.com
>>> blog: http://blog.sameera.org
>>> twitter: https://twitter.com/sameerajayasoma
>>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>>> Mobile: 0094776364456
>>>
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting the profile which WSO2 server has started with

[Sameera Jayasoma]

profile=all doesn't makes sense to me :)

Can we have proper name for this profile?

On Fri, Sep 11, 2015 at 11:51 AM, Chamila Wijayarathna 
wrote:

> Hi Sameera,
>
> In IS 5.1.0 we are supporting workflow for user management operations.
> There we have added BPEL and Human Task components of BPS to IS.
> But in default profile we don't enable those features and they are only
> enabled in "profile=all".
>
> Thanks
>
> On Fri, Sep 11, 2015 at 11:45 AM, Sameera Jayasoma 
> wrote:
>
>> Hi Chamila,
>>
>> What do you mean by profile=all?
>>
>> On Fri, Sep 11, 2015 at 11:00 AM, Chamila Wijayarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> We start WSO2 IS using following profiles.
>>>
>>> ./wso2server.sh
>>> ./wso2server.sh -Dprofile=all
>>>
>>> Is it possible to check from java code, for which profile server started
>>> from?
>>>
>>> Thank You
>>>
>>> --
>>> *Chamila Dilshan Wijayarathna,*
>>> Software Engineer
>>> Mobile:(+94)788193620
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>



-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Lasantha Fernando]

Thanks Hasintha for pointing this out.

@Manu, UES team, would you be able to do another release with the above fix?

On 11 September 2015 at 12:04, Hasintha Indrajee  wrote:

> The issue with jaggery-extension release was referring and old pom as
> parent pom [1]. You need to update it into a new version of jaggery-parent
> pom  which is released with wss4j version upgrade.
>
> [1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>
> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando 
> wrote:
>
>> Hi all,
>>
>> Thanks for the quick turnaround and releasing the required repo quickly.
>> Appreciate your support very much!
>>
>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing
>> wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the
>> artifact packed inside the plugins folder in the zip at [1].
>>
>> Can you check why the old version is still getting packed and provide a
>> release with the fixes? I think there is an issue in how the wss4j
>> dependency has been specified. It is not there in the dependencyManagement
>> section of the top level pom, but has been specified as a dependency
>> without versions in child level poms. Also I could not find any place where
>> the 'wss4j.osgi.version' seems to be used. Can you check on these issues
>> and fix it so that the proper jar is packed if needed (or drop the jar
>> altogether from the feature if possible) ?
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>
>> Thanks,
>> Lasantha
>>
>> On 10 September 2015 at 19:58, KasunG Gajasinghe  wrote:
>>
>>>
>>> Released the repo from staging.
>>>
>>> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena 
>>> wrote:
>>>
 Hi all,

 We have prepared the release steps for jagggery-extensions 1.4.1.
 Builder team please close the repo and release jagggery-extensions
 1.4.1.

 Thanks!
 -Chanaka

 On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando 
 wrote:

> Hi Manu, UES team,
>
> It seems this is fixed in jaggery 0.11.0. If we move our dashboard
> dependency version from 0.10.3 to 0.11.0, will this affect our current
> dashboard functionality? (Any API changes, functionality changes of
> existing features)
>
> Also, as per the thread started by KasunG, it seems this issue is
> there in jaggery-extensions as well. So can we get a release for
> jaggery-extensions and jaggery (if upgrade does not work) with the proper
> fix?
>
> We are currently planning to put an RC release of CEP tomorrow and
> currently we are blocked on releasing the dependent repos because of this.
> Would appreciate a response at your earliest please.
>
> Thanks,
> Lasantha
>
> On 10 September 2015 at 15:17, Lasantha Fernando 
> wrote:
>
>> Thanks Harsha anyway for the suggestion.. :-)
>>
>> After removing the older wss4j from the bundles.info of the pack as
>> suggested by Gokul, the pack is starting fine. So I guess we will have to
>> fix the jaggery features properly to resolve this issue.
>>
>> Thanks,
>> Lasantha
>>
>> On 10 September 2015 at 15:03, Harsha Thirimanna 
>> wrote:
>>
>>> Sorry , didn't see your reply. :)
>>> On Sep 10, 2015 3:02 PM, "Harsha Thirimanna" 
>>> wrote:
>>>
 Hi Lasantha,

 Can't we enable logs and check whether which component will take
 more time
 OR
 do profiling to get the root cause.
 On Sep 10, 2015 2:34 PM, "Gokul Balakrishnan" 
 wrote:

> We're facing the same issue in the later DAS packs, where the pack
> startup is much slower after the upgrade. This is apparent under Java 
> 8 as
> well (1.8.0_51).
>
> Thanks,
>
> On 10 September 2015 at 14:29, Lasantha Fernando <
> lasan...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> For product-cep, after upgrading the dependent carbon identity
>> repo version from 4.5.5 to 4.5.6, the server startup has become 
>> extremely
>> slow. If you downgrade this particular identity version back to 
>> 4.5.5, it
>> starts normally.
>>
>> The difference is from around 24-30 sec startup time with
>> identity 4.5.5 and 70-80 sec startup time for identity 4.5.6 with no 
>> other
>> changes.
>>
>> In the OSGi console, all bundles are active and all our WSO2 OSGi
>> services are also  active for both packs.
>>
>> Any idea why this issue is coming up? A similar issue was
>> reported in DAS packs as well after they upgraded their 

Re: [Dev] Getting the profile which WSO2 server has started with

[Chamila Wijayarathna]

Hi Sameera,

In IS 5.1.0 we are supporting workflow for user management operations.
There we have added BPEL and Human Task components of BPS to IS.
But in default profile we don't enable those features and they are only
enabled in "profile=all".

Thanks

On Fri, Sep 11, 2015 at 11:45 AM, Sameera Jayasoma  wrote:

> Hi Chamila,
>
> What do you mean by profile=all?
>
> On Fri, Sep 11, 2015 at 11:00 AM, Chamila Wijayarathna 
> wrote:
>
>> Hi all,
>>
>> We start WSO2 IS using following profiles.
>>
>> ./wso2server.sh
>> ./wso2server.sh -Dprofile=all
>>
>> Is it possible to check from java code, for which profile server started
>> from?
>>
>> Thank You
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Hasintha Indrajee]

The issue with jaggery-extension release was referring and old pom as
parent pom [1]. You need to update it into a new version of jaggery-parent
pom  which is released with wss4j version upgrade.

[1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23

On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando 
wrote:

> Hi all,
>
> Thanks for the quick turnaround and releasing the required repo quickly.
> Appreciate your support very much!
>
> Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing
> wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the
> artifact packed inside the plugins folder in the zip at [1].
>
> Can you check why the old version is still getting packed and provide a
> release with the fixes? I think there is an issue in how the wss4j
> dependency has been specified. It is not there in the dependencyManagement
> section of the top level pom, but has been specified as a dependency
> without versions in child level poms. Also I could not find any place where
> the 'wss4j.osgi.version' seems to be used. Can you check on these issues
> and fix it so that the proper jar is packed if needed (or drop the jar
> altogether from the feature if possible) ?
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>
> Thanks,
> Lasantha
>
> On 10 September 2015 at 19:58, KasunG Gajasinghe  wrote:
>
>>
>> Released the repo from staging.
>>
>> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena 
>> wrote:
>>
>>> Hi all,
>>>
>>> We have prepared the release steps for jagggery-extensions 1.4.1.
>>> Builder team please close the repo and release jagggery-extensions 1.4.1.
>>>
>>> Thanks!
>>> -Chanaka
>>>
>>> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando 
>>> wrote:
>>>
 Hi Manu, UES team,

 It seems this is fixed in jaggery 0.11.0. If we move our dashboard
 dependency version from 0.10.3 to 0.11.0, will this affect our current
 dashboard functionality? (Any API changes, functionality changes of
 existing features)

 Also, as per the thread started by KasunG, it seems this issue is there
 in jaggery-extensions as well. So can we get a release for
 jaggery-extensions and jaggery (if upgrade does not work) with the proper
 fix?

 We are currently planning to put an RC release of CEP tomorrow and
 currently we are blocked on releasing the dependent repos because of this.
 Would appreciate a response at your earliest please.

 Thanks,
 Lasantha

 On 10 September 2015 at 15:17, Lasantha Fernando 
 wrote:

> Thanks Harsha anyway for the suggestion.. :-)
>
> After removing the older wss4j from the bundles.info of the pack as
> suggested by Gokul, the pack is starting fine. So I guess we will have to
> fix the jaggery features properly to resolve this issue.
>
> Thanks,
> Lasantha
>
> On 10 September 2015 at 15:03, Harsha Thirimanna 
> wrote:
>
>> Sorry , didn't see your reply. :)
>> On Sep 10, 2015 3:02 PM, "Harsha Thirimanna" 
>> wrote:
>>
>>> Hi Lasantha,
>>>
>>> Can't we enable logs and check whether which component will take
>>> more time
>>> OR
>>> do profiling to get the root cause.
>>> On Sep 10, 2015 2:34 PM, "Gokul Balakrishnan" 
>>> wrote:
>>>
 We're facing the same issue in the later DAS packs, where the pack
 startup is much slower after the upgrade. This is apparent under Java 
 8 as
 well (1.8.0_51).

 Thanks,

 On 10 September 2015 at 14:29, Lasantha Fernando  wrote:

> Hi Devs,
>
> For product-cep, after upgrading the dependent carbon identity
> repo version from 4.5.5 to 4.5.6, the server startup has become 
> extremely
> slow. If you downgrade this particular identity version back to 
> 4.5.5, it
> starts normally.
>
> The difference is from around 24-30 sec startup time with identity
> 4.5.5 and 70-80 sec startup time for identity 4.5.6 with no other 
> changes.
>
> In the OSGi console, all bundles are active and all our WSO2 OSGi
> services are also  active for both packs.
>
> Any idea why this issue is coming up? A similar issue was reported
> in DAS packs as well after they upgraded their dependent repos.
>
> These tests were done with JDK 1.7.0_80.
>
> Thanks,
> Lasantha
>
> --
> *Lasantha Fernando*
> Senior Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 

[Dev] carbon-deployment 4.5.3 released!

[Kalpa Welivitigoda]

Hi Devs,

$subject,

org.wso2.carbon.deployment
carbon-deployment
4.5.3

-- 
Best Regards,

Kalpa Welivitigoda
Software Engineer, WSO2 Inc. http://wso2.com
Email: kal...@wso2.com
Mobile: +94776509215
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 AS 5.3.0 RC2

[Kalpa Welivitigoda]

Hi Devs,

This is the second release candidate of WSO2 AS 5.3.0.

This release fixes the following issues:

https://wso2.org/jira/issues/?filter=12251

Please download, test and vote. Vote will be open for 72 hours or as needed.

*Binary distribution files:*
http://svn.wso2.org/repos/wso2/people/kalpaw/as-5.3.0-rc2/


*Maven staging repo:*
http://maven.wso2.org/nexus/content/repositories/orgwso2appserver-073/


*The tag to be voted upon:*
https://github.com/wso2/product-as/tree/v5.3.0-rc2


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release

Thanks and Regards,
~ WSO2 Application Server Team ~
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting the profile which WSO2 server has started with

[Sameera Jayasoma]

Hi Chamila,

What do you mean by profile=all?

On Fri, Sep 11, 2015 at 11:00 AM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> We start WSO2 IS using following profiles.
>
> ./wso2server.sh
> ./wso2server.sh -Dprofile=all
>
> Is it possible to check from java code, for which profile server started
> from?
>
> Thank You
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API

[Udara Liyanage]

Hi Nuwan,

Could you please point me to the test case location, me too is looking for
a similar sample.

On Fri, Sep 11, 2015 at 3:39 PM, Nuwan Wimalasekara  wrote:

> Hi Udara,
>
> In APIM integration test, HTTP endpoint is used to call the
> RestAPI(Publisher and Store) and It is working fine without any issue. This
> should work
>
> Thanks,
> Nuwanw
>
> On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias  wrote:
>
>> They run on HTTPS only. If you send an http request, it automatically
>> redirects to https.
>>
>> On Fri, Sep 11, 2015 at 8:46 AM, Udara Liyanage  wrote:
>>
>>> Hi,
>>>
>>> I could create APIs by changing to port 9443 and protocol to HTTPS.
>>> However why does REST APIs runs on HTTP?
>>>
>>> curl -X POST -c cookies
>>> https://localhost:9443/publisher/site/blocks/user/login/ajax/login.jag
>>> -d 'action=login=admin=admin' -k
>>>
>>>
>>> curl -b cookies -k
>>> https://localhost:9443/publisher/site/blocks/item-add/ajax/add.jag -d
>>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>>> a phone
>>> number=phone,mobile,multimedia=nonsecured===Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>>> x...@ee.com=xx=g...@ww.com"
>>> -d'endpoint_config={"production_endpoints":{"url":"
>>> http://ws.cdyne.com/phoneverify/phoneverify.asmx","config":null},"endpoint_type":"http
>>> "}';
>>>
>>> On Fri, Sep 11, 2015 at 4:18 AM, Udara Liyanage  wrote:
>>>
 Hi,

 I got this error while trying the sample Add API command mentioned in
 the doc . No
 backend error is displayed, any idea?


  $ curl -X POST -c cookies
 http://localhost:9763/publisher/site/blocks/user/login/ajax/login.jag
 -d 'action=login=admin=admin'
 {"error" : false}


  $ curl -X POST -b cookies
 http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d
 "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
 a phone
 number=phone,mobile,multimedia=nonsecured=Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
 x...@ee.com=xx=g...@ww.com"
 -d'endpoint_config={"production_endpoints":{"url":"
 http://ws.cdyne.com/phoneverify/phoneverify.asmx
 ","config":null},"endpoint_type":"http"}';
 {"error" : true, "message" : "*timeout*"}

 --

 Udara Liyanage
 Software Engineer
 WSO2, Inc.: http://wso2.com
 lean. enterprise. middleware

 web: http://udaraliyanage.wordpress.com
 phone: +94 71 443 6897

>>>
>>>
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Technical Lead - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>


-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Lasantha Fernando]

Thanks a lot Manu for your help!!

On 11 September 2015 at 21:47, Manuranga Perera  wrote:

> done
>
>
> On Fri, Sep 11, 2015 at 9:37 PM, Lasantha Fernando 
> wrote:
>
>> Hi Manu,
>>
>> Tested the CEP pack with the staged artifacts and the functionality is
>> working fine. Please release the repo from staging.
>>
>> Thanks,
>> Lasantha
>>
>> On 11 September 2015 at 21:10, Manuranga Perera  wrote:
>>
>>> update
>>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-084/
>>> please try and let me know
>>>
>>> On Fri, Sep 11, 2015 at 8:00 PM, Manuranga Perera  wrote:
>>>
 please try with
 http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/

 On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera 
 wrote:

> please try 1.3.4 version with
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
>
>
> On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera 
> wrote:
>
>> ok will do. reverting the staging.
>>
>> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando > > wrote:
>>
>>> When the jaggery versions are downgraded, it starts functioning
>>> properly without any issue, albeit with the startup delay issue.
>>>
>>> If we can get releases of jaggery and jaggery-extensions for 0.10.x
>>> and 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it 
>>> should
>>> resolve all the issues we are currently facing.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 11 September 2015 at 15:45, Lasantha Fernando 
>>> wrote:
>>>
 Hi Manu,

 Thanks for the quick turnaround. This particular version upgrades
 the proper wss4j version and the startup issue gets fixed. But
 unfortunately, when we upgrade from jaggery 0.10.3 to 0.11.0 and
 jaggery-extensions from 1.3.2 to 1.4.2 to get these fixes, our 
 dashboard is
 broken.

 When creating a single dashboard, about 20 additional dashboards
 with the same name get created in our dashboards ui. See attached
 screenshot.

 @Manu, UES team, sorry to trouble you guys again, but would you
 guys be able to release new repos for jaggery-0.10.x and
 jaggery-extensions-1.3.x. It seems the upgrade from 0.10.x to 0.11.0
 doesn't work and we've already tested the dashboard extensively with 
 the
 older jaggery versions.

 Thanks,
 Lasantha

 On 11 September 2015 at 14:25, KasunG Gajasinghe 
 wrote:

>
> Closed the staging repo as requested by Jaggery team. Please find
> the url -
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>
> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
> wrote:
>
>> will release with today.
>>
>> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando <
>> lasan...@wso2.com> wrote:
>>
>>> Thanks Hasintha for pointing this out.
>>>
>>> @Manu, UES team, would you be able to do another release with
>>> the above fix?
>>>
>>> On 11 September 2015 at 12:04, Hasintha Indrajee <
>>> hasin...@wso2.com> wrote:
>>>
 The issue with jaggery-extension release was referring and old
 pom as parent pom [1]. You need to update it into a new version of
 jaggery-parent pom  which is released with wss4j version upgrade.

 [1]
 https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23

 On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
 lasan...@wso2.com> wrote:

> Hi all,
>
> Thanks for the quick turnaround and releasing the required
> repo quickly. Appreciate your support very much!
>
> Unfortunately, it seems the jaggery-extensions-1.4.1 is still
> packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 
> version. Please
> see the artifact packed inside the plugins folder in the zip at 
> [1].
>
> Can you check why the old version is still getting packed and
> provide a release with the fixes? I think there is an issue in 
> how the
> wss4j dependency has been specified. It is not there in the
> dependencyManagement section of the top level pom, but has been 
> specified
> as a dependency without versions in child level poms. Also I 
> could not find
> any place where the 'wss4j.osgi.version' seems to be used. 

Re: [Dev] [BPS][IS][Workflow] Two Human Tasks created at same event goes to different states

[Chamila Wijayarathna]

Hi Vinod,

At creation of workflows we can assign both users and roles to own the
human tasks. All so we can assign more than one user to own tasks. Above
question occurred since I was unaware of the difference between two states.
Since we can assign roles to own human tasks, I human tasks going to READY
state is unavoidable, so we handled it from IS side as well as at IS
dashboard.

Thanks

On Fri, Sep 11, 2015 at 5:39 PM, Vinod Kavinda  wrote:

> Hi Chamila,
> It is the correct behaviour as Hasitha mentioned.
> But, Are you assigning users for the human task using roles? As I
> remember, in the bpel process we created for the workflow support, you can
> pass users also as the potential owners to the ht. Try passing only the
> user name in the initial request inside user tags. Then it will be in
> reserved state.
> Regards,
> Vinod kavinda
> On Sep 10, 2015 3:40 PM, "Hasitha Aravinda"  wrote:
>
>> Hi Chamila,
>>
>> Yes, This is correct user delegation behavior according to HumanTask spec
>> [1]. This is what is happening in your scenario.
>>
>> When first task is created, you have only one user in admin/role1 roles.
>> That means task has only one potential owner. When task has only one
>> potential owner, task is automatically assigned that user and moves to
>> RESERVED state.
>>
>> Then 2nd task is creates, you have multiple uses in admin/role1 roles.
>> When task has multiple potential owners, task remains in READY state. Once
>> user claims, it moves to RESERVED state. But any potential owner can start
>> Ready tasks.
>>
>> Basically you have to search for both RESERVED and READY tasks for
>> approval.
>>
>> [1] -
>> http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html#_Toc135718798
>>
>>
>> Thanks,
>> Hasitha.
>>
>>
>> On Thu, Sep 10, 2015 at 2:37 PM, Chamila Wijayarathna 
>> wrote:
>>
>>> Hi Nandika,
>>>
>>> I am running recently built IS pack workflow features. I came up with
>>> following scenario which is confusing.
>>>
>>> I have two workflows which use same BPS.
>>> Workflow1 need to be approved by 'admin' role and Workflow2 need to be
>>> approved by 'role1' role.
>>> Then I have a user 'user1' in my userstore who has both 'admin' and
>>> 'role1' roles.
>>>
>>> Then I have configured two associations for addUser operation, where
>>> association1 get assigned to workflow1 and association2 get assigned to
>>> workflow2.
>>>
>>> Then when I add a new user to user store, 2 workflows get triggered, but
>>> when I check the human tasks associated with them by calling
>>> 'HumanTaskClientAPIAdmin', what I observe is even though there are two
>>> human tasks created, one task is in 'RESERVED' state while other task is in
>>> 'READY' state. This only happens when I add a user who has both 'admin' and
>>> 'role1' roles. If there are no user with both roles, both tasks goes to the
>>> 'RESERVED' state which is the expected behavior.
>>>
>>> What is the reason for this?
>>>
>>> Thank You!
>>>
>>> --
>>> *Chamila Dilshan Wijayarathna,*
>>> Software Engineer
>>> Mobile:(+94)788193620
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +1 201 887 1971, +94 718 210 200
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>


-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cron job on MessageProcessor?

[John Hawkins]

Thanks for your thoroughness folks !!

I'm not sure, from the description, what gets sent to  the
message.processor.deactivate.sequence
- is it the message that failed or just the reply from the server or both?

cheers,
John.

John Hawkins
Director: Solutions Architecture


On Thu, Sep 10, 2015 at 7:47 PM, Vanjikumaran Sivajothy 
wrote:

>
> [1] jira for the doc
> https://wso2.org/jira/browse/DOCUMENTATION-952
>
> On Thu, Sep 10, 2015 at 11:44 AM, Vanjikumaran Sivajothy 
> wrote:
>
>> Hi John,
>>
>>
>> On Wed, Sep 9, 2015 at 4:51 AM, John Hawkins  wrote:
>>
>>> Aargh - I meant "max.delivery.drop" ! I can't see that docced anywhere?
>>>
>>
>>
>> This new parameter is introduced in ESB 4.9.0 onwards. It should be there
>> in the 490 documentation according to [1]
>>
>> [1]  https://docs.wso2.com/display/ESB490/Message+Forwarding+Processor
>>
>>
>>
>>
>>> So we are implementing a trigger sequence for when MessageProcessor gets
>>> de-activated? I think is the same thing I'm thinking of isn't it ? When the
>>> message fails to get sent after n retries then the sequence gets called -
>>> presumably with the message that's failing as part of the payload in the
>>> sequence - along with the error message from the server too?
>>>
>>> cheers for the clarifications !
>>> John.
>>>
>>> John Hawkins
>>> Director: Solutions Architecture
>>>
>>>
>>> On Wed, Sep 9, 2015 at 12:41 PM, Ravindra Ranwala 
>>> wrote:
>>>
 Hi John,

 Message Processor Max Delivery attempt parameter is clearly documented
 here [1].


 Anyway in ESB 4.9.0 version we have deactivateSequence, which can be
 triggered when the Message Processor is deactivated after reaching
 max-delivery-attempts. In that sequence you may implement DLC pattern.

 Also I understand that your requirement is valid, and you may create a
 public jira to track that. We may incorporate it in to the product in a
 future release.



 [1] https://docs.wso2.com/display/ESB481/Message+Forwarding+Processor



 Thanks & Regards,

 On Wed, Sep 9, 2015 at 4:07 PM, John Hawkins  wrote:

> Hi Ravindra,
> I'm thinking about this a lot now
> max.delivery.attempts is not documented anywhere nor is it in the
> MessageProcessor wizard (but it is in a few JIRA's and blog entries). Is
> this deliberate do you know - are we hiding it for some reason?
>
> Personally I would expect some kind of 'retries fail' sequence to be
> an optional thing I can set. Then I could do what I wanted with the 
> message
> and the MessageProcessor can continue. Are you aware of any thoughts like
> this at all? If not then I think I need to create a JIRA to at least
> document this feature as-is.
>
> cheers,
> john.
>
> John Hawkins
> Director: Solutions Architecture
>
>
> On Wed, Sep 9, 2015 at 11:03 AM, Ravindra Ranwala 
> wrote:
>
>> Hi John,
>>
>> There is no DLC behaviour after reaching the max-retry-count at the
>> moment.
>>
>>
>> Thanks & Regards,
>>
>> On Wed, Sep 9, 2015 at 3:23 PM, John Hawkins  wrote:
>>
>>> Another question - is there no Dead Letter Queue behaviour then if a
>>> message fails to get sent after max_retry is done?
>>>
>>> John Hawkins
>>> Director: Solutions Architecture
>>>
>>>
>>> On Thu, Sep 3, 2015 at 4:41 PM, Ravindra Ranwala 
>>> wrote:
>>>
 Hi John,

 The Cron expression in MP is used to create firing schedules such
 as "At 8:00am every Monday through Friday" [1]. If it is set the MP 
 will
 run according to that. Otherwise MP will poll the queue with the 
 specified
 interval value continuously.

 Also the MP has a parameter called max_delivery_attempts (defaults
 to 4), which defines the maximum retry attempts in case of a failure 
 in end
 point. By default if the MP could not send the message to the end point
 after this number of retry count, it deactivates itself. But that 
 message
 remains in the queue. After that you have to activate the MP 
 explicitly to
 make the next schedule to be effective. Otherwise it will remain
 deactivated.

 If you need to override the above behaviour, you need to enable
 max-delivery-drop parameter, so that if the MP could not send the 
 message
 after this number of attempts, it merely drops the message and 
 continues.
 Here you loose the message if the endpoint is down.


 [1]
 http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger


 Thanks & Regards,

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[KasunG Gajasinghe]

Closed the staging repo as requested by Jaggery team. Please find the url -
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/

On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera  wrote:

> will release with today.
>
> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando 
> wrote:
>
>> Thanks Hasintha for pointing this out.
>>
>> @Manu, UES team, would you be able to do another release with the above
>> fix?
>>
>> On 11 September 2015 at 12:04, Hasintha Indrajee 
>> wrote:
>>
>>> The issue with jaggery-extension release was referring and old pom as
>>> parent pom [1]. You need to update it into a new version of jaggery-parent
>>> pom  which is released with wss4j version upgrade.
>>>
>>> [1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>>
>>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando 
>>> wrote:
>>>
 Hi all,

 Thanks for the quick turnaround and releasing the required repo
 quickly. Appreciate your support very much!

 Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing
 wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the
 artifact packed inside the plugins folder in the zip at [1].

 Can you check why the old version is still getting packed and provide a
 release with the fixes? I think there is an issue in how the wss4j
 dependency has been specified. It is not there in the dependencyManagement
 section of the top level pom, but has been specified as a dependency
 without versions in child level poms. Also I could not find any place where
 the 'wss4j.osgi.version' seems to be used. Can you check on these issues
 and fix it so that the proper jar is packed if needed (or drop the jar
 altogether from the feature if possible) ?

 [1]
 http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/

 Thanks,
 Lasantha

 On 10 September 2015 at 19:58, KasunG Gajasinghe 
 wrote:

>
> Released the repo from staging.
>
> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena 
> wrote:
>
>> Hi all,
>>
>> We have prepared the release steps for jagggery-extensions 1.4.1.
>> Builder team please close the repo and release jagggery-extensions
>> 1.4.1.
>>
>> Thanks!
>> -Chanaka
>>
>> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando > > wrote:
>>
>>> Hi Manu, UES team,
>>>
>>> It seems this is fixed in jaggery 0.11.0. If we move our dashboard
>>> dependency version from 0.10.3 to 0.11.0, will this affect our current
>>> dashboard functionality? (Any API changes, functionality changes of
>>> existing features)
>>>
>>> Also, as per the thread started by KasunG, it seems this issue is
>>> there in jaggery-extensions as well. So can we get a release for
>>> jaggery-extensions and jaggery (if upgrade does not work) with the 
>>> proper
>>> fix?
>>>
>>> We are currently planning to put an RC release of CEP tomorrow and
>>> currently we are blocked on releasing the dependent repos because of 
>>> this.
>>> Would appreciate a response at your earliest please.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 10 September 2015 at 15:17, Lasantha Fernando 
>>> wrote:
>>>
 Thanks Harsha anyway for the suggestion.. :-)

 After removing the older wss4j from the bundles.info of the pack
 as suggested by Gokul, the pack is starting fine. So I guess we will 
 have
 to fix the jaggery features properly to resolve this issue.

 Thanks,
 Lasantha

 On 10 September 2015 at 15:03, Harsha Thirimanna 
 wrote:

> Sorry , didn't see your reply. :)
> On Sep 10, 2015 3:02 PM, "Harsha Thirimanna" 
> wrote:
>
>> Hi Lasantha,
>>
>> Can't we enable logs and check whether which component will take
>> more time
>> OR
>> do profiling to get the root cause.
>> On Sep 10, 2015 2:34 PM, "Gokul Balakrishnan" 
>> wrote:
>>
>>> We're facing the same issue in the later DAS packs, where the
>>> pack startup is much slower after the upgrade. This is apparent 
>>> under Java
>>> 8 as well (1.8.0_51).
>>>
>>> Thanks,
>>>
>>> On 10 September 2015 at 14:29, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Hi Devs,

 For product-cep, after upgrading the dependent carbon identity
 repo version from 4.5.5 to 4.5.6, the server startup has become 
 

Re: [Dev] Removing RMSequence mediator from Developer Studio 3.8.0 ESB Palette

[Awanthika Senarath]

Is there anyway that we can support older ESB versions with the new
release? since we are giving many bug fixes with 3.8.0 it is better if we
can support older versions as well.

Just My opinion though..

Regards
Awanthika

Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791



On Fri, Sep 11, 2015 at 2:02 PM, Rajeevan Vimalanathan 
wrote:

> Hi,
>
> We have observed that RMSequence mediator has been removed from ESB 4.8.1.
> We also planning to remove that from ESB palette as well from Developer
> Studio 3.8.0 since synapse libraries have been updated accordingly.
> Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
> Developer Studio 3.8.0? These features won't be supported anymore. In that
> case, can we suggest the user to use Developer Studio 3.7.1 which is a
> older version? Please appreciate your thoughts on this.
>
> Thanks,
> Rajeevan
>
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* 
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Configuration issue in permission tree - MB

[Dilini Gunatilake]

Hi All,

This is regarding a known issue of the permission tree. When you try to
configure permissions of a Role in Management Console, we can either select
the parent and enable all the permissions under the parent or deselect the
parent and enable only few permissions under the parent. In this case, even
it is possible to select only few permissions in the UI, it does not
apply.

For example, in Message Broker (MB), there are permissions under Queues to
Add, Browse, Delete and Purge queues. If I want to allow a user only to Add
and Browse queues, I will have to deselect Queue parent element and select
only Add and Browse child elements. After applying this, the user will not
be able to access the entire Queue section, not only Purge and Delete
functions.

I have also raised an issue in JIRA [1]. Can you please explain how to
achieve the above mentioned scenario in MB?

[1] https://wso2.org/jira/browse/IDENTITY-3573

Thank you.

Regards,

-- 

*Dilini GunatilakeSoftware Engineer - QA Team*
Mobile : +94 (0) 771 162518
dili...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing RMSequence mediator from Developer Studio 3.8.0 ESB Palette

[Jasintha Dasanayake]

 only problem case is if user  waiting for a fix which will be coming with
this release but that user may use older ESB version , but any way now we
have to remove this , we have to educate  users via the documentations

Thanks and Regards
/Jasintha

On Fri, Sep 11, 2015 at 3:09 PM, Harshana Eranga Martin <
harshan...@gmail.com> wrote:

> Hi Rajeevan,
>
> In that case you may recommend to use an older stable version of DevS such
> as DevS 3.7.0 or 3.7.1 since that supports full feature set of ESB 4.8.0.
>
> Thanks and Regards,
> Harshana
>
>
> On Friday, September 11, 2015, Rajeevan Vimalanathan 
> wrote:
>
>> Hi,
>>
>> We have observed that RMSequence mediator has been removed from ESB
>> 4.8.1. We also planning to remove that from ESB palette as well from
>> Developer Studio 3.8.0 since synapse libraries have been updated
>> accordingly.
>> Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
>> Developer Studio 3.8.0? These features won't be supported anymore. In that
>> case, can we suggest the user to use Developer Studio 3.7.1 which is a
>> older version? Please appreciate your thoughts on this.
>>
>> Thanks,
>> Rajeevan
>>
>> --
>> Vimalanathan Rajeevan
>> Software Engineer,
>> WSO2, Inc. *http://wso2.com* 
>> Lean.Enterprise.Middleware
>>
>> Mobile:
>> *+94 773090875 <%2B94%20773090875>*
>> LinkedIn:
>> *https://www.linkedin.com/in/RajeevanVimalanathan
>> *
>>
>
>
> --
> Sent from Gmail Mobile for IPhone
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Jasintha Dasanayake*

*Senior Software EngineerWSO2 Inc. | http://wso2.com lean
. enterprise . middleware*


*mobile :- 0711368118*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Selvaratnam Uthaiyashankar]

See, there are nothing called intermittent issue. Just wrong way of doing
stuff :)

On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham 
wrote:

> Hi Shankar,
>
> I went through the log and noticed that in the ServerRestartTestCase, it
> sends a command to restart the server and waits for 15 seconds and
> proceeds. If in case the server takes longer time then there is an issue.
> Therefore I added the check to wait for the http port to be closed (or wait
> for 30 seconds - This is for the server to shutdown) and then use the util
> provided by the automation team to check if the port it open (this is to
> check if the port is open). Thanks Nuwan for the help.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>>
>>
>> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Shankar,
>>>
>>> It seems to be another server was accessing the h2 database.
>>>
>>
>>
>> How it is possible? It can't be intermittent.. May be we are shutting
>> down / killing the server in one test case and without waiting for the
>> server to stop fully, starting the server in another test case. So,
>> depending on the time, sometime it will work and sometime it will not work.
>> Is that the case?
>>
>>
>>
>>> I am looking into the CarbonTestServerManager class which is used to
>>> start the servers.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 Folks, intermittent issues are the serious problem. We can't just leave
 it with intermittent issues. Please track and see what was the cause?
 database locked by another process means, two servers are running at the
 same time?

 On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi all,
>
> I was able to build the Kernel 4.4.x branch successfully. As Supun
> mentioned this looks like an intermittent issue. I will look into
> this further and update this thread.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Supun,
>>
>> I will look into this. Just now triggered a build in openstack.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
>> wrote:
>>
>>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>>> test method fails saying below,
>>>
>>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x branch.
>>> fyi, I built 4.4.x last night with all tests and build passed for
>>> me. May be this is intermittent.
>>>
>>> INFO  
>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - 
>>> [2015-09-11 02:04:44,020] FATAL 
>>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to create 
>>> database tables for registry resource store. Database may be already in 
>>> use: "Locked by another process". Possible solutions: close all other 
>>> connection(s); use the server mode; SQL 
>>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b [90020-140] 
>>> (Sanitized)
>>> INFO  
>>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - 
>>> org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked 
>>> by another process". Possible solutions: close all other connection(s); 
>>> use the server mode; SQL statement:
>>>
>>>
>>>
>>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/
>>>
>>>
>>>
>>>
>>> On Fri, Sep 11, 2015 at 7:47 AM,  wrote:
>>>
 See 


>>>
>>>
>>> --
>>> Supun Malinga,
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> http://wso2.com
>>> email: sup...@wso2.com 
>>> mobile: +94 (0)71 56 91 321
>>>
>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 S.Uthaiyashankar
 VP Engineering
 WSO2 Inc.
 http://wso2.com/ - "lean . enterprise . middleware"

 Phone: +94 714897591

>>>
>>>
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: 

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

will release with today.

On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando 
wrote:

> Thanks Hasintha for pointing this out.
>
> @Manu, UES team, would you be able to do another release with the above
> fix?
>
> On 11 September 2015 at 12:04, Hasintha Indrajee 
> wrote:
>
>> The issue with jaggery-extension release was referring and old pom as
>> parent pom [1]. You need to update it into a new version of jaggery-parent
>> pom  which is released with wss4j version upgrade.
>>
>> [1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>
>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando 
>> wrote:
>>
>>> Hi all,
>>>
>>> Thanks for the quick turnaround and releasing the required repo quickly.
>>> Appreciate your support very much!
>>>
>>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing
>>> wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the
>>> artifact packed inside the plugins folder in the zip at [1].
>>>
>>> Can you check why the old version is still getting packed and provide a
>>> release with the fixes? I think there is an issue in how the wss4j
>>> dependency has been specified. It is not there in the dependencyManagement
>>> section of the top level pom, but has been specified as a dependency
>>> without versions in child level poms. Also I could not find any place where
>>> the 'wss4j.osgi.version' seems to be used. Can you check on these issues
>>> and fix it so that the proper jar is packed if needed (or drop the jar
>>> altogether from the feature if possible) ?
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 10 September 2015 at 19:58, KasunG Gajasinghe 
>>> wrote:
>>>

 Released the repo from staging.

 On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena 
 wrote:

> Hi all,
>
> We have prepared the release steps for jagggery-extensions 1.4.1.
> Builder team please close the repo and release jagggery-extensions
> 1.4.1.
>
> Thanks!
> -Chanaka
>
> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando 
> wrote:
>
>> Hi Manu, UES team,
>>
>> It seems this is fixed in jaggery 0.11.0. If we move our dashboard
>> dependency version from 0.10.3 to 0.11.0, will this affect our current
>> dashboard functionality? (Any API changes, functionality changes of
>> existing features)
>>
>> Also, as per the thread started by KasunG, it seems this issue is
>> there in jaggery-extensions as well. So can we get a release for
>> jaggery-extensions and jaggery (if upgrade does not work) with the proper
>> fix?
>>
>> We are currently planning to put an RC release of CEP tomorrow and
>> currently we are blocked on releasing the dependent repos because of 
>> this.
>> Would appreciate a response at your earliest please.
>>
>> Thanks,
>> Lasantha
>>
>> On 10 September 2015 at 15:17, Lasantha Fernando 
>> wrote:
>>
>>> Thanks Harsha anyway for the suggestion.. :-)
>>>
>>> After removing the older wss4j from the bundles.info of the pack as
>>> suggested by Gokul, the pack is starting fine. So I guess we will have 
>>> to
>>> fix the jaggery features properly to resolve this issue.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 10 September 2015 at 15:03, Harsha Thirimanna 
>>> wrote:
>>>
 Sorry , didn't see your reply. :)
 On Sep 10, 2015 3:02 PM, "Harsha Thirimanna" 
 wrote:

> Hi Lasantha,
>
> Can't we enable logs and check whether which component will take
> more time
> OR
> do profiling to get the root cause.
> On Sep 10, 2015 2:34 PM, "Gokul Balakrishnan" 
> wrote:
>
>> We're facing the same issue in the later DAS packs, where the
>> pack startup is much slower after the upgrade. This is apparent 
>> under Java
>> 8 as well (1.8.0_51).
>>
>> Thanks,
>>
>> On 10 September 2015 at 14:29, Lasantha Fernando <
>> lasan...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> For product-cep, after upgrading the dependent carbon identity
>>> repo version from 4.5.5 to 4.5.6, the server startup has become 
>>> extremely
>>> slow. If you downgrade this particular identity version back to 
>>> 4.5.5, it
>>> starts normally.
>>>
>>> The difference is from around 24-30 sec startup time with
>>> identity 4.5.5 and 70-80 sec startup time for identity 4.5.6 with 
>>> no other
>>> changes.
>>>
>>> 

[Dev] Removing RMSequence mediator from Developer Studio 3.8.0 ESB Palette

[Rajeevan Vimalanathan]

Hi,

We have observed that RMSequence mediator has been removed from ESB 4.8.1.
We also planning to remove that from ESB palette as well from Developer
Studio 3.8.0 since synapse libraries have been updated accordingly.
Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
Developer Studio 3.8.0? These features won't be supported anymore. In that
case, can we suggest the user to use Developer Studio 3.7.1 which is a
older version? Please appreciate your thoughts on this.

Thanks,
Rajeevan

-- 
Vimalanathan Rajeevan
Software Engineer,
WSO2, Inc. *http://wso2.com* 
Lean.Enterprise.Middleware

Mobile:
*+94 773090875*
LinkedIn:
*https://www.linkedin.com/in/RajeevanVimalanathan
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Timeout error when creating APIs using APIM 1.9.0 REST API

[Nuwan Wimalasekara]

Hi Udara,

In APIM integration test, HTTP endpoint is used to call the
RestAPI(Publisher and Store) and It is working fine without any issue. This
should work

Thanks,
Nuwanw

On Fri, Sep 11, 2015 at 9:41 AM, Nuwan Dias  wrote:

> They run on HTTPS only. If you send an http request, it automatically
> redirects to https.
>
> On Fri, Sep 11, 2015 at 8:46 AM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> I could create APIs by changing to port 9443 and protocol to HTTPS.
>> However why does REST APIs runs on HTTP?
>>
>> curl -X POST -c cookies
>> https://localhost:9443/publisher/site/blocks/user/login/ajax/login.jag
>> -d 'action=login=admin=admin' -k
>>
>>
>> curl -b cookies -k
>> https://localhost:9443/publisher/site/blocks/item-add/ajax/add.jag -d
>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>> a phone
>> number=phone,mobile,multimedia=nonsecured===Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>> x...@ee.com=xx=g...@ww.com"
>> -d'endpoint_config={"production_endpoints":{"url":"
>> http://ws.cdyne.com/phoneverify/phoneverify.asmx","config":null},"endpoint_type":"http
>> "}';
>>
>> On Fri, Sep 11, 2015 at 4:18 AM, Udara Liyanage  wrote:
>>
>>> Hi,
>>>
>>> I got this error while trying the sample Add API command mentioned in
>>> the doc . No
>>> backend error is displayed, any idea?
>>>
>>>
>>>  $ curl -X POST -c cookies
>>> http://localhost:9763/publisher/site/blocks/user/login/ajax/login.jag
>>> -d 'action=login=admin=admin'
>>> {"error" : false}
>>>
>>>
>>>  $ curl -X POST -b cookies
>>> http://localhost:9763/publisher/site/blocks/item-add/ajax/add.jag -d
>>> "action=addAPI=PhoneVerification=/phoneverify=1.0.0=public==Verify
>>> a phone
>>> number=phone,mobile,multimedia=nonsecured=Gold,Bronze_checked=http_checked=https=0=GET=Application=Unlimited=/*_version_checked=default_version=xx=
>>> x...@ee.com=xx=g...@ww.com"
>>> -d'endpoint_config={"production_endpoints":{"url":"
>>> http://ws.cdyne.com/phoneverify/phoneverify.asmx
>>> ","config":null},"endpoint_type":"http"}';
>>> {"error" : true, "message" : "*timeout*"}
>>>
>>> --
>>>
>>> Udara Liyanage
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean. enterprise. middleware
>>>
>>> web: http://udaraliyanage.wordpress.com
>>> phone: +94 71 443 6897
>>>
>>
>>
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> web: http://udaraliyanage.wordpress.com
>> phone: +94 71 443 6897
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Wimalasekara
Senior Software Engineer - Test Automation
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

phone: +94 71 668 4620
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Removing RMSequence mediator from Developer Studio 3.8.0 ESB Palette

[Harshana Eranga Martin]

Hi Rajeevan,

In that case you may recommend to use an older stable version of DevS such
as DevS 3.7.0 or 3.7.1 since that supports full feature set of ESB 4.8.0.

Thanks and Regards,
Harshana

On Friday, September 11, 2015, Rajeevan Vimalanathan 
wrote:

> Hi,
>
> We have observed that RMSequence mediator has been removed from ESB 4.8.1.
> We also planning to remove that from ESB palette as well from Developer
> Studio 3.8.0 since synapse libraries have been updated accordingly.
> Here our concern is what if a user wants to develop ESB 4.8.0 stuff with
> Developer Studio 3.8.0? These features won't be supported anymore. In that
> case, can we suggest the user to use Developer Studio 3.7.1 which is a
> older version? Please appreciate your thoughts on this.
>
> Thanks,
> Rajeevan
>
> --
> Vimalanathan Rajeevan
> Software Engineer,
> WSO2, Inc. *http://wso2.com* 
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> *
>


-- 
Sent from Gmail Mobile for IPhone
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ES][Doc] Adding a new sample Artifact of an Asset Type(RXT) in Enterprise Store

[Mariangela Hills]

I created a JIRA [1] to track this task.

[1] https://wso2.org/jira/browse/DOCUMENTATION-2366

Regards,
Mariangela


*Mariangela Hills*
Senior Technical Writer - WSO2, Inc. http://wso2.com
Committer and PMC member - Apache Stratos
email:mariang...@wso2.com | mobile: +94 773 500185

On Fri, Sep 11, 2015 at 10:25 AM, Mariangela Hills 
wrote:

> Thanks, Shabir! I will add this to the docs!
>
> Regards,
> Mariangela
>
>
> *Mariangela Hills*
> Senior Technical Writer - WSO2, Inc. http://wso2.com
> Committer and PMC member - Apache Stratos
> email:mariang...@wso2.com | mobile: +94 773 500185
>
> On Thu, Sep 10, 2015 at 10:47 PM, Shabir Mohamed  wrote:
>
>> Also to be added to *Common Mistakes:*
>>
>>
>>- The *"name" *attribute and the *"overview_name"* attribute, both
>>needs to have the same Value, (Ex: 'RaspberryPi' & 'Raspberry Pi' will not
>>work). *"name"* is the Artifact-Name and "*overview_name*" is the
>>value used when creating the resource path in the registry.
>>
>>
>> -
>> *Shabir Mohamed*
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> Email: sha...@wso2.com 
>> Mobile: +94 77 3516019 | +94 71 6583393
>>
>> On Thu, Sep 10, 2015 at 9:10 PM, Shabir Mohamed  wrote:
>>
>>> Hi,
>>>
>>> I have been trying to do $subject and found no relevant documentation.
>>> Hence, I backtracked the path as to how the existing sample-artifacts of
>>> the default asset-types (i.e.: gadget & site) are added when running the
>>> WSO2 - Enterprise Store 2.0.
>>>
>>> *As per my study these are the necessary steps required to do $subject:*
>>>
>>> Say the Asset-type for which we want to add a sample artifact has its
>>> *"RXT"* name as *"device.rxt". **(sample txt attached in the email)*
>>>
>>> 1. *The sample artifacts per asset-type are found at path:*
>>>
>>>-
>>>
>>> */repository/deployment/server/jaggeryapps/publisher/samples/assets*
>>>- Create a folder by the plural-name of the asset-type(rxt) in this
>>>path. In this example we make a folder by the name *"devices"*.
>>>- All sample/default artifacts of asset-type *"device" *shall go
>>>into this folder.
>>>
>>> 2. The parent installation script - *"install.js"* - for all samples is
>>> found at the above mentioned path. Any *"install.js"* scripts found
>>> within sub-folders *(ex: devices, gadgets & sites)* of this path will
>>> over-ride the parent script to perform any specific operations relavant to
>>> that asset-type.
>>>
>>>- copy the sample asset-specific *"install.js"** (attached with this
>>>email)* into the folder created in the previous step.
>>>- search and change the following tags appropriately in the copied
>>>script:
>>>
>>>   ** : LifeCycle definition to which
>>> the asset-type *(in this example "device") *needs to be attached to *(ex:
>>> DeviceLifeCycle)*. Should be one of the lifecycle definitions found
>>> inside:
>>> */repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles/*
>>>   ** : The *"rxt"* name of the
>>> asset-type for which the samples are to be made *(in this
>>> example "device"). *
>>>
>>>- Save and close the *"install.js"* script.
>>>
>>> 3. Create a folder by the name of the sample-artifact inside the
>>> asset-specific-parent-folder created in Step 1. In this example lets call
>>> our sample artifact of asset-type *"device"* as *"firealarm"*. We can
>>> continue adding any number of folders *per artifact* of the asset-type *(ex:
>>> firearm, raspberryPi, arduino & etc)*. Artifact specific details go
>>> into these folders.
>>>
>>> *The folder structure
>>> at- /repository/deployment/server/jaggeryapps/publisher/samples 
>>> should
>>> look as follows:*
>>>
>>> *.*
>>>
>>> *└── samples*
>>>
>>> *└── assets*
>>>
>>> *├── devices*
>>>
>>> *│   ├── firealarm*
>>>
>>> *│   │   ├── banner.png*
>>>
>>> *│   │   ├── device.json*
>>>
>>> *│   │   └── thumbnail.png*
>>>
>>> *│   └── install.js*
>>>
>>> *└── install.js*
>>>
>>>
>>> 4. Now we have to specify the asset specific attributes to be used when
>>> creating our sample (firealarm) artifact. These details are provided as a 
>>> *"json"
>>> *file with the same name as the asset-type/rxt *(.json)*.
>>>
>>>
>>>- In our example this is found inside the *"firealarm"* artifact
>>>folder as *"device.json"*. For every additional artifact-folder that
>>>is declared, there will be a corresponding *"device.json" *file with
>>>relevant attribute details. *(The one used for declaring "firealarm"
>>>artifact is attached)*
>>>
>>>
>>>- Additionally, any images used for thumbnail & banner views of the
>>>artifact in the store also need to go into the artifact specific folder.
>>>The path to these images need to be given appropriately in the 
>>> *.json
>>>*file. (See attached sample 

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Niranjan Karunanandham]

Hi Shankar,

I went through the log and noticed that in the ServerRestartTestCase, it
sends a command to restart the server and waits for 15 seconds and
proceeds. If in case the server takes longer time then there is an issue.
Therefore I added the check to wait for the http port to be closed (or wait
for 30 seconds - This is for the server to shutdown) and then use the util
provided by the automation team to check if the port it open (this is to
check if the port is open). Thanks Nuwan for the help.

Regards,
Nira

On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

>
>
> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Shankar,
>>
>> It seems to be another server was accessing the h2 database.
>>
>
>
> How it is possible? It can't be intermittent.. May be we are shutting down
> / killing the server in one test case and without waiting for the server to
> stop fully, starting the server in another test case. So, depending on the
> time, sometime it will work and sometime it will not work. Is that the
> case?
>
>
>
>> I am looking into the CarbonTestServerManager class which is used to
>> start the servers.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Folks, intermittent issues are the serious problem. We can't just leave
>>> it with intermittent issues. Please track and see what was the cause?
>>> database locked by another process means, two servers are running at the
>>> same time?
>>>
>>> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi all,

 I was able to build the Kernel 4.4.x branch successfully. As Supun
 mentioned this looks like an intermittent issue. I will look into this
 further and update this thread.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Supun,
>
> I will look into this. Just now triggered a build in openstack.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
> wrote:
>
>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>> test method fails saying below,
>>
>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x branch.
>> fyi, I built 4.4.x last night with all tests and build passed for me.
>> May be this is intermittent.
>>
>> INFO  
>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - 
>> [2015-09-11 02:04:44,020] FATAL 
>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to create 
>> database tables for registry resource store. Database may be already in 
>> use: "Locked by another process". Possible solutions: close all other 
>> connection(s); use the server mode; SQL 
>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b [90020-140] 
>> (Sanitized)
>> INFO  
>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] - 
>> org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by 
>> another process". Possible solutions: close all other connection(s); use 
>> the server mode; SQL statement:
>>
>>
>>
>> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/
>>
>>
>>
>>
>> On Fri, Sep 11, 2015 at 7:47 AM,  wrote:
>>
>>> See 
>>>
>>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Senior Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> email: sup...@wso2.com 
>> mobile: +94 (0)71 56 91 321
>>
>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



 --

 *Niranjan Karunanandham*
 Senior Software Engineer - WSO2 Inc.
 WSO2 Inc.: http://www.wso2.com

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> S.Uthaiyashankar
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com/ - "lean . enterprise . middleware"
>>>
>>> Phone: +94 714897591
>>>
>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> S.Uthaiyashankar
> VP Engineering
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591
>



-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Selvaratnam Uthaiyashankar]

Even waiting for 30 seconds might not work. Can we loop with a sleep and
see whether the process is not there and proceed? Port will be closed
immediately, but the process might still run AFAIK.

On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

> See, there are nothing called intermittent issue. Just wrong way of doing
> stuff :)
>
> On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Shankar,
>>
>> I went through the log and noticed that in the ServerRestartTestCase, it
>> sends a command to restart the server and waits for 15 seconds and
>> proceeds. If in case the server takes longer time then there is an issue.
>> Therefore I added the check to wait for the http port to be closed (or wait
>> for 30 seconds - This is for the server to shutdown) and then use the util
>> provided by the automation team to check if the port it open (this is to
>> check if the port is open). Thanks Nuwan for the help.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>>
>>>
>>> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Shankar,

 It seems to be another server was accessing the h2 database.

>>>
>>>
>>> How it is possible? It can't be intermittent.. May be we are shutting
>>> down / killing the server in one test case and without waiting for the
>>> server to stop fully, starting the server in another test case. So,
>>> depending on the time, sometime it will work and sometime it will not work.
>>> Is that the case?
>>>
>>>
>>>
 I am looking into the CarbonTestServerManager class which is used to
 start the servers.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
 shan...@wso2.com> wrote:

> Folks, intermittent issues are the serious problem. We can't just
> leave it with intermittent issues. Please track and see what was the 
> cause?
> database locked by another process means, two servers are running at the
> same time?
>
> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi all,
>>
>> I was able to build the Kernel 4.4.x branch successfully. As Supun
>> mentioned this looks like an intermittent issue. I will look into
>> this further and update this thread.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Supun,
>>>
>>> I will look into this. Just now triggered a build in openstack.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
>>> wrote:
>>>
 org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
 test method fails saying below,

 Aruna/ Niranjan can one of you have a look ? This is 4.4.x branch.
 fyi, I built 4.4.x last night with all tests and build passed for
 me. May be this is intermittent.

 INFO  
 [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] 
 - [2015-09-11 02:04:44,020] FATAL 
 {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to create 
 database tables for registry resource store. Database may be already 
 in use: "Locked by another process". Possible solutions: close all 
 other connection(s); use the server mode; SQL 
 statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b 
 [90020-140] (Sanitized)
 INFO  
 [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] 
 - org.h2.jdbc.JdbcSQLException: Database may be already in use: 
 "Locked by another process". Possible solutions: close all other 
 connection(s); use the server mode; SQL statement:



 https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/




 On Fri, Sep 11, 2015 at 7:47 AM,  wrote:

> See 
>
>


 --
 Supun Malinga,

 Senior Software Engineer,
 WSO2 Inc.
 http://wso2.com
 email: sup...@wso2.com 
 mobile: +94 (0)71 56 91 321

>>>
>>>
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>> 

Re: [Dev] Extract year from timestamp with Spark in DAS 3.0.0

[Jorge]

the question in SO:
http://stackoverflow.com/questions/32531169/extract-year-from-timestamp-with-spark-sql-in-wso2-das

Jorge.

2015-09-10 12:32 GMT-04:00 Jorge :

> Hi folks,
>
> In my hive scripts if I want to extract the year from timestamp I used
> this:
>
> year(from_unixtime(cast(payload_fecha/1000 as BIGINT),'-MM-dd
> HH:mm:ss.SSS' )) as year
>
> now I testing the new DAS snapshot and I want to do the same but I cannot
> use *from_unixtime*.
> So how can I do the same in spark SQL?
>
> Regards,
>Jorge.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Lasantha Fernando]

When the jaggery versions are downgraded, it starts functioning properly
without any issue, albeit with the startup delay issue.

If we can get releases of jaggery and jaggery-extensions for 0.10.x and
1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
resolve all the issues we are currently facing.

Thanks,
Lasantha

On 11 September 2015 at 15:45, Lasantha Fernando  wrote:

> Hi Manu,
>
> Thanks for the quick turnaround. This particular version upgrades the
> proper wss4j version and the startup issue gets fixed. But unfortunately,
> when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
> 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.
>
> When creating a single dashboard, about 20 additional dashboards with the
> same name get created in our dashboards ui. See attached screenshot.
>
> @Manu, UES team, sorry to trouble you guys again, but would you guys be
> able to release new repos for jaggery-0.10.x and jaggery-extensions-1.3.x.
> It seems the upgrade from 0.10.x to 0.11.0 doesn't work and we've already
> tested the dashboard extensively with the older jaggery versions.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 14:25, KasunG Gajasinghe  wrote:
>
>>
>> Closed the staging repo as requested by Jaggery team. Please find the url
>> - http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>>
>> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera  wrote:
>>
>>> will release with today.
>>>
>>> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando 
>>> wrote:
>>>
 Thanks Hasintha for pointing this out.

 @Manu, UES team, would you be able to do another release with the above
 fix?

 On 11 September 2015 at 12:04, Hasintha Indrajee 
 wrote:

> The issue with jaggery-extension release was referring and old pom as
> parent pom [1]. You need to update it into a new version of jaggery-parent
> pom  which is released with wss4j version upgrade.
>
> [1] https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>
> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando 
> wrote:
>
>> Hi all,
>>
>> Thanks for the quick turnaround and releasing the required repo
>> quickly. Appreciate your support very much!
>>
>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still packing
>> wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. Please see the
>> artifact packed inside the plugins folder in the zip at [1].
>>
>> Can you check why the old version is still getting packed and provide
>> a release with the fixes? I think there is an issue in how the wss4j
>> dependency has been specified. It is not there in the 
>> dependencyManagement
>> section of the top level pom, but has been specified as a dependency
>> without versions in child level poms. Also I could not find any place 
>> where
>> the 'wss4j.osgi.version' seems to be used. Can you check on these issues
>> and fix it so that the proper jar is packed if needed (or drop the jar
>> altogether from the feature if possible) ?
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>
>> Thanks,
>> Lasantha
>>
>> On 10 September 2015 at 19:58, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>> Released the repo from staging.
>>>
>>> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena 
>>> wrote:
>>>
 Hi all,

 We have prepared the release steps for jagggery-extensions 1.4.1.
 Builder team please close the repo and release jagggery-extensions
 1.4.1.

 Thanks!
 -Chanaka

 On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando <
 lasan...@wso2.com> wrote:

> Hi Manu, UES team,
>
> It seems this is fixed in jaggery 0.11.0. If we move our dashboard
> dependency version from 0.10.3 to 0.11.0, will this affect our current
> dashboard functionality? (Any API changes, functionality changes of
> existing features)
>
> Also, as per the thread started by KasunG, it seems this issue is
> there in jaggery-extensions as well. So can we get a release for
> jaggery-extensions and jaggery (if upgrade does not work) with the 
> proper
> fix?
>
> We are currently planning to put an RC release of CEP tomorrow and
> currently we are blocked on releasing the dependent repos because of 
> this.
> Would appreciate a response at your earliest please.
>
> Thanks,
> Lasantha
>
> On 10 September 2015 at 15:17, Lasantha Fernando <
> lasan...@wso2.com> 

Re: [Dev] [DEV] Clarification on App Cloud- Built-in Editor has popup NPE for git->commit

[Amila Maha Arachchi]

If you checked the "Events" tab in code editor when you saw that exception,
some more information could have been revealed. If you come across this
again, please check the events tab too.

On Fri, Sep 11, 2015 at 10:46 AM, Kavitha Subramaniyam 
wrote:

> Hi Manjula,
>
> I was tried this by directly accessing cloud.wso2.com
>  and was working on front end, therefore couldn't
> access log/backend.
> As you mentioned I will clone project to my local machine and check, and
> share the tenant domain if this is happen on that setup as well.
>
>
> Thanks & Kind regards,
>
>
> On Fri, Sep 11, 2015 at 8:31 AM, Manjula Rathnayake 
> wrote:
>
>> Hi Kavitha,
>>
>> This is the first time I see this issue. If you clone the project to your
>> local machine and try to commit and push, does it pass?
>>
>> Please provide the tenant domain to investigate further.
>>
>> thank you.
>>
>>
>> On Thu, Sep 10, 2015 at 4:59 PM, Kavitha Subramaniyam 
>> wrote:
>>
>>> Hi team,
>>>
>>> I have been created a test java web application on App Cloud and by
>>> using Built-in Editor have made some changes at index.jsp of
>>> testjava_project (followed the tutorial steps). After Git-> Add to index
>>> and when do the Git-> Commit it has given NPE and changes are not affected.
>>>
>>> Appreciate if anyone help me to find the cause..
>>>
>>> PFA for screen shot.
>>>
>>>
>>>
>>> --
>>> Kavitha.S
>>> *Software Engineer -QA*
>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>>> kavi...@wso2.com 
>>>
>>
>>
>>
>> --
>> Manjula Rathnayaka
>> Associate Technical Lead
>> WSO2, Inc.
>> Mobile:+94 77 743 1987
>>
>
>
>
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting error while installing features to IS 5.0.0 pack using pom

[Malintha Adikari]

attaching POM file used to install key manager features.

On Thu, Sep 10, 2015 at 10:56 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi Malintha,
>
> Shall we try to installed the feature using osgi console. You can refer
> [1]. Automation of this approach would be bit tricky as we need to maintain
> another script to do all these command execution.
>
> [1] http://wiki.eclipse.org/Equinox_p2_Console_Users_Guide
>
> Thanks,
> Krishantha.
>
> On Wed, Sep 9, 2015 at 10:46 PM, Malintha Adikari 
> wrote:
>
>> Thank you Lasitha for infomation
>>
>> On Wed, Sep 9, 2015 at 10:26 PM, Malintha Adikari 
>> wrote:
>>
>>> Adding Krishantha
>>> On Sep 9, 2015 6:30 PM, "Lasitha Wattaladeniya" 
>>> wrote:
>>>
 Hi Malintha,

 Apparently there's a bug, it's reported in this jira [1].

 [1]. https://wso2.org/jira/browse/CARBON-15195

 On Wed, Sep 9, 2015 at 3:59 PM, Malintha Adikari 
 wrote:

> Hi,
>
> I am installing keymanager feature to IS 5.0.0 pack using pom file. I
> am getting version conflicts for some features.
> When I try to install
>
> Ex:
> 
>org.wso2.carbon.registry.contentsearch.server.feature.group
>4.2.2
> 
>
> I am getting following error
>
> Installing org.wso2.carbon.xfer.feature.group 4.2.0.
> Installing org.wso2.carbon.stratos.deployment.feature.group 2.2.1.
> Installing org.wso2.carbon.system.statistics.feature.group 4.2.2.
> Installation failed.
> Cannot complete the install because of a conflicting dependency.
>  Software being installed: WSO2 Carbon - Registry Content Search
> Server Feature 4.2.2
> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.2)
>  Software currently installed: WSO2 Carbon - Registry Content Search
> Feature 4.2.1 (org.wso2.carbon.registry.contentsearch.feature.group 4.2.1)
>  Only one of the following can be installed at once:
>   WSO2 Carbon - Registry Content Search Server Feature 4.2.2
> (org.wso2.carbon.registry.contentsearch.server.feature.jar 4.2.2)
>   WSO2 Carbon - Registry Content Search Server Feature 4.2.1
> (org.wso2.carbon.registry.contentsearch.server.feature.jar 4.2.1)
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Content Search Feature 4.2.1
> (org.wso2.carbon.registry.contentsearch.feature.group 4.2.1)
>   To: org.wso2.carbon.registry.contentsearch.server.feature.group
> [4.2.1]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Content Search Server Feature 4.2.1
> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.1)
>   To: org.wso2.carbon.registry.contentsearch.server.feature.jar [4.2.1]
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Registry Content Search Server Feature 4.2.2
> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.2)
>   To: org.wso2.carbon.registry.contentsearch.server.feature.jar [4.2.2]
> Application failed, log file location:
> /root/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1441793612480.log
>
> Seems there is a conflict between existing feature in the carbon pack
> and the new feature to be installed. How can I upgrade a feature ?.
> Appreciate your help on this.
>
> Regards,
> Malintha
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile: +94 71 2312958
> Blog:http://malinthas.blogspot.com
> Page:   http://about.me/malintha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Lasitha Wattaladeniya
 Software Engineer
 WSO2, Inc. | http://wso2.com
 lean. enterprise. middleware

 Mobile : +94719397528
 Blog : techreadme.blogspot.com

>>>
>>
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Krishantha Samaraweera
> Senior Technical Lead - Test Automation
> Mobile: +94 77 7759918
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>



-- 
*Malintha Adikari*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

Mobile: +94 71 2312958
Blog:http://malinthas.blogspot.com
Page:   http://about.me/malintha

http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 

Re: [Dev] Extract year from timestamp with Spark in DAS 3.0.0

[Gimantha Bandara]

Hi Jorge,

You can use Spark UDFs to write a function to extract the year from epoch
time. Please refer to the blog [1] for example implementation of UDFs.

@Niranda, is there any other way to achieve the same?

[1]
http://thanu912.blogspot.com/2015/08/using-user-defined-function-udf-in.html

On Fri, Sep 11, 2015 at 4:07 PM, Jorge  wrote:

> the question in SO:
>
> http://stackoverflow.com/questions/32531169/extract-year-from-timestamp-with-spark-sql-in-wso2-das
>
> Jorge.
>
>
> 2015-09-10 12:32 GMT-04:00 Jorge :
>
>> Hi folks,
>>
>> In my hive scripts if I want to extract the year from timestamp I used
>> this:
>>
>> year(from_unixtime(cast(payload_fecha/1000 as BIGINT),'-MM-dd
>> HH:mm:ss.SSS' )) as year
>>
>> now I testing the new DAS snapshot and I want to do the same but I cannot
>> use *from_unixtime*.
>> So how can I do the same in spark SQL?
>>
>> Regards,
>>Jorge.
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Lasantha Fernando]

Hi Manu,

Tested the CEP pack with the staged artifacts and the functionality is
working fine. Please release the repo from staging.

Thanks,
Lasantha

On 11 September 2015 at 21:10, Manuranga Perera  wrote:

> update http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-084/
> please try and let me know
>
> On Fri, Sep 11, 2015 at 8:00 PM, Manuranga Perera  wrote:
>
>> please try with
>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/
>>
>> On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera  wrote:
>>
>>> please try 1.3.4 version with
>>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
>>>
>>>
>>> On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera  wrote:
>>>
 ok will do. reverting the staging.

 On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
 wrote:

> When the jaggery versions are downgraded, it starts functioning
> properly without any issue, albeit with the startup delay issue.
>
> If we can get releases of jaggery and jaggery-extensions for 0.10.x
> and 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
> resolve all the issues we are currently facing.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 15:45, Lasantha Fernando 
> wrote:
>
>> Hi Manu,
>>
>> Thanks for the quick turnaround. This particular version upgrades the
>> proper wss4j version and the startup issue gets fixed. But unfortunately,
>> when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
>> 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.
>>
>> When creating a single dashboard, about 20 additional dashboards with
>> the same name get created in our dashboards ui. See attached screenshot.
>>
>> @Manu, UES team, sorry to trouble you guys again, but would you guys
>> be able to release new repos for jaggery-0.10.x and
>> jaggery-extensions-1.3.x. It seems the upgrade from 0.10.x to 0.11.0
>> doesn't work and we've already tested the dashboard extensively with the
>> older jaggery versions.
>>
>> Thanks,
>> Lasantha
>>
>> On 11 September 2015 at 14:25, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>> Closed the staging repo as requested by Jaggery team. Please find
>>> the url -
>>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>>>
>>> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
>>> wrote:
>>>
 will release with today.

 On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando <
 lasan...@wso2.com> wrote:

> Thanks Hasintha for pointing this out.
>
> @Manu, UES team, would you be able to do another release with the
> above fix?
>
> On 11 September 2015 at 12:04, Hasintha Indrajee <
> hasin...@wso2.com> wrote:
>
>> The issue with jaggery-extension release was referring and old
>> pom as parent pom [1]. You need to update it into a new version of
>> jaggery-parent pom  which is released with wss4j version upgrade.
>>
>> [1]
>> https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>
>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
>> lasan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> Thanks for the quick turnaround and releasing the required repo
>>> quickly. Appreciate your support very much!
>>>
>>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still
>>> packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
>>> Please
>>> see the artifact packed inside the plugins folder in the zip at [1].
>>>
>>> Can you check why the old version is still getting packed and
>>> provide a release with the fixes? I think there is an issue in how 
>>> the
>>> wss4j dependency has been specified. It is not there in the
>>> dependencyManagement section of the top level pom, but has been 
>>> specified
>>> as a dependency without versions in child level poms. Also I could 
>>> not find
>>> any place where the 'wss4j.osgi.version' seems to be used. Can you 
>>> check on
>>> these issues and fix it so that the proper jar is packed if needed 
>>> (or drop
>>> the jar altogether from the feature if possible) ?
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 10 September 2015 at 19:58, KasunG Gajasinghe <
>>> kas...@wso2.com> wrote:
>>>

Re: [Dev] [AF] "Show More Detail" button in runtime config page takes long time to respond

[Danushka Fernando]

+1 for a button for each property. I thought we already had that.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Fri, Sep 11, 2015 at 9:23 PM, Amalka Subasinghe  wrote:

>
> Hi,
>
> With the improvement we have made in 2.2.0-M3 release to the Runtime
> Config pages [1], we have introduced a new button called "Show More Detail"
> to show all details of resources only when the user click on it. otherwise
> we display name and description only.
>
> Let's say we have 10 properties defined in a given application, when we
> click on this button it makes more than 30 remote calls to all dev, test,
> prod gregs to returns the details.
> In the cloud staging environment it takes around *19 seconds to load the
> details of 10 properties.*
>
> We can reduce this loading time, introducing button or icon in front of
> each property to load information one by one (not all at once)
>
> [1] architecture mail - [Architecture] [AF] Removing Registry Mounts for
> the Dev, Test, Prod Registries.
>
> Thanks
> Amalka
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

done


On Fri, Sep 11, 2015 at 9:37 PM, Lasantha Fernando 
wrote:

> Hi Manu,
>
> Tested the CEP pack with the staged artifacts and the functionality is
> working fine. Please release the repo from staging.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 21:10, Manuranga Perera  wrote:
>
>> update http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-084/
>> please try and let me know
>>
>> On Fri, Sep 11, 2015 at 8:00 PM, Manuranga Perera  wrote:
>>
>>> please try with
>>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/
>>>
>>> On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera  wrote:
>>>
 please try 1.3.4 version with
 http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/


 On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera 
 wrote:

> ok will do. reverting the staging.
>
> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
> wrote:
>
>> When the jaggery versions are downgraded, it starts functioning
>> properly without any issue, albeit with the startup delay issue.
>>
>> If we can get releases of jaggery and jaggery-extensions for 0.10.x
>> and 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it 
>> should
>> resolve all the issues we are currently facing.
>>
>> Thanks,
>> Lasantha
>>
>> On 11 September 2015 at 15:45, Lasantha Fernando 
>> wrote:
>>
>>> Hi Manu,
>>>
>>> Thanks for the quick turnaround. This particular version upgrades
>>> the proper wss4j version and the startup issue gets fixed. But
>>> unfortunately, when we upgrade from jaggery 0.10.3 to 0.11.0 and
>>> jaggery-extensions from 1.3.2 to 1.4.2 to get these fixes, our 
>>> dashboard is
>>> broken.
>>>
>>> When creating a single dashboard, about 20 additional dashboards
>>> with the same name get created in our dashboards ui. See attached
>>> screenshot.
>>>
>>> @Manu, UES team, sorry to trouble you guys again, but would you guys
>>> be able to release new repos for jaggery-0.10.x and
>>> jaggery-extensions-1.3.x. It seems the upgrade from 0.10.x to 0.11.0
>>> doesn't work and we've already tested the dashboard extensively with the
>>> older jaggery versions.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 11 September 2015 at 14:25, KasunG Gajasinghe 
>>> wrote:
>>>

 Closed the staging repo as requested by Jaggery team. Please find
 the url -
 http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/

 On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
 wrote:

> will release with today.
>
> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando <
> lasan...@wso2.com> wrote:
>
>> Thanks Hasintha for pointing this out.
>>
>> @Manu, UES team, would you be able to do another release with the
>> above fix?
>>
>> On 11 September 2015 at 12:04, Hasintha Indrajee <
>> hasin...@wso2.com> wrote:
>>
>>> The issue with jaggery-extension release was referring and old
>>> pom as parent pom [1]. You need to update it into a new version of
>>> jaggery-parent pom  which is released with wss4j version upgrade.
>>>
>>> [1]
>>> https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>>
>>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Hi all,

 Thanks for the quick turnaround and releasing the required repo
 quickly. Appreciate your support very much!

 Unfortunately, it seems the jaggery-extensions-1.4.1 is still
 packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
 Please
 see the artifact packed inside the plugins folder in the zip at 
 [1].

 Can you check why the old version is still getting packed and
 provide a release with the fixes? I think there is an issue in how 
 the
 wss4j dependency has been specified. It is not there in the
 dependencyManagement section of the top level pom, but has been 
 specified
 as a dependency without versions in child level poms. Also I could 
 not find
 any place where the 'wss4j.osgi.version' seems to be used. Can you 
 check on
 these issues and fix it so that the proper jar is packed if needed 
 (or drop
 the jar altogether from the feature if possible) ?

 [1]
 

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Nuwan Wimalasekara]

Hi Shankar,

We wait for 5 min(by looping till 5 min) to let the server port open. if
the server failed to open the port within 5 min, We failed the test case or
skip all the tests. However 30 sec may be not enough for server to close
the port when restart, if it fail, Test case will be failed and we have to
kill the server after test and it will be tough since the server is not
starting properly. So better to wait for 2 min after we called restart and
let the server to close the port.

Thanks,
Nuwanw

On Fri, Sep 11, 2015 at 3:55 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

> sorry I misunderstood your comment previously.. Yes, what you have done is
> correct, but my thinking is, what will happen if the port is not closed
> within 30 seconds? Do we fail the test case? Same for the check on port
> open. If it didn't open within 15 seconds, do we fail the test case?
>
> On Fri, Sep 11, 2015 at 3:50 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Shankar,
>>
>> In the code currently we are looping to check if the port is close. If
>> the port does not close within 30 seconds then there should be an issue
>> (please correct me if am wrong). Then we wait for 15 seconds and then check
>> if the port is open (using the waitForPort provided by the automation
>> framework). This is to check if the server has successfully started again.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 3:43 PM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Even waiting for 30 seconds might not work. Can we loop with a sleep and
>>> see whether the process is not there and proceed? Port will be closed
>>> immediately, but the process might still run AFAIK.
>>>
>>> On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 See, there are nothing called intermittent issue. Just wrong way of
 doing stuff :)

 On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Shankar,
>
> I went through the log and noticed that in the ServerRestartTestCase,
> it sends a command to restart the server and waits for 15 seconds and
> proceeds. If in case the server takes longer time then there is an issue.
> Therefore I added the check to wait for the http port to be closed (or 
> wait
> for 30 seconds - This is for the server to shutdown) and then use the util
> provided by the automation team to check if the port it open (this is to
> check if the port is open). Thanks Nuwan for the help.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>>
>>
>> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Shankar,
>>>
>>> It seems to be another server was accessing the h2 database.
>>>
>>
>>
>> How it is possible? It can't be intermittent.. May be we are shutting
>> down / killing the server in one test case and without waiting for the
>> server to stop fully, starting the server in another test case. So,
>> depending on the time, sometime it will work and sometime it will not 
>> work.
>> Is that the case?
>>
>>
>>
>>> I am looking into the CarbonTestServerManager class which is used to
>>> start the servers.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 Folks, intermittent issues are the serious problem. We can't just
 leave it with intermittent issues. Please track and see what was the 
 cause?
 database locked by another process means, two servers are running at 
 the
 same time?

 On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi all,
>
> I was able to build the Kernel 4.4.x branch successfully. As Supun
> mentioned this looks like an intermittent issue. I will look into
> this further and update this thread.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Supun,
>>
>> I will look into this. Just now triggered a build in openstack.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
>> wrote:
>>
>>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>>> test method fails saying below,
>>>
>>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x
>>> branch.
>>> fyi, I built 4.4.x last night with all tests and build passed
>>> 

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Selvaratnam Uthaiyashankar]

Hi Nuwan,

My comment is, don't assume a particular duration where it will happen. I
agree we have to have a maximum, and beyond that we have to fail the test
case. If we are doing that, then fine. Just wanted to make sure we are not
assuming if we wait for n minutes, anyway the port will be closed/open and
then happily we can continue doing other tasks.

So, in future, when someone says it is an intermittent failure and second
build is successful, don't buy in the comment and go deep to see what
happens.

On Fri, Sep 11, 2015 at 4:05 PM, Nuwan Wimalasekara  wrote:

> Hi Shankar,
>
> We wait for 5 min(by looping till 5 min) to let the server port open. if
> the server failed to open the port within 5 min, We failed the test case or
> skip all the tests. However 30 sec may be not enough for server to close
> the port when restart, if it fail, Test case will be failed and we have to
> kill the server after test and it will be tough since the server is not
> starting properly. So better to wait for 2 min after we called restart and
> let the server to close the port.
>
> Thanks,
> Nuwanw
>
> On Fri, Sep 11, 2015 at 3:55 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> sorry I misunderstood your comment previously.. Yes, what you have done
>> is correct, but my thinking is, what will happen if the port is not closed
>> within 30 seconds? Do we fail the test case? Same for the check on port
>> open. If it didn't open within 15 seconds, do we fail the test case?
>>
>> On Fri, Sep 11, 2015 at 3:50 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Shankar,
>>>
>>> In the code currently we are looping to check if the port is close. If
>>> the port does not close within 30 seconds then there should be an issue
>>> (please correct me if am wrong). Then we wait for 15 seconds and then check
>>> if the port is open (using the waitForPort provided by the automation
>>> framework). This is to check if the server has successfully started again.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 3:43 PM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 Even waiting for 30 seconds might not work. Can we loop with a sleep
 and see whether the process is not there and proceed? Port will be closed
 immediately, but the process might still run AFAIK.

 On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
 shan...@wso2.com> wrote:

> See, there are nothing called intermittent issue. Just wrong way of
> doing stuff :)
>
> On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Shankar,
>>
>> I went through the log and noticed that in the ServerRestartTestCase,
>> it sends a command to restart the server and waits for 15 seconds and
>> proceeds. If in case the server takes longer time then there is an issue.
>> Therefore I added the check to wait for the http port to be closed (or 
>> wait
>> for 30 seconds - This is for the server to shutdown) and then use the 
>> util
>> provided by the automation team to check if the port it open (this is to
>> check if the port is open). Thanks Nuwan for the help.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>>
>>>
>>> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Shankar,

 It seems to be another server was accessing the h2 database.

>>>
>>>
>>> How it is possible? It can't be intermittent.. May be we are
>>> shutting down / killing the server in one test case and without waiting 
>>> for
>>> the server to stop fully, starting the server in another test case. So,
>>> depending on the time, sometime it will work and sometime it will not 
>>> work.
>>> Is that the case?
>>>
>>>
>>>
 I am looking into the CarbonTestServerManager class which is used
 to start the servers.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
 shan...@wso2.com> wrote:

> Folks, intermittent issues are the serious problem. We can't just
> leave it with intermittent issues. Please track and see what was the 
> cause?
> database locked by another process means, two servers are running at 
> the
> same time?
>
> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi all,
>>
>> I was able to build the Kernel 4.4.x branch successfully. As
>> Supun mentioned this looks like an intermittent issue. I will
>> look into this further and update this thread.
>>
>> Regards,
>> Nira

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

please try 1.3.4 version with
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/


On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera  wrote:

> ok will do. reverting the staging.
>
> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
> wrote:
>
>> When the jaggery versions are downgraded, it starts functioning properly
>> without any issue, albeit with the startup delay issue.
>>
>> If we can get releases of jaggery and jaggery-extensions for 0.10.x and
>> 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
>> resolve all the issues we are currently facing.
>>
>> Thanks,
>> Lasantha
>>
>> On 11 September 2015 at 15:45, Lasantha Fernando 
>> wrote:
>>
>>> Hi Manu,
>>>
>>> Thanks for the quick turnaround. This particular version upgrades the
>>> proper wss4j version and the startup issue gets fixed. But unfortunately,
>>> when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
>>> 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.
>>>
>>> When creating a single dashboard, about 20 additional dashboards with
>>> the same name get created in our dashboards ui. See attached screenshot.
>>>
>>> @Manu, UES team, sorry to trouble you guys again, but would you guys be
>>> able to release new repos for jaggery-0.10.x and jaggery-extensions-1.3.x.
>>> It seems the upgrade from 0.10.x to 0.11.0 doesn't work and we've already
>>> tested the dashboard extensively with the older jaggery versions.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 11 September 2015 at 14:25, KasunG Gajasinghe 
>>> wrote:
>>>

 Closed the staging repo as requested by Jaggery team. Please find the
 url -
 http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/

 On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
 wrote:

> will release with today.
>
> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando  > wrote:
>
>> Thanks Hasintha for pointing this out.
>>
>> @Manu, UES team, would you be able to do another release with the
>> above fix?
>>
>> On 11 September 2015 at 12:04, Hasintha Indrajee 
>> wrote:
>>
>>> The issue with jaggery-extension release was referring and old pom
>>> as parent pom [1]. You need to update it into a new version of
>>> jaggery-parent pom  which is released with wss4j version upgrade.
>>>
>>> [1]
>>> https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>>
>>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Hi all,

 Thanks for the quick turnaround and releasing the required repo
 quickly. Appreciate your support very much!

 Unfortunately, it seems the jaggery-extensions-1.4.1 is still
 packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
 Please
 see the artifact packed inside the plugins folder in the zip at [1].

 Can you check why the old version is still getting packed and
 provide a release with the fixes? I think there is an issue in how the
 wss4j dependency has been specified. It is not there in the
 dependencyManagement section of the top level pom, but has been 
 specified
 as a dependency without versions in child level poms. Also I could not 
 find
 any place where the 'wss4j.osgi.version' seems to be used. Can you 
 check on
 these issues and fix it so that the proper jar is packed if needed (or 
 drop
 the jar altogether from the feature if possible) ?

 [1]
 http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/

 Thanks,
 Lasantha

 On 10 September 2015 at 19:58, KasunG Gajasinghe 
 wrote:

>
> Released the repo from staging.
>
> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena <
> chan...@wso2.com> wrote:
>
>> Hi all,
>>
>> We have prepared the release steps for jagggery-extensions 1.4.1.
>> Builder team please close the repo and release
>> jagggery-extensions 1.4.1.
>>
>> Thanks!
>> -Chanaka
>>
>> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando <
>> lasan...@wso2.com> wrote:
>>
>>> Hi Manu, UES team,
>>>
>>> It seems this is fixed in jaggery 0.11.0. If we move our
>>> dashboard dependency version from 0.10.3 to 0.11.0, will this 
>>> affect our
>>> current dashboard functionality? (Any API changes, functionality 
>>> changes of
>>> existing features)
>>>
>>> Also, as per the thread 

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Amila De Silva]

Will be moving throttle.core to a new component under carbon-mediation. The
new component name will be throttle-core and a new feature with the same
name will be created. Planning to do these changes on
carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.

On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva  wrote:

> Hi All,
>
> One of the changes done while moving to Git was, moving source code which
> was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle core is
> used by both ESB (in Throttle mediator) and by API Manager (in
> APIThrottleHandler - to keep track of the number of API calls made over the
> cluster). At the time throttle core was moved, it was depending on Axis2
> only, making it possible to move the source code to wso2-synapse - which is
> not depending on any carbon components.
>
> While doing several improvements on throttling, Hazelcast AtomicLongs were
> used for keeping cluster-wide counts, which now creates a coupling between
> Hazelcast and Throttle Core. If these changes are to be merged with
> synapse, we would have to add a dependency to Hazelcast.
>
> The other option is to move Throttle Core into carbon-mediation. Since
> this already depends on several carbon components adding Hazelcast as a
> dependancy won't be an issue.
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][IS][Workflow] Two Human Tasks created at same event goes to different states

[Vinod Kavinda]

Hi Chamila,
It is the correct behaviour as Hasitha mentioned.
But, Are you assigning users for the human task using roles? As I remember,
in the bpel process we created for the workflow support, you can pass users
also as the potential owners to the ht. Try passing only the user name in
the initial request inside user tags. Then it will be in reserved state.
Regards,
Vinod kavinda
On Sep 10, 2015 3:40 PM, "Hasitha Aravinda"  wrote:

> Hi Chamila,
>
> Yes, This is correct user delegation behavior according to HumanTask spec
> [1]. This is what is happening in your scenario.
>
> When first task is created, you have only one user in admin/role1 roles.
> That means task has only one potential owner. When task has only one
> potential owner, task is automatically assigned that user and moves to
> RESERVED state.
>
> Then 2nd task is creates, you have multiple uses in admin/role1 roles.
> When task has multiple potential owners, task remains in READY state. Once
> user claims, it moves to RESERVED state. But any potential owner can start
> Ready tasks.
>
> Basically you have to search for both RESERVED and READY tasks for
> approval.
>
> [1] -
> http://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html#_Toc135718798
>
>
> Thanks,
> Hasitha.
>
>
> On Thu, Sep 10, 2015 at 2:37 PM, Chamila Wijayarathna 
> wrote:
>
>> Hi Nandika,
>>
>> I am running recently built IS pack workflow features. I came up with
>> following scenario which is confusing.
>>
>> I have two workflows which use same BPS.
>> Workflow1 need to be approved by 'admin' role and Workflow2 need to be
>> approved by 'role1' role.
>> Then I have a user 'user1' in my userstore who has both 'admin' and
>> 'role1' roles.
>>
>> Then I have configured two associations for addUser operation, where
>> association1 get assigned to workflow1 and association2 get assigned to
>> workflow2.
>>
>> Then when I add a new user to user store, 2 workflows get triggered, but
>> when I check the human tasks associated with them by calling
>> 'HumanTaskClientAPIAdmin', what I observe is even though there are two
>> human tasks created, one task is in 'RESERVED' state while other task is in
>> 'READY' state. This only happens when I add a user who has both 'admin' and
>> 'role1' roles. If there are no user with both roles, both tasks goes to the
>> 'RESERVED' state which is the expected behavior.
>>
>> What is the reason for this?
>>
>> Thank You!
>>
>> --
>> *Chamila Dilshan Wijayarathna,*
>> Software Engineer
>> Mobile:(+94)788193620
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +1 201 887 1971, +94 718 210 200
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Niranjan Karunanandham]

Hi Shankar,

In the code currently we are looping to check if the port is close. If the
port does not close within 30 seconds then there should be an issue (please
correct me if am wrong). Then we wait for 15 seconds and then check if the
port is open (using the waitForPort provided by the automation framework).
This is to check if the server has successfully started again.

Regards,
Nira

On Fri, Sep 11, 2015 at 3:43 PM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

> Even waiting for 30 seconds might not work. Can we loop with a sleep and
> see whether the process is not there and proceed? Port will be closed
> immediately, but the process might still run AFAIK.
>
> On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> See, there are nothing called intermittent issue. Just wrong way of doing
>> stuff :)
>>
>> On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Shankar,
>>>
>>> I went through the log and noticed that in the ServerRestartTestCase, it
>>> sends a command to restart the server and waits for 15 seconds and
>>> proceeds. If in case the server takes longer time then there is an issue.
>>> Therefore I added the check to wait for the http port to be closed (or wait
>>> for 30 seconds - This is for the server to shutdown) and then use the util
>>> provided by the automation team to check if the port it open (this is to
>>> check if the port is open). Thanks Nuwan for the help.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>


 On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Shankar,
>
> It seems to be another server was accessing the h2 database.
>


 How it is possible? It can't be intermittent.. May be we are shutting
 down / killing the server in one test case and without waiting for the
 server to stop fully, starting the server in another test case. So,
 depending on the time, sometime it will work and sometime it will not work.
 Is that the case?



> I am looking into the CarbonTestServerManager class which is used to
> start the servers.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> Folks, intermittent issues are the serious problem. We can't just
>> leave it with intermittent issues. Please track and see what was the 
>> cause?
>> database locked by another process means, two servers are running at the
>> same time?
>>
>> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> I was able to build the Kernel 4.4.x branch successfully. As Supun
>>> mentioned this looks like an intermittent issue. I will look into
>>> this further and update this thread.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Supun,

 I will look into this. Just now triggered a build in openstack.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
 wrote:

> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
> test method fails saying below,
>
> Aruna/ Niranjan can one of you have a look ? This is 4.4.x branch.
> fyi, I built 4.4.x last night with all tests and build passed for
> me. May be this is intermittent.
>
> INFO  
> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] 
> - [2015-09-11 02:04:44,020] FATAL 
> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to create 
> database tables for registry resource store. Database may be already 
> in use: "Locked by another process". Possible solutions: close all 
> other connection(s); use the server mode; SQL 
> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b 
> [90020-140] (Sanitized)
> INFO  
> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader] 
> - org.h2.jdbc.JdbcSQLException: Database may be already in use: 
> "Locked by another process". Possible solutions: close all other 
> connection(s); use the server mode; SQL statement:
>
>
>
> https://wso2.org/jenkins/job/carbon4-kernel_4.4.x/org.wso2.carbon$org.wso2.carbon.kernel.integration.test/48/testReport/
>
>
>
>
> On Fri, Sep 11, 2015 at 7:47 AM,  wrote:
>
>> See 

Re: [Dev] Getting error while installing features to IS 5.0.0 pack using pom

[Sameera Jayasoma]

I will check this.

On Fri, Sep 11, 2015 at 5:18 PM, Malintha Adikari  wrote:

> attaching POM file used to install key manager features.
>
> On Thu, Sep 10, 2015 at 10:56 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Hi Malintha,
>>
>> Shall we try to installed the feature using osgi console. You can refer
>> [1]. Automation of this approach would be bit tricky as we need to maintain
>> another script to do all these command execution.
>>
>> [1] http://wiki.eclipse.org/Equinox_p2_Console_Users_Guide
>>
>> Thanks,
>> Krishantha.
>>
>> On Wed, Sep 9, 2015 at 10:46 PM, Malintha Adikari 
>> wrote:
>>
>>> Thank you Lasitha for infomation
>>>
>>> On Wed, Sep 9, 2015 at 10:26 PM, Malintha Adikari 
>>> wrote:
>>>
 Adding Krishantha
 On Sep 9, 2015 6:30 PM, "Lasitha Wattaladeniya" 
 wrote:

> Hi Malintha,
>
> Apparently there's a bug, it's reported in this jira [1].
>
> [1]. https://wso2.org/jira/browse/CARBON-15195
>
> On Wed, Sep 9, 2015 at 3:59 PM, Malintha Adikari 
> wrote:
>
>> Hi,
>>
>> I am installing keymanager feature to IS 5.0.0 pack using pom file. I
>> am getting version conflicts for some features.
>> When I try to install
>>
>> Ex:
>> 
>>
>>  org.wso2.carbon.registry.contentsearch.server.feature.group
>>4.2.2
>> 
>>
>> I am getting following error
>>
>> Installing org.wso2.carbon.xfer.feature.group 4.2.0.
>> Installing org.wso2.carbon.stratos.deployment.feature.group 2.2.1.
>> Installing org.wso2.carbon.system.statistics.feature.group 4.2.2.
>> Installation failed.
>> Cannot complete the install because of a conflicting dependency.
>>  Software being installed: WSO2 Carbon - Registry Content Search
>> Server Feature 4.2.2
>> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.2)
>>  Software currently installed: WSO2 Carbon - Registry Content Search
>> Feature 4.2.1 (org.wso2.carbon.registry.contentsearch.feature.group 
>> 4.2.1)
>>  Only one of the following can be installed at once:
>>   WSO2 Carbon - Registry Content Search Server Feature 4.2.2
>> (org.wso2.carbon.registry.contentsearch.server.feature.jar 4.2.2)
>>   WSO2 Carbon - Registry Content Search Server Feature 4.2.1
>> (org.wso2.carbon.registry.contentsearch.server.feature.jar 4.2.1)
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Registry Content Search Feature 4.2.1
>> (org.wso2.carbon.registry.contentsearch.feature.group 4.2.1)
>>   To: org.wso2.carbon.registry.contentsearch.server.feature.group
>> [4.2.1]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Registry Content Search Server Feature 4.2.1
>> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.1)
>>   To: org.wso2.carbon.registry.contentsearch.server.feature.jar
>> [4.2.1]
>>  Cannot satisfy dependency:
>>   From: WSO2 Carbon - Registry Content Search Server Feature 4.2.2
>> (org.wso2.carbon.registry.contentsearch.server.feature.group 4.2.2)
>>   To: org.wso2.carbon.registry.contentsearch.server.feature.jar
>> [4.2.2]
>> Application failed, log file location:
>> /root/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1441793612480.log
>>
>> Seems there is a conflict between existing feature in the carbon pack
>> and the new feature to be installed. How can I upgrade a feature ?.
>> Appreciate your help on this.
>>
>> Regards,
>> Malintha
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Lasitha Wattaladeniya
> Software Engineer
> WSO2, Inc. | http://wso2.com
> lean. enterprise. middleware
>
> Mobile : +94719397528
> Blog : techreadme.blogspot.com
>

>>>
>>>
>>> --
>>> *Malintha Adikari*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 71 2312958
>>> Blog:http://malinthas.blogspot.com
>>> Page:   http://about.me/malintha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Krishantha Samaraweera
>> Senior Technical Lead - Test Automation
>> Mobile: +94 77 7759918
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>
>
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> 

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Nuwan Wimalasekara]

Yes. We have to check whether the port is closed by looping within a
defined max time (30 sec) just after *restart* is called. then we know It
is shutdown and going to restart. Then we have to wait for port to open.

Note : 30 sec is depends on the server load at that time. We can increase
the time since it only looping until the 30 sec.

Thanks,
Nuwanw

On Fri, Sep 11, 2015 at 3:50 PM, Niranjan Karunanandham 
wrote:

> Hi Shankar,
>
> In the code currently we are looping to check if the port is close. If the
> port does not close within 30 seconds then there should be an issue (please
> correct me if am wrong). Then we wait for 15 seconds and then check if the
> port is open (using the waitForPort provided by the automation framework).
> This is to check if the server has successfully started again.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 3:43 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> Even waiting for 30 seconds might not work. Can we loop with a sleep and
>> see whether the process is not there and proceed? Port will be closed
>> immediately, but the process might still run AFAIK.
>>
>> On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> See, there are nothing called intermittent issue. Just wrong way of
>>> doing stuff :)
>>>
>>> On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Shankar,

 I went through the log and noticed that in the ServerRestartTestCase,
 it sends a command to restart the server and waits for 15 seconds and
 proceeds. If in case the server takes longer time then there is an issue.
 Therefore I added the check to wait for the http port to be closed (or wait
 for 30 seconds - This is for the server to shutdown) and then use the util
 provided by the automation team to check if the port it open (this is to
 check if the port is open). Thanks Nuwan for the help.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
 shan...@wso2.com> wrote:

>
>
> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Shankar,
>>
>> It seems to be another server was accessing the h2 database.
>>
>
>
> How it is possible? It can't be intermittent.. May be we are shutting
> down / killing the server in one test case and without waiting for the
> server to stop fully, starting the server in another test case. So,
> depending on the time, sometime it will work and sometime it will not 
> work.
> Is that the case?
>
>
>
>> I am looking into the CarbonTestServerManager class which is used to
>> start the servers.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Folks, intermittent issues are the serious problem. We can't just
>>> leave it with intermittent issues. Please track and see what was the 
>>> cause?
>>> database locked by another process means, two servers are running at the
>>> same time?
>>>
>>> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi all,

 I was able to build the Kernel 4.4.x branch successfully. As Supun
 mentioned this looks like an intermittent issue. I will look into
 this further and update this thread.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Supun,
>
> I will look into this. Just now triggered a build in openstack.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
> wrote:
>
>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>> test method fails saying below,
>>
>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x
>> branch.
>> fyi, I built 4.4.x last night with all tests and build passed for
>> me. May be this is intermittent.
>>
>> INFO  
>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>  - [2015-09-11 02:04:44,020] FATAL 
>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to 
>> create database tables for registry resource store. Database may be 
>> already in use: "Locked by another process". Possible solutions: 
>> close all other connection(s); use the server mode; SQL 
>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b 
>> [90020-140] (Sanitized)
>> INFO  
>> 

Re: [Dev] Jenkins build became unstable: carbon4-kernel_4.4.x #48

[Selvaratnam Uthaiyashankar]

sorry I misunderstood your comment previously.. Yes, what you have done is
correct, but my thinking is, what will happen if the port is not closed
within 30 seconds? Do we fail the test case? Same for the check on port
open. If it didn't open within 15 seconds, do we fail the test case?

On Fri, Sep 11, 2015 at 3:50 PM, Niranjan Karunanandham 
wrote:

> Hi Shankar,
>
> In the code currently we are looping to check if the port is close. If the
> port does not close within 30 seconds then there should be an issue (please
> correct me if am wrong). Then we wait for 15 seconds and then check if the
> port is open (using the waitForPort provided by the automation framework).
> This is to check if the server has successfully started again.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 3:43 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> Even waiting for 30 seconds might not work. Can we loop with a sleep and
>> see whether the process is not there and proceed? Port will be closed
>> immediately, but the process might still run AFAIK.
>>
>> On Fri, Sep 11, 2015 at 3:41 PM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> See, there are nothing called intermittent issue. Just wrong way of
>>> doing stuff :)
>>>
>>> On Fri, Sep 11, 2015 at 3:36 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Shankar,

 I went through the log and noticed that in the ServerRestartTestCase,
 it sends a command to restart the server and waits for 15 seconds and
 proceeds. If in case the server takes longer time then there is an issue.
 Therefore I added the check to wait for the http port to be closed (or wait
 for 30 seconds - This is for the server to shutdown) and then use the util
 provided by the automation team to check if the port it open (this is to
 check if the port is open). Thanks Nuwan for the help.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 10:49 AM, Selvaratnam Uthaiyashankar <
 shan...@wso2.com> wrote:

>
>
> On Fri, Sep 11, 2015 at 10:38 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Shankar,
>>
>> It seems to be another server was accessing the h2 database.
>>
>
>
> How it is possible? It can't be intermittent.. May be we are shutting
> down / killing the server in one test case and without waiting for the
> server to stop fully, starting the server in another test case. So,
> depending on the time, sometime it will work and sometime it will not 
> work.
> Is that the case?
>
>
>
>> I am looking into the CarbonTestServerManager class which is used to
>> start the servers.
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 11, 2015 at 10:36 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Folks, intermittent issues are the serious problem. We can't just
>>> leave it with intermittent issues. Please track and see what was the 
>>> cause?
>>> database locked by another process means, two servers are running at the
>>> same time?
>>>
>>> On Fri, Sep 11, 2015 at 10:14 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi all,

 I was able to build the Kernel 4.4.x branch successfully. As Supun
 mentioned this looks like an intermittent issue. I will look into
 this further and update this thread.

 Regards,
 Nira

 On Fri, Sep 11, 2015 at 9:28 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Supun,
>
> I will look into this. Just now triggered a build in openstack.
>
> Regards,
> Nira
>
> On Fri, Sep 11, 2015 at 8:33 AM, Supun Malinga 
> wrote:
>
>> org.wso2.carbon.integration.tests.integration.ServerShutdownTestCase.testGracefulServerShutdown
>> test method fails saying below,
>>
>> Aruna/ Niranjan can one of you have a look ? This is 4.4.x
>> branch.
>> fyi, I built 4.4.x last night with all tests and build passed for
>> me. May be this is intermittent.
>>
>> INFO  
>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>  - [2015-09-11 02:04:44,020] FATAL 
>> {org.wso2.carbon.utils.dbcreator.DatabaseCreator} -  Failed to 
>> create database tables for registry resource store. Database may be 
>> already in use: "Locked by another process". Possible solutions: 
>> close all other connection(s); use the server mode; SQL 
>> statement:_null/14fba259c68182ad8201c93136703b5cf1b9e6fb09b 
>> [90020-140] (Sanitized)
>> INFO  
>> [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
>>  - 

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

ok will do. reverting the staging.

On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
wrote:

> When the jaggery versions are downgraded, it starts functioning properly
> without any issue, albeit with the startup delay issue.
>
> If we can get releases of jaggery and jaggery-extensions for 0.10.x and
> 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
> resolve all the issues we are currently facing.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 15:45, Lasantha Fernando 
> wrote:
>
>> Hi Manu,
>>
>> Thanks for the quick turnaround. This particular version upgrades the
>> proper wss4j version and the startup issue gets fixed. But unfortunately,
>> when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
>> 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.
>>
>> When creating a single dashboard, about 20 additional dashboards with the
>> same name get created in our dashboards ui. See attached screenshot.
>>
>> @Manu, UES team, sorry to trouble you guys again, but would you guys be
>> able to release new repos for jaggery-0.10.x and jaggery-extensions-1.3.x.
>> It seems the upgrade from 0.10.x to 0.11.0 doesn't work and we've already
>> tested the dashboard extensively with the older jaggery versions.
>>
>> Thanks,
>> Lasantha
>>
>> On 11 September 2015 at 14:25, KasunG Gajasinghe  wrote:
>>
>>>
>>> Closed the staging repo as requested by Jaggery team. Please find the
>>> url - http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>>>
>>> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
>>> wrote:
>>>
 will release with today.

 On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando 
 wrote:

> Thanks Hasintha for pointing this out.
>
> @Manu, UES team, would you be able to do another release with the
> above fix?
>
> On 11 September 2015 at 12:04, Hasintha Indrajee 
> wrote:
>
>> The issue with jaggery-extension release was referring and old pom as
>> parent pom [1]. You need to update it into a new version of 
>> jaggery-parent
>> pom  which is released with wss4j version upgrade.
>>
>> [1]
>> https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>>
>> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando > > wrote:
>>
>>> Hi all,
>>>
>>> Thanks for the quick turnaround and releasing the required repo
>>> quickly. Appreciate your support very much!
>>>
>>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still
>>> packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
>>> Please
>>> see the artifact packed inside the plugins folder in the zip at [1].
>>>
>>> Can you check why the old version is still getting packed and
>>> provide a release with the fixes? I think there is an issue in how the
>>> wss4j dependency has been specified. It is not there in the
>>> dependencyManagement section of the top level pom, but has been 
>>> specified
>>> as a dependency without versions in child level poms. Also I could not 
>>> find
>>> any place where the 'wss4j.osgi.version' seems to be used. Can you 
>>> check on
>>> these issues and fix it so that the proper jar is packed if needed (or 
>>> drop
>>> the jar altogether from the feature if possible) ?
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 10 September 2015 at 19:58, KasunG Gajasinghe 
>>> wrote:
>>>

 Released the repo from staging.

 On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena  wrote:

> Hi all,
>
> We have prepared the release steps for jagggery-extensions 1.4.1.
> Builder team please close the repo and release jagggery-extensions
> 1.4.1.
>
> Thanks!
> -Chanaka
>
> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando <
> lasan...@wso2.com> wrote:
>
>> Hi Manu, UES team,
>>
>> It seems this is fixed in jaggery 0.11.0. If we move our
>> dashboard dependency version from 0.10.3 to 0.11.0, will this affect 
>> our
>> current dashboard functionality? (Any API changes, functionality 
>> changes of
>> existing features)
>>
>> Also, as per the thread started by KasunG, it seems this issue is
>> there in jaggery-extensions as well. So can we get a release for
>> jaggery-extensions and jaggery (if upgrade does not work) with the 
>> proper
>> fix?
>>
>> We are currently planning to put an RC release of CEP 

[Dev] [AF Tools] use "master" as the label for default branch instead of "trunk"

[Kavith Lokuhewage]

Hi,

This is regarding $subject raised in [1] and [2].

Currently the default version of an application is given the version
"trunk" (which corresponds to "master" branch of the git repo). When
checking out a version, DevStudio checks whether the user is checking out
the version "trunk" and if so, sets "master" as the branch to checkout.
However, when labeling the list of apps in tree view, we are not doing a
mapping from "trunk" to "master". Rather we display the list of versions
returned from AF API as it is.
To fix this, either we have to maintain such a mapping in DevStudio side or
this can be fixed from the AF side itself - by renaming version "trunk" to
"master".
Most importantly, it will be a bad experience for the user if we use two
different version names in AF UI and DevS UI, to display this  default
version.
Is it possible (or make sense) to change this from AppFactory? Please share
your thoughts.


[1] https://wso2.org/jira/browse/TOOLS-3142
[2] https://wso2.org/jira/browse/TOOLS-3143

Thanks,

-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF Tools] use "master" as the label for default branch instead of "trunk"

[Danushka Fernando]

I guess we use trunk because we started this with svn and then moved on to
git. +1 for renaming. @Manjula WDYT?

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Fri, Sep 11, 2015 at 5:00 PM, Kavith Lokuhewage  wrote:

> Hi,
>
> This is regarding $subject raised in [1] and [2].
>
> Currently the default version of an application is given the version
> "trunk" (which corresponds to "master" branch of the git repo). When
> checking out a version, DevStudio checks whether the user is checking out
> the version "trunk" and if so, sets "master" as the branch to checkout.
> However, when labeling the list of apps in tree view, we are not doing a
> mapping from "trunk" to "master". Rather we display the list of versions
> returned from AF API as it is.
> To fix this, either we have to maintain such a mapping in DevStudio side
> or this can be fixed from the AF side itself - by renaming version "trunk"
> to "master".
> Most importantly, it will be a bad experience for the user if we use two
> different version names in AF UI and DevS UI, to display this  default
> version.
> Is it possible (or make sense) to change this from AppFactory? Please
> share your thoughts.
>
>
> [1] https://wso2.org/jira/browse/TOOLS-3142
> [2] https://wso2.org/jira/browse/TOOLS-3143
>
> Thanks,
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Chanaka Fernando]

Hi Amila,

You can find [1] which already has the throttle policy editor related
packages and named as mediation-throttle. You can move the throttle-core
packages to this component.

[1]
https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle

On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda 
wrote:

> +1.
>
>
> On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva  wrote:
>
>> Will be moving throttle.core to a new component under carbon-mediation.
>> The new component name will be throttle-core and a new feature with the
>> same name will be created. Planning to do these changes on
>> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>>
>> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva  wrote:
>>
>>> Hi All,
>>>
>>> One of the changes done while moving to Git was, moving source code
>>> which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
>>> core is used by both ESB (in Throttle mediator) and by API Manager (in
>>> APIThrottleHandler - to keep track of the number of API calls made over the
>>> cluster). At the time throttle core was moved, it was depending on Axis2
>>> only, making it possible to move the source code to wso2-synapse - which is
>>> not depending on any carbon components.
>>>
>>> While doing several improvements on throttling, Hazelcast AtomicLongs
>>> were used for keeping cluster-wide counts, which now creates a coupling
>>> between Hazelcast and Throttle Core. If these changes are to be merged with
>>> synapse, we would have to add a dependency to Hazelcast.
>>>
>>> The other option is to move Throttle Core into carbon-mediation. Since
>>> this already depends on several carbon components adding Hazelcast as a
>>> dependancy won't be an issue.
>>>
>>> --
>>> *Amila De Silva*
>>>
>>> WSO2 Inc.
>>> mobile :(+94) 775119302
>>>
>>>
>>
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 
--
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] CEP 4.0.0 Release Testing Update

[Shavantha Weerasinghe]

Hi All

This is to update the current status of CEP400 Release

Current pack used for testing is the pack we took on :9th September 2015

*Areas Covered up to now*

1.Event Receivers and Publishes
Email
File-tail
HTTP
JMS
MQTT
RDBMS
SOAP(receiver only)
WSO2Event (Thrift/Binary)(receiver only)

2.Carbon features

3.Siddhi Queries
Filters
Windows

*Aggregators*R siddhi extension

4.Integration


*Integration with App Server and ESB and MB was tested (tested mainly with
a local setup as we faced issues with the cluster CEP-1346)5.Fail over
scenarios*
Fail over scenarios between and Event publishers and CEP Receivers


6. User stores JDBC and  LDAP and also tested using MySQL and Oracle

7.samples testing

*Current testing status*

1.Currently we are focusing on verification of the cluster scenarios with
CEP and Storm however, for some tenants we face and issue where the CEP
manager fails to communicate with the storm cluster
https://wso2.org/jira/browse/CEP-1346 this blocks the testing for some
tenants.

2. We have set a long running test to run over the weekend


*What needs to be covered*

1.Siddhi extensions ML and others
2.Cover the remaining samples
3.Cover the Integration /Fail-over scenarios of CEP on the Cluster set-up
4.Verification of fixed bugs
5.Testing of analytic dashboard
6.Verification of remaining event receivers and publishers



Regards,
Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Sanjeewa Malalgoda]

+1.


On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva  wrote:

> Will be moving throttle.core to a new component under carbon-mediation.
> The new component name will be throttle-core and a new feature with the
> same name will be created. Planning to do these changes on
> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>
> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva  wrote:
>
>> Hi All,
>>
>> One of the changes done while moving to Git was, moving source code which
>> was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle core is
>> used by both ESB (in Throttle mediator) and by API Manager (in
>> APIThrottleHandler - to keep track of the number of API calls made over the
>> cluster). At the time throttle core was moved, it was depending on Axis2
>> only, making it possible to move the source code to wso2-synapse - which is
>> not depending on any carbon components.
>>
>> While doing several improvements on throttling, Hazelcast AtomicLongs
>> were used for keeping cluster-wide counts, which now creates a coupling
>> between Hazelcast and Throttle Core. If these changes are to be merged with
>> synapse, we would have to add a dependency to Hazelcast.
>>
>> The other option is to move Throttle Core into carbon-mediation. Since
>> this already depends on several carbon components adding Hazelcast as a
>> dependancy won't be an issue.
>>
>> --
>> *Amila De Silva*
>>
>> WSO2 Inc.
>> mobile :(+94) 775119302
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

please try with
http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/

On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera  wrote:

> please try 1.3.4 version with
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
>
>
> On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera  wrote:
>
>> ok will do. reverting the staging.
>>
>> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
>> wrote:
>>
>>> When the jaggery versions are downgraded, it starts functioning properly
>>> without any issue, albeit with the startup delay issue.
>>>
>>> If we can get releases of jaggery and jaggery-extensions for 0.10.x and
>>> 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
>>> resolve all the issues we are currently facing.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 11 September 2015 at 15:45, Lasantha Fernando 
>>> wrote:
>>>
 Hi Manu,

 Thanks for the quick turnaround. This particular version upgrades the
 proper wss4j version and the startup issue gets fixed. But unfortunately,
 when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.

 When creating a single dashboard, about 20 additional dashboards with
 the same name get created in our dashboards ui. See attached screenshot.

 @Manu, UES team, sorry to trouble you guys again, but would you guys be
 able to release new repos for jaggery-0.10.x and jaggery-extensions-1.3.x.
 It seems the upgrade from 0.10.x to 0.11.0 doesn't work and we've already
 tested the dashboard extensively with the older jaggery versions.

 Thanks,
 Lasantha

 On 11 September 2015 at 14:25, KasunG Gajasinghe 
 wrote:

>
> Closed the staging repo as requested by Jaggery team. Please find the
> url -
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>
> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
> wrote:
>
>> will release with today.
>>
>> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando <
>> lasan...@wso2.com> wrote:
>>
>>> Thanks Hasintha for pointing this out.
>>>
>>> @Manu, UES team, would you be able to do another release with the
>>> above fix?
>>>
>>> On 11 September 2015 at 12:04, Hasintha Indrajee 
>>> wrote:
>>>
 The issue with jaggery-extension release was referring and old pom
 as parent pom [1]. You need to update it into a new version of
 jaggery-parent pom  which is released with wss4j version upgrade.

 [1]
 https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23

 On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
 lasan...@wso2.com> wrote:

> Hi all,
>
> Thanks for the quick turnaround and releasing the required repo
> quickly. Appreciate your support very much!
>
> Unfortunately, it seems the jaggery-extensions-1.4.1 is still
> packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
> Please
> see the artifact packed inside the plugins folder in the zip at [1].
>
> Can you check why the old version is still getting packed and
> provide a release with the fixes? I think there is an issue in how the
> wss4j dependency has been specified. It is not there in the
> dependencyManagement section of the top level pom, but has been 
> specified
> as a dependency without versions in child level poms. Also I could 
> not find
> any place where the 'wss4j.osgi.version' seems to be used. Can you 
> check on
> these issues and fix it so that the proper jar is packed if needed 
> (or drop
> the jar altogether from the feature if possible) ?
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>
> Thanks,
> Lasantha
>
> On 10 September 2015 at 19:58, KasunG Gajasinghe 
> wrote:
>
>>
>> Released the repo from staging.
>>
>> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena <
>> chan...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We have prepared the release steps for jagggery-extensions 1.4.1.
>>> Builder team please close the repo and release
>>> jagggery-extensions 1.4.1.
>>>
>>> Thanks!
>>> -Chanaka
>>>
>>> On Thu, Sep 10, 2015 at 4:19 PM, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Hi Manu, UES team,

 It seems this is fixed in jaggery 0.11.0. If we 

Re: [Dev] [Throttling] Moving throttle.core out from Synapse

[Amila De Silva]

Hi Chanaka,

Since throttle core can be used on its own, thought of creating a separate
feature out of that - so a new place to put throttle component. If we put
it under mediation-throttle, that would imply two components have to be
used together, isn't it?

On Fri, Sep 11, 2015 at 6:45 PM, Chanaka Fernando  wrote:

> Hi Amila,
>
> You can find [1] which already has the throttle policy editor related
> packages and named as mediation-throttle. You can move the throttle-core
> packages to this component.
>
> [1]
> https://github.com/wso2/carbon-mediation/tree/master/components/mediation-throttle
>
> On Fri, Sep 11, 2015 at 6:23 PM, Sanjeewa Malalgoda 
> wrote:
>
>> +1.
>>
>>
>> On Fri, Sep 11, 2015 at 5:20 PM, Amila De Silva  wrote:
>>
>>> Will be moving throttle.core to a new component under carbon-mediation.
>>> The new component name will be throttle-core and a new feature with the
>>> same name will be created. Planning to do these changes on
>>> carbon-mediation 4.4.11-SNAPSHOT and synapse 2.1.3-wso2v12-SNAPSHOT.
>>>
>>> On Mon, Sep 7, 2015 at 6:25 PM, Amila De Silva  wrote:
>>>
 Hi All,

 One of the changes done while moving to Git was, moving source code
 which was under org.wso2.carbon.throttle.core to wso2-synapse. Throttle
 core is used by both ESB (in Throttle mediator) and by API Manager (in
 APIThrottleHandler - to keep track of the number of API calls made over the
 cluster). At the time throttle core was moved, it was depending on Axis2
 only, making it possible to move the source code to wso2-synapse - which is
 not depending on any carbon components.

 While doing several improvements on throttling, Hazelcast AtomicLongs
 were used for keeping cluster-wide counts, which now creates a coupling
 between Hazelcast and Throttle Core. If these changes are to be merged with
 synapse, we would have to add a dependency to Hazelcast.

 The other option is to move Throttle Core into carbon-mediation. Since
 this already depends on several carbon components adding Hazelcast as a
 dependancy won't be an issue.

 --
 *Amila De Silva*

 WSO2 Inc.
 mobile :(+94) 775119302


>>>
>>>
>>> --
>>> *Amila De Silva*
>>>
>>> WSO2 Inc.
>>> mobile :(+94) 775119302
>>>
>>>
>>
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>
>
> --
> --
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server startup slow after upgrading carbon.identity version from 4.5.5 to 4.5.6

[Manuranga Perera]

update http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-084/
please try and let me know

On Fri, Sep 11, 2015 at 8:00 PM, Manuranga Perera  wrote:

> please try with
> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-083/
>
> On Fri, Sep 11, 2015 at 4:59 PM, Manuranga Perera  wrote:
>
>> please try 1.3.4 version with
>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-079/
>>
>>
>> On Fri, Sep 11, 2015 at 3:54 PM, Manuranga Perera  wrote:
>>
>>> ok will do. reverting the staging.
>>>
>>> On Fri, Sep 11, 2015 at 3:48 PM, Lasantha Fernando 
>>> wrote:
>>>
 When the jaggery versions are downgraded, it starts functioning
 properly without any issue, albeit with the startup delay issue.

 If we can get releases of jaggery and jaggery-extensions for 0.10.x and
 1.3.x respectively, that uses the wss4j-1.5.11.wso2v11, then it should
 resolve all the issues we are currently facing.

 Thanks,
 Lasantha

 On 11 September 2015 at 15:45, Lasantha Fernando 
 wrote:

> Hi Manu,
>
> Thanks for the quick turnaround. This particular version upgrades the
> proper wss4j version and the startup issue gets fixed. But unfortunately,
> when we upgrade from jaggery 0.10.3 to 0.11.0 and jaggery-extensions from
> 1.3.2 to 1.4.2 to get these fixes, our dashboard is broken.
>
> When creating a single dashboard, about 20 additional dashboards with
> the same name get created in our dashboards ui. See attached screenshot.
>
> @Manu, UES team, sorry to trouble you guys again, but would you guys
> be able to release new repos for jaggery-0.10.x and
> jaggery-extensions-1.3.x. It seems the upgrade from 0.10.x to 0.11.0
> doesn't work and we've already tested the dashboard extensively with the
> older jaggery versions.
>
> Thanks,
> Lasantha
>
> On 11 September 2015 at 14:25, KasunG Gajasinghe 
> wrote:
>
>>
>> Closed the staging repo as requested by Jaggery team. Please find the
>> url -
>> http://maven.wso2.org/nexus/content/repositories/orgjaggeryjs-075/
>>
>> On Fri, Sep 11, 2015 at 12:45 PM, Manuranga Perera 
>> wrote:
>>
>>> will release with today.
>>>
>>> On Fri, Sep 11, 2015 at 12:13 PM, Lasantha Fernando <
>>> lasan...@wso2.com> wrote:
>>>
 Thanks Hasintha for pointing this out.

 @Manu, UES team, would you be able to do another release with the
 above fix?

 On 11 September 2015 at 12:04, Hasintha Indrajee  wrote:

> The issue with jaggery-extension release was referring and old pom
> as parent pom [1]. You need to update it into a new version of
> jaggery-parent pom  which is released with wss4j version upgrade.
>
> [1]
> https://github.com/wso2/jaggery-extensions/blob/v1.4.1/pom.xml#L23
>
> On Thu, Sep 10, 2015 at 9:10 PM, Lasantha Fernando <
> lasan...@wso2.com> wrote:
>
>> Hi all,
>>
>> Thanks for the quick turnaround and releasing the required repo
>> quickly. Appreciate your support very much!
>>
>> Unfortunately, it seems the jaggery-extensions-1.4.1 is still
>> packing wss4j-1.5.11-wso2v9.jar instead of 1.5.11-wso2v11 version. 
>> Please
>> see the artifact packed inside the plugins folder in the zip at [1].
>>
>> Can you check why the old version is still getting packed and
>> provide a release with the fixes? I think there is an issue in how 
>> the
>> wss4j dependency has been specified. It is not there in the
>> dependencyManagement section of the top level pom, but has been 
>> specified
>> as a dependency without versions in child level poms. Also I could 
>> not find
>> any place where the 'wss4j.osgi.version' seems to be used. Can you 
>> check on
>> these issues and fix it so that the proper jar is packed if needed 
>> (or drop
>> the jar altogether from the feature if possible) ?
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/releases/org/jaggeryjs/modules/ws.feature/1.4.1/
>>
>> Thanks,
>> Lasantha
>>
>> On 10 September 2015 at 19:58, KasunG Gajasinghe > > wrote:
>>
>>>
>>> Released the repo from staging.
>>>
>>> On Thu, Sep 10, 2015 at 7:04 PM, Chanaka Jayasena <
>>> chan...@wso2.com> wrote:
>>>
 Hi all,

 We have prepared the release steps for jagggery-extensions
 1.4.1.
 Builder team please close the repo and 

[Dev] [AF] "Show More Detail" button in runtime config page takes long time to respond

[Amalka Subasinghe]

Hi,

With the improvement we have made in 2.2.0-M3 release to the Runtime Config
pages [1], we have introduced a new button called "Show More Detail" to
show all details of resources only when the user click on it. otherwise we
display name and description only.

Let's say we have 10 properties defined in a given application, when we
click on this button it makes more than 30 remote calls to all dev, test,
prod gregs to returns the details.
In the cloud staging environment it takes around *19 seconds to load the
details of 10 properties.*

We can reduce this loading time, introducing button or icon in front of
each property to load information one by one (not all at once)

[1] architecture mail - [Architecture] [AF] Removing Registry Mounts for
the Dev, Test, Prod Registries.

Thanks
Amalka
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ES] Unbounded Data Field Tables Not Working As Expected

[Rasika Perera]

Hi ES Team,

I tried to create an Asset Type with following model elements in RXT using
ES v2.3.6;


> 
> Step Description
> 
> 
> Step Description
> 
> 


When creating an asset using "ES Publisher"; All model elements are
rendered correctly as per the image.

[image: Inline image 1]

But after submitting the form; when viewing the created artifact it has
only "step 2" value. This is also confirmed when viewing the artifact from
the "carbon console". And also, when adding an artifact using "carbon
console"; artifact is created correctly.

How can I get all values(e.g. step1, step2) into the unbounded artifact
field?

Note: I observed that; the form input elements for "step 1" and "step 2"
has the same "name" attribute."asset-api.js"[1] uses jaggery API
 `request.getAllParameters()` to read all submitted parameters where they
are stored on a map structure[2]. Hence, Parameters with the same key will
be overridden.

[1]
https://github.com/wso2/carbon-store/blob/9d79318fd657e278b1e7c7450681c0845c2964a6/apps/store/modules/asset-api.js#L127

[2]
https://github.com/wso2/jaggery/blob/542105b0bc01ec229773f905fc8a7e87a4bb167e/components/hostobjects/org.jaggeryjs.hostobjects.web/src/main/java/org/jaggeryjs/hostobjects/web/RequestHostObject.java#L254

-- 
With Regards,

*Rasika Perera*
Software Engineer
M: +94 71 680 9060 E: rasi...@wso2.com
LinkedIn: http://lk.linkedin.com/in/rasika90

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ML] Wrangler Integration

[Danula Eranjith]

Hi Nirmal,

Please find the document at [1] and I have already created the PR.

[1] -
https://docs.google.com/document/d/172MavBl2TuBNHVoyEPuRIPwmSW5lBljHFSNxrq4gclQ/edit?usp=sharing

Danula

On Sat, Sep 5, 2015 at 12:25 PM, Danula Eranjith 
wrote:

> Sure. Ill send the document and the PR
>
> Thanks,
> Danula
>
> On Fri, Sep 4, 2015 at 9:01 AM, Nirmal Fernando  wrote:
>
>> Also please send a PR to our repos.
>>
>> On Fri, Sep 4, 2015 at 8:59 AM, Nirmal Fernando  wrote:
>>
>>> Thanks Danula.
>>>
>>> ML team like to do the integration of this, since there're few things we
>>> need to clear up in ML side.
>>>
>>> Can you please come up with a clearly explained document on the project
>>> work carried out during the summer?
>>>
>>> On Wed, Sep 2, 2015 at 12:41 AM, Danula Eranjith 
>>> wrote:
>>>
 Hi,

 I have made the changes you suggested at [1] and created a API to
 access the wrangler service at [2].

 Also added a new step in the wizard at [3] with the wrangler interface.
 Please have a look.

 How can we create a sample of the dataset to be passed to wrangler? I
 couldn't find any current implementation capable of this.

 Another concern is if we are adding the feature selection step after
 the cleaning step, we need to reflect the changes done in step one at step
 two. But since we do not apply transformations to RDD initially, we need to
 come up an alternative approach.

 [1] -
 https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler/src/main/java/org/wso2/carbon/ml/wrangler

 [2] -
 https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.rest.api/src/main/java/org/wso2/carbon/ml/rest/api/WranglerApiV10.java
 

 [3] -
 https://github.com/danula/carbon-ml/blob/master/apps/ml/site/clean/clean.jag

 Thanks,
 Danula


 On Thu, Aug 27, 2015 at 9:41 AM, Danula Eranjith 
 wrote:

> Basically script exported from Wrangler tool has list of operations.
> Wrangler class parse that script and create WranglerOperation object
> for each operation with its parameters.
> Then when WranglerOperation.executeOperation() is invoked, it creates
> the respective SparkOperation object and then applies operations to the
> JavaRDD
>
> On Thu, Aug 27, 2015 at 9:35 AM, Nirmal Fernando 
> wrote:
>
>> What does WranglerOperation class do?
>>
>> On Thu, Aug 27, 2015 at 9:24 AM, Danula Eranjith > > wrote:
>>
>>> Currently Wrangler Operation is the class that holds details related
>>> to wrangler and SparkOperation contains the relevant Spark 
>>> transformation.
>>>
>>> If we are changing SparkOperation as WranglerOperation, we need to
>>> rename the current WranglerOperation into something else.
>>>
>>> On Thu, Aug 27, 2015 at 9:18 AM, Nirmal Fernando 
>>> wrote:
>>>
 /s/SparkOpration/SparkOperation

 May be as Supun said, I too think we should call them as
 'WranglerOperation'.

 On Thu, Aug 27, 2015 at 7:02 AM, Nirmal Fernando 
 wrote:

> Also, avoid static methods in transformations.
>
> On Thu, Aug 27, 2015 at 2:48 AM, Supun Sethunga 
> wrote:
>
>> Hi Danula,
>>
>> Few comments:
>>
>>- You might have to register the component in the OSGI
>>environment, to be able to call the services from a another 
>> component.
>>Refer [1] on how to do this.
>>- Better to introduce an interface for WranglerOperation
>>class.
>>- Add class level/ method level comments.
>>- Use logger in-place of System.out.println
>>
>> [1]
>> https://github.com/danula/carbon-ml/blob/master/components/ml/org.wso2.carbon.ml.database/src/main/java/org/wso2/carbon/ml/database/internal/ds/MLDatabaseServiceDS.java
>>
>> Thanks,
>> Supun
>>
>> On Wed, Aug 26, 2015 at 1:32 PM, Danula Eranjith <
>> hmdanu...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I added the component at [1]
>>> 
>>> Please have a look.
>>>
>>> [1] -
>>> https://github.com/danula/carbon-ml/tree/master/components/ml/org.wso2.carbon.ml.wrangler
>>>
>>> Danula
>>>
>>> On Tue, Aug 25, 2015 at 8:35 PM,