Re: [Dev] Need updates from all RMs

[Isuru Suriarachchi]

Here's the status of AS..

On Tue, Apr 3, 2012 at 8:41 PM, Afkham Azeez  wrote:

> RMs,
> Please send in a report of the current state of your products. This should
> include;
>
> 1. Build status
>

Currently no build breaks


> 2. Test status - any failing commented out tests. Jira links if so
>

No failures in tests


> 3. Code coverage - current coverage figures
>

OVERALL COVERAGE SUMMARYnameblock, %method, %class, %all classes
14%  (204999/1428949)17%  (9994/58824)26%  (1634/6174)



> 4. Status & severity of pending L1s/L2s
>

Still there are some persistence related issues which currently being
addressed. There are few L1's which was found in the last release and
planing to attend those after holidays.


> 5. Other issues & concerns
>

Need to do some OSGi level fixes to expose some packages from JDK. These
are needed to make AS fully CXF compliant. Looking into these.

Thanks,
~Isuru


>
> Thanks
> Azeez
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Dev] Need updates from all RMs

[Asela Pathberiya]

On Tue, Apr 3, 2012 at 8:41 PM, Afkham Azeez  wrote:

> RMs,
> Please send in a report of the current state of your products. This should
> include;
>
> 1. Build status
>

Successfully build with tests on Apr 03


> 2. Test status - any failing commented out tests. Jira links if so
>

No


> 3. Code coverage - current coverage figures
>

line   3%
methods  4%
classes 9%



> 4. Status & severity of pending L1s/L2s
>

There are  7 L1 and 11 L2 that related to IS product.


> 5. Other issues & concerns
>

Openid and STS feature has been removed from product, due to
some refactoring. And we need to add some more integration tests.


Thanks,
Asela.


> Thanks
> Azeez
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *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] Class loading issues when deploying JAXWS webapps in latest AS

[Isuru Suriarachchi]

I'll have a look into this..

Thanks,
~Isuru

On Wed, Apr 4, 2012 at 10:26 AM, Yumani Ranaweera  wrote:

>
>
> On Wed, Apr 4, 2012 at 9:43 AM, Yumani Ranaweera  wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 10:46 PM, Charitha Kankanamge 
>> wrote:
>>
>>> Btw, I'm on windows.
>>
>>
>>
>> Getting the same exceptions in Ubuntu also.
>
>
>
> But its only async_jaxws that failed for me. jaxrs_basic worked and
> only failure was this [1].
>
> [1] - https://wso2.org/jira/browse/CARBON-12809
>
> -Yumani
>
>
>>
>> Thanks,
>> Yumani
>>
>>
>>
>>
>> --
>> Yumani Ranaweera
>> Associate Technical Lead - QA
>> WSO2, Inc. - http://wso2.org
>>
>> Email : yum...@wso2.com
>> Cell: +94 077 7795242
>> Blog   : http://yumani.blogspot.com/
>>
>>
>
>
> --
> Yumani Ranaweera
> Associate Technical Lead - QA
> WSO2, Inc. - http://wso2.org
>
> Email : yum...@wso2.com
> Cell: +94 077 7795242
> Blog   : http://yumani.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Dev] Product Build #35 Failed

[Suhothayan Sriskandarajah]

On Wed, Apr 4, 2012 at 8:59 AM, Charith Wickramarachchi wrote:

> Hi  All ,
>
>
> Our Latest Product Build failed. Due to some test failures :(
>
> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-35/
>
> We have Two new Test Failures.
> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-35/test
>
> Please have a look. And also Sill We are getting the CEP Product Failure.
> I m checking what is the root cause for this.
>
> After the fix I found CEP  Product has passed in products build #36

Regards
Suho

>
> Reliable messaging test case: Test Case Result
> The below summarizes the result of the test "Reliable messaging test case"
> in build 35 of WSO2 Carbon - Products - Default Job. 
> 
>   DescriptionReliable messaging test case Test Class
> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase Method
> reliableMessagingTestCase
>  Duration1 min StatusFailed (New Failure)
>  Error Log
>
>
> java.lang.RuntimeException: The onComplete in HelloServiceCallbackHandler 
> didn't get invoked within 60 seconds
>   at 
> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:191)
>   at 
> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.reliableMessagingTestCase(HelloWorldSampleTestCase.java:229)
>
>
>
>
>
>
> Security scenarios test case: Test Case Result
>
>
> The below summarizes the result of the test "Security scenarios test case" in 
> build 35 of WSO2 Carbon - Products - Default Job.  
> 
>
>
>
>
> DescriptionSecurity scenarios test case
>
> Test Classorg.wso2.appserver.integration.tests.HelloWorldSampleTestCase
>
> MethodsecurityScenariosTestCase
>
>
>
> Duration32 secs
>
> StatusFailed (New Failure)
>
>
>
> Error Log
>
>
> org.apache.axis2.AxisFault: The security token could not be authenticated or 
> authorized; nested exception is:   
> javax.security.auth.callback.UnsupportedCallbackException: Check failed : 
> System error
> org.apache.axis2.AxisFault: The security token could not be authenticated or 
> authorized; nested exception is:
>   javax.security.auth.callback.UnsupportedCallbackException: Check failed 
> : System error
>   at 
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
>   at 
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>   at 
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>   at 
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
>   at 
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
>   at 
> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:206)
>   at 
> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.securityScenariosTestCase(HelloWorldSampleTestCase.java:376)
>
>
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*S. Suhothayan
*
Software Engineer,
Data Technologies Team,
 *WSO2, Inc. **http://wso2.com
 *
*lean.enterprise.middleware.*

*email: **s...@wso2.com* * cell: (+94) 779 756 757
blog: **http://suhothayan.blogspot.com/* *
twitter: **http://twitter.com/suhothayan* *
linked-in: **http://lk.linkedin.com/in/suhothayan*
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Next ESB version?

[Hiranya Jayathilaka]

On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:

>
>
> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka wrote:
>
>> Hi all,
>>
>> We still haven't decided on version for next ESB release which is based
>> on carbon 4.0.0.
>>
>> Latest released ESB version is 4.0.3 and next release will not have huge
>> changes to consider as 5.0.0.
>> I'm thinking about 4.[1-5].0
>>
>> How about 4.1.0?
>

+1

Thanks,
Hiranya


>
>
>> WDYT?
>>
>> --
>> Thanks,
>> Miyuru
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Vijitha Kumara]

> I think you did this on a clean repo ? Can you try running all 200+
integration tests and check, instead of running only those two ?

Initial build also contained all the 230 tests in GReg as the report
indicates.

But I'm now trying with including all other products as well to see whether
it makes any difference.

Regards,

On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga  wrote:

>
>
> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara  wrote:
>
>> All,
>>
>> All the tests related to these two classes passed. Attached the surefire
>> report with this.
>>
>
> Hi Vijitha,
>
> I think you did this on a clean repo ? Can you try running all 200+
> integration tests and check, instead of running only those two ?
>
>
>>
>>
>> Regards,
>>
>>
>> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara  wrote:
>>
>>> Had an issue with the build, Mail @Dev "Platform build error".
>>>
>>>
>>> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga wrote:
>>>


 On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando wrote:

> Hi Vijitha/Subash,
>
> Any update on this?
>

 Vijitha was building this on a clean repo. Vijitha , were you able to
 reproduce this ?


>
> Thanks,
> Senaka.
>
>
> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara wrote:
>
>> I'm looking into this.
>>
>> Regards,
>>
>> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando wrote:
>>
>>> Hi Subash, Vijitha,
>>>
>>> Please test this on a clean M2 repo, and before you start to compile
>>> edit the POM in the integration tests for G-Reg and make sure you enable
>>> the excluded tests. If we can reproduce this issue, it shouldn't be hard
>>> figure out how this broke.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando wrote:
>>>
 Hi all,

 I have moved it. The new issue can be accessed from
 https://wso2.org/jira/browse/CARBON-12758, and also the old issue
 ID.

 Thanks,
 Senaka.


 On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma >>> > wrote:

> +1. Senaka, please create these issues under CARBON project as
> L1s. Otherwise, its hard to track these stuff.
>
>  Thanks,
> Sameera.
>
> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
> chari...@wso2.com> wrote:
>
>> Hi Senaka,
>> Should not these failures reported as CARBON jira instead of
>> product specific JIRA? Have we changed our process of reporting 
>> JIRAs in C4
>> release? Or am I missing something?
>>
>> Thanks,
>> Charitha
>>
>>
>> On Friday, March 30, 2012, Senaka Fernando wrote:
>>
>>> FYI,  https://wso2.org/jira/browse/REGISTRY-717
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Fri, Mar 30, 2012 at 5:35 PM, Senaka Fernando <
>>> sen...@wso2.com> wrote:
>>>
 Hi Subash,

 Can you have a look into this? I tried this out with a build
 starting from orbit -> kernel -> platform, and was unable to 
 reproduce.

 Thanks,
 Senaka.

 --
 *Senaka Fernando*
 Product Manager - WSO2 Governance Registry;
 Associate Technical Lead; WSO2 Inc.; http://wso2.com*
 Member; Apache Software Foundation; http://apache.org

 E-mail: senaka AT wso2.com
 **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
 Linked-In: http://linkedin.com/in/senakafernando

 *Lean . Enterprise . Middleware


>>>
>>>
>>> --
>>> *Senaka Fernando*
>>> Product Manager - WSO2 Governance Registry;
>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>> Member; Apache Software Foundation; http://apache.org
>>>
>>> E-mail: senaka AT wso2.com
>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>> Linked-In: http://linkedin.com/in/senakafernando
>>>
>>> *Lean . Enterprise . Middleware
>>>
>>>
>>
>> --
>> Charitha Kankanamge
>> cell: +94 718 359 265
>> blog: http://charithaka.blogspot.com 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sameera Jayasoma
> Technical Lead and Product Manager, WSO2 Carbon
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: ht

Re: [Dev] Build Failure when building Axis2-jaxws

[Srinath Perera]

Hi Susara,

please try go to patch-releases/3.2.3/ directory and run mvn clean
install -Dmaven.test.skip=true

--Srinath

On Wed, Apr 4, 2012 at 10:15 AM, Susara De Saram  wrote:
> Hi all,
>       I need to build the source of ESB 4.0.3. I downloaded the source
> distribution of ESB 4.0.3 and followed the installation guide provided. The
> source tree contains carbon 3.2.0 (this branch
> - https://svn.wso2.org/repos/wso2/branches/carbon/3.2.0/). But I get the
> following error while the module axis2-jaxws is getting built. I use jdk
> 1.6.0 and Apache Maven 2.2.1 and I build on Windows 7. Any help for this
> would be truly appreciated.
>
> Thank you,
> Susara.
>
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Compiling 284 source files to E:\source1-esb\dependencies\
> axis2\1.6.1-wso
> 2v1\modules\jaxws\target\classes
> [INFO] -
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> \source1-esb\dependencies\axis2\1.6.1-wso2v1\modules\jaxws\src\org\apach
> e\axis2\jaxws\addressing\package-info.java:[22,37] cannot find symbol
> symbol  : method location()
> location: @interface javax.xml.bind.annotation.XmlSchema
>
> [INFO] 1error
> [INFO] -
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
> \source1-esb\dependencies\axis2\1.6.1-wso2v1\modules\jaxws\src\org\apache\axis2\
> jaxws\addressing\package-info.java:[22,37] cannot find symbol
> symbol  : method location()
> location: @interface javax.xml.bind.annotation.XmlSchema
>
>
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 27 minutes 22 seconds
> [INFO] Finished at: Wed Mar 28 21:22:35 IST 2012
> [INFO] Final Memory: 408M/508M
> [INFO]
> 



-- 

Srinath Perera, Ph.D.
  Senior Software Architect, WSO2 Inc.
  Visiting Faculty, University of Moratuwa
  Member, Apache Software Foundation
  Research Scientist, Lanka Software Foundation
  Blog: http://srinathsview.blogspot.com/
  Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Senaka Fernando]

Hi Vijitha,

It should include 233 test cases, IIRC, and you will have to uncomment the
ones that are excluded before you build.

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara  wrote:

> > I think you did this on a clean repo ? Can you try running all 200+
> integration tests and check, instead of running only those two ?
>
> Initial build also contained all the 230 tests in GReg as the report
> indicates.
>
> But I'm now trying with including all other products as well to see
> whether it makes any difference.
>
> Regards,
>
> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga  wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara  wrote:
>>
>>> All,
>>>
>>> All the tests related to these two classes passed. Attached the surefire
>>> report with this.
>>>
>>
>> Hi Vijitha,
>>
>> I think you did this on a clean repo ? Can you try running all 200+
>> integration tests and check, instead of running only those two ?
>>
>>
>>>
>>>
>>> Regards,
>>>
>>>
>>> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara  wrote:
>>>
 Had an issue with the build, Mail @Dev "Platform build error".


 On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga wrote:

>
>
> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando wrote:
>
>> Hi Vijitha/Subash,
>>
>> Any update on this?
>>
>
> Vijitha was building this on a clean repo. Vijitha , were you able to
> reproduce this ?
>
>
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara wrote:
>>
>>> I'm looking into this.
>>>
>>> Regards,
>>>
>>> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando wrote:
>>>
 Hi Subash, Vijitha,

 Please test this on a clean M2 repo, and before you start to
 compile edit the POM in the integration tests for G-Reg and make sure 
 you
 enable the excluded tests. If we can reproduce this issue, it 
 shouldn't be
 hard figure out how this broke.

 Thanks,
 Senaka.


 On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando 
 wrote:

> Hi all,
>
> I have moved it. The new issue can be accessed from
> https://wso2.org/jira/browse/CARBON-12758, and also the old issue
> ID.
>
> Thanks,
> Senaka.
>
>
> On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
> same...@wso2.com> wrote:
>
>> +1. Senaka, please create these issues under CARBON project as
>> L1s. Otherwise, its hard to track these stuff.
>>
>>  Thanks,
>> Sameera.
>>
>> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
>> chari...@wso2.com> wrote:
>>
>>> Hi Senaka,
>>> Should not these failures reported as CARBON jira instead of
>>> product specific JIRA? Have we changed our process of reporting 
>>> JIRAs in C4
>>> release? Or am I missing something?
>>>
>>> Thanks,
>>> Charitha
>>>
>>>
>>> On Friday, March 30, 2012, Senaka Fernando wrote:
>>>
 FYI,  https://wso2.org/jira/browse/REGISTRY-717

 Thanks,
 Senaka.

 On Fri, Mar 30, 2012 at 5:35 PM, Senaka Fernando <
 sen...@wso2.com> wrote:

> Hi Subash,
>
> Can you have a look into this? I tried this out with a build
> starting from orbit -> kernel -> platform, and was unable to 
> reproduce.
>
> Thanks,
> Senaka.
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


 --
 *Senaka Fernando*
 Product Manager - WSO2 Governance Registry;
 Associate Technical Lead; WSO2 Inc.; http://wso2.com*
 Member; Apache Software Foundation; http://apache.org

 E-mail: senaka AT wso2.com
 **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
 Linked-In: http://linkedin.com/in/senakafernando

 *Lean . Enterprise . Middleware


>>>
>>> --
>>> Charitha Kankanamge
>>> cell: +94 718 359 265
>>> blog: http://charithaka.blogspot.com 
>>

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #155 was SUCCESSFUL (with 2793 tests)

[Bamboo]

---
WSO2 Carbon > Kernel > #155 was successful.
---
This build was manually triggered by BambooBuilder.
2793 tests in total.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-155/



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Check-in Client using old Jars

[Dimuthu Leelarathne]

Hi,

Check-in client requires the following old jars to build.

commons-dbcp.wso2:commons-dbcp:jar:1.2.2.wso2v1 but version on trunk
1.4.0.wso2v1
org.apache.synapse:synapse-securevault:jar:2.1.0-wso2v2 but version trunk
2.1.0-wso2v6

thanks,
dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] Product Build #35 Failed

[Afkham Azeez]

On Wed, Apr 4, 2012 at 1:18 PM, Suhothayan Sriskandarajah wrote:

>
>
> On Wed, Apr 4, 2012 at 8:59 AM, Charith Wickramarachchi 
> wrote:
>
>> Hi  All ,
>>
>>
>> Our Latest Product Build failed. Due to some test failures :(
>>
>> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-35/
>>
>> We have Two new Test Failures.
>> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-35/test
>>
>> Please have a look. And also Sill We are getting the CEP Product Failure.
>> I m checking what is the root cause for this.
>>
>> After the fix I found CEP  Product has passed in products build #36
>

Yes, it was passing for me on my machine too.

>
> Regards
> Suho
>
>>
>> Reliable messaging test case: Test Case Result
>> The below summarizes the result of the test "Reliable messaging test
>> case" in build 35 of WSO2 Carbon - Products - Default Job. 
>> 
>>   DescriptionReliable messaging test case Test Class
>> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase Method
>> reliableMessagingTestCase
>>  Duration1 min StatusFailed (New Failure)
>>  Error Log
>>
>>
>> java.lang.RuntimeException: The onComplete in HelloServiceCallbackHandler 
>> didn't get invoked within 60 seconds
>>  at 
>> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:191)
>>  at 
>> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.reliableMessagingTestCase(HelloWorldSampleTestCase.java:229)
>>
>>
>>
>>
>>
>>
>>
>>
>> Security scenarios test case: Test Case Result
>>
>>
>>
>>
>> The below summarizes the result of the test "Security scenarios test case" 
>> in build 35 of WSO2 Carbon - Products - Default Job.  
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> DescriptionSecurity scenarios test case
>>
>>
>>
>> Test Classorg.wso2.appserver.integration.tests.HelloWorldSampleTestCase
>>
>>
>>
>> MethodsecurityScenariosTestCase
>>
>>
>>
>>
>>
>>
>>
>> Duration32 secs
>>
>>
>>
>> StatusFailed (New Failure)
>>
>>
>>
>>
>>
>>
>>
>> Error Log
>>
>>
>> org.apache.axis2.AxisFault: The security token could not be authenticated or 
>> authorized; nested exception is:   
>> javax.security.auth.callback.UnsupportedCallbackException: Check failed : 
>> System error
>> org.apache.axis2.AxisFault: The security token could not be authenticated or 
>> authorized; nested exception is:
>>  javax.security.auth.callback.UnsupportedCallbackException: Check failed 
>> : System error
>>  at 
>> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
>>  at 
>> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
>>  at 
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
>>  at 
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>>  at 
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>>  at 
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:555)
>>  at 
>> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:531)
>>  at 
>> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.doGreetWithSec(HelloWorldSampleTestCase.java:206)
>>  at 
>> org.wso2.appserver.integration.tests.HelloWorldSampleTestCase.securityScenariosTestCase(HelloWorldSampleTestCase.java:376)
>>
>>
>>
>> --
>> Charith Dhanushka Wickramarachchi
>> Software Engineer
>> WSO2 Inc
>> http://wso2.com/
>> http://wso2.org/
>>
>> blog
>> http://charithwiki.blogspot.com/
>>
>> twitter
>> http://twitter.com/charithwiki
>>
>> Mobile : 0776706568
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *S. Suhothayan
> *
> Software Engineer,
> Data Technologies Team,
>  *WSO2, Inc. **http://wso2.com
>  *
> *lean.enterprise.middleware.*
>
> *email: **s...@wso2.com* * cell: (+94) 779 756 757
> blog: **http://suhothayan.blogspot.com/* 
> *
> twitter: **http://twitter.com/suhothayan* *
> linked-in: **http://lk.linkedin.com/in/suhothayan*
> *
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev 

[Dev] Registry mounting fails with latest G-Reg/ESB packs

[Evanthika Amarasiri]

Hi all,

I came across [1], while setting up a registry mount with latest WSO2 ESB.
The configuration files used (in both ESB and G-Reg instances) are attached
to the JIRA.

[1] - https://wso2.org/jira/browse/CARBON-12819
*
*[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get child
paths of /_system/governance/permission/admin/manage. Cannot get a
connection, pool error Timeout waiting for idle object
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
error Timeout waiting for idle object
at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)

at
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)

at
org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)

at
org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)

at
org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)

at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)

at
org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)

at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)

at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)

at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)

at
org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)

at
org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)

at
org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)

at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)

at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)

at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)

at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)

at
org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)

at
org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)

at
org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
at
org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)

at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
at
org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)

Caused by: java.util.NoSuchElementException: Timeout waiting for idle
object
at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167)

at
org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)

... 28 more
[2012-04-04 12:13:55,529] ERROR - UserMgtInitializer While adding
management permission :: Resource does not exist at path
/_system/governance/permission/admin/manage
org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
Resource does not exist at path /_system/governance/permission/admin/manage
at
org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:437)

at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)

at
org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)

at
org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)

at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)

at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)

at
org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)

at
org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)

at
org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)

at
org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Subash Chaturanga]

On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando  wrote:

> Hi Vijitha,
>
> It should include 233 test cases, IIRC, and you will have to uncomment the
> ones that are excluded before you build.
>

Schema Test has excluded not from the pom but from the test class itself by
removing annotations. Seems that is the one missing which has 3,4 test
cases.
I have refactored it and excluded from the pom.

Vijitha, take an up in the integration module, and then remove all excluded
stuff locally and build again. Then you'll get #233.
BTW, I also able to build all the tests on a full svn up.


> Thanks,
> Senaka.
>
>
> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara  wrote:
>
>> > I think you did this on a clean repo ? Can you try running all 200+
>> integration tests and check, instead of running only those two ?
>>
>> Initial build also contained all the 230 tests in GReg as the report
>> indicates.
>>
>> But I'm now trying with including all other products as well to see
>> whether it makes any difference.
>>
>> Regards,
>>
>> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara  wrote:
>>>
 All,

 All the tests related to these two classes passed. Attached the
 surefire report with this.

>>>
>>> Hi Vijitha,
>>>
>>> I think you did this on a clean repo ? Can you try running all 200+
>>> integration tests and check, instead of running only those two ?
>>>
>>>


 Regards,


 On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara wrote:

> Had an issue with the build, Mail @Dev "Platform build error".
>
>
> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando wrote:
>>
>>> Hi Vijitha/Subash,
>>>
>>> Any update on this?
>>>
>>
>> Vijitha was building this on a clean repo. Vijitha , were you able to
>> reproduce this ?
>>
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara wrote:
>>>
 I'm looking into this.

 Regards,

 On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando 
 wrote:

> Hi Subash, Vijitha,
>
> Please test this on a clean M2 repo, and before you start to
> compile edit the POM in the integration tests for G-Reg and make sure 
> you
> enable the excluded tests. If we can reproduce this issue, it 
> shouldn't be
> hard figure out how this broke.
>
> Thanks,
> Senaka.
>
>
> On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando 
> wrote:
>
>> Hi all,
>>
>> I have moved it. The new issue can be accessed from
>> https://wso2.org/jira/browse/CARBON-12758, and also the old
>> issue ID.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
>> same...@wso2.com> wrote:
>>
>>> +1. Senaka, please create these issues under CARBON project as
>>> L1s. Otherwise, its hard to track these stuff.
>>>
>>>  Thanks,
>>> Sameera.
>>>
>>> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
>>> chari...@wso2.com> wrote:
>>>
 Hi Senaka,
 Should not these failures reported as CARBON jira instead of
 product specific JIRA? Have we changed our process of reporting 
 JIRAs in C4
 release? Or am I missing something?

 Thanks,
 Charitha


 On Friday, March 30, 2012, Senaka Fernando wrote:

> FYI,  https://wso2.org/jira/browse/REGISTRY-717
>
> Thanks,
> Senaka.
>
> On Fri, Mar 30, 2012 at 5:35 PM, Senaka Fernando <
> sen...@wso2.com> wrote:
>
>> Hi Subash,
>>
>> Can you have a look into this? I tried this out with a build
>> starting from orbit -> kernel -> platform, and was unable to 
>> reproduce.
>>
>> Thanks,
>> Senaka.
>>
>> --
>> *Senaka Fernando*
>> Product Manager - WSO2 Governance Registry;
>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Senaka Fernand

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Senaka Fernando]

On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga  wrote:

>
>
> On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando  wrote:
>
>> Hi Vijitha,
>>
>> It should include 233 test cases, IIRC, and you will have to uncomment
>> the ones that are excluded before you build.
>>
>
> Schema Test has excluded not from the pom but from the test class itself
> by removing annotations. Seems that is the one missing which has 3,4 test
> cases.
>

Oh, that's not done right who ever did that, :(..


> I have refactored it and excluded from the pom.
>

Great.

>
> Vijitha, take an up in the integration module, and then remove all
> excluded stuff locally and build again. Then you'll get #233.
> BTW, I also able to build all the tests on a full svn up.
>

+1

Thanks,
Senaka.

>
>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara  wrote:
>>
>>> > I think you did this on a clean repo ? Can you try running all 200+
>>> integration tests and check, instead of running only those two ?
>>>
>>> Initial build also contained all the 230 tests in GReg as the report
>>> indicates.
>>>
>>> But I'm now trying with including all other products as well to see
>>> whether it makes any difference.
>>>
>>> Regards,
>>>
>>> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga wrote:
>>>


 On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara wrote:

> All,
>
> All the tests related to these two classes passed. Attached the
> surefire report with this.
>

 Hi Vijitha,

 I think you did this on a clean repo ? Can you try running all 200+
 integration tests and check, instead of running only those two ?


>
>
> Regards,
>
>
> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara wrote:
>
>> Had an issue with the build, Mail @Dev "Platform build error".
>>
>>
>> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando wrote:
>>>
 Hi Vijitha/Subash,

 Any update on this?

>>>
>>> Vijitha was building this on a clean repo. Vijitha , were you able
>>> to reproduce this ?
>>>
>>>

 Thanks,
 Senaka.


 On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara wrote:

> I'm looking into this.
>
> Regards,
>
> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando 
> wrote:
>
>> Hi Subash, Vijitha,
>>
>> Please test this on a clean M2 repo, and before you start to
>> compile edit the POM in the integration tests for G-Reg and make 
>> sure you
>> enable the excluded tests. If we can reproduce this issue, it 
>> shouldn't be
>> hard figure out how this broke.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando > > wrote:
>>
>>> Hi all,
>>>
>>> I have moved it. The new issue can be accessed from
>>> https://wso2.org/jira/browse/CARBON-12758, and also the old
>>> issue ID.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
>>> same...@wso2.com> wrote:
>>>
 +1. Senaka, please create these issues under CARBON project as
 L1s. Otherwise, its hard to track these stuff.

  Thanks,
 Sameera.

 On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
 chari...@wso2.com> wrote:

> Hi Senaka,
> Should not these failures reported as CARBON jira instead of
> product specific JIRA? Have we changed our process of reporting 
> JIRAs in C4
> release? Or am I missing something?
>
> Thanks,
> Charitha
>
>
> On Friday, March 30, 2012, Senaka Fernando wrote:
>
>> FYI,  https://wso2.org/jira/browse/REGISTRY-717
>>
>> Thanks,
>> Senaka.
>>
>> On Fri, Mar 30, 2012 at 5:35 PM, Senaka Fernando <
>> sen...@wso2.com> wrote:
>>
>>> Hi Subash,
>>>
>>> Can you have a look into this? I tried this out with a build
>>> starting from orbit -> kernel -> platform, and was unable to 
>>> reproduce.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> --
>>> *Senaka Fernando*
>>> Product Manager - WSO2 Governance Registry;
>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
>>> Member; Apache Software Foundation; http://apache.org
>>>
>>> E

Re: [Dev] Having an Option to enable disable Cassandra Server Startup

[Charith Wickramarachchi]

On Wed, Apr 4, 2012 at 12:18 PM, Charith Wickramarachchi
wrote:

> There is one more problem even going with this
> property/configuration based approach.
>
> In Our case Cassandra server must be started before starting andes related
> features.
> So if we go with this approach In a Cluster enabled mode User will have to
>
> 1) Change the andes-config.xml in which he will enable clustering  (and do
> other config changes to point to zookeeper , Cassandra server etc )
> 2) Start the server with that system property used
> by Cassandra component   (Or if its a conifg change that config file)
>
>


> 2 places to do the same change. So its ugly.
>
>
May be this is ok. Since one can say they are two independent Tasks

--Charith

I think for BAM same problem will be there.
>
> Any ideas to fix this in a proper way ?
>
> thanks,
> Charith
>
>
> On Wed, Apr 4, 2012 at 12:09 PM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> basically its bundles that get activated. There is not feature concept in
>> runtime. Configuration based approach is the only way to handle this kind
>> of scenario. However configuration can be done using,
>> property/xml file
>> system property
>> Some other bundle configuring the target through configuration admin
>> service.
>>
>> thanks,
>> --Pradeep
>>
>
>
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
> http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
> twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

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

Re: [Dev] Registry mounting fails with latest G-Reg/ESB packs

[Sumedha Rubasinghe]

Were you pointing to an outside database or using the embedded one?


On Wed, Apr 4, 2012 at 1:53 PM, Evanthika Amarasiri wrote:

> Hi all,
>
> I came across [1], while setting up a registry mount with latest WSO2 ESB.
> The configuration files used (in both ESB and G-Reg instances) are attached
> to the JIRA.
>
> [1] - https://wso2.org/jira/browse/CARBON-12819
> *
> *[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get child
> paths of /_system/governance/permission/admin/manage. Cannot get a
> connection, pool error Timeout waiting for idle object
> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
> error Timeout waiting for idle object
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
>
> at
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
>
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)
>
> at
> org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>
> at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>
> at
> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>
> at
> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
>
> at
> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
>
> at
> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
> at
> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
>
> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
> at
> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>
> Caused by: java.util.NoSuchElementException: Timeout waiting for idle
> object
> at
> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167)
>
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
>
> ... 28 more
> [2012-04-04 12:13:55,529] ERROR - UserMgtInitializer While adding
> management permission :: Resource does not exist at path
> /_system/governance/permission/admin/manage
> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
> Resource does not exist at path /_system/governance/permission/admin/manage
> at
> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:437)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>
> at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>
> at
> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSC

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Vijitha Kumara]

> Schema Test has excluded not from the pom but from the test class itself
by removing annotations.

wasn't aware of that, will do as suggested.

On Wed, Apr 4, 2012 at 1:55 PM, Senaka Fernando  wrote:

>
>
> On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga  wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando  wrote:
>>
>>> Hi Vijitha,
>>>
>>> It should include 233 test cases, IIRC, and you will have to uncomment
>>> the ones that are excluded before you build.
>>>
>>
>> Schema Test has excluded not from the pom but from the test class itself
>> by removing annotations. Seems that is the one missing which has 3,4 test
>> cases.
>>
>
> Oh, that's not done right who ever did that, :(..
>
>
>> I have refactored it and excluded from the pom.
>>
>
> Great.
>
>>
>> Vijitha, take an up in the integration module, and then remove all
>> excluded stuff locally and build again. Then you'll get #233.
>> BTW, I also able to build all the tests on a full svn up.
>>
>
> +1
>
> Thanks,
> Senaka.
>
>>
>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara  wrote:
>>>
 > I think you did this on a clean repo ? Can you try running all 200+
 integration tests and check, instead of running only those two ?

 Initial build also contained all the 230 tests in GReg as the report
 indicates.

 But I'm now trying with including all other products as well to see
 whether it makes any difference.

 Regards,

 On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga wrote:

>
>
> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara wrote:
>
>> All,
>>
>> All the tests related to these two classes passed. Attached the
>> surefire report with this.
>>
>
> Hi Vijitha,
>
> I think you did this on a clean repo ? Can you try running all 200+
> integration tests and check, instead of running only those two ?
>
>
>>
>>
>> Regards,
>>
>>
>> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara wrote:
>>
>>> Had an issue with the build, Mail @Dev "Platform build error".
>>>
>>>
>>> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga 
>>> wrote:
>>>


 On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando wrote:

> Hi Vijitha/Subash,
>
> Any update on this?
>

 Vijitha was building this on a clean repo. Vijitha , were you able
 to reproduce this ?


>
> Thanks,
> Senaka.
>
>
> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara 
> wrote:
>
>> I'm looking into this.
>>
>> Regards,
>>
>> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando > > wrote:
>>
>>> Hi Subash, Vijitha,
>>>
>>> Please test this on a clean M2 repo, and before you start to
>>> compile edit the POM in the integration tests for G-Reg and make 
>>> sure you
>>> enable the excluded tests. If we can reproduce this issue, it 
>>> shouldn't be
>>> hard figure out how this broke.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando <
>>> sen...@wso2.com> wrote:
>>>
 Hi all,

 I have moved it. The new issue can be accessed from
 https://wso2.org/jira/browse/CARBON-12758, and also the old
 issue ID.

 Thanks,
 Senaka.


 On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
 same...@wso2.com> wrote:

> +1. Senaka, please create these issues under CARBON project as
> L1s. Otherwise, its hard to track these stuff.
>
>  Thanks,
> Sameera.
>
> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
> chari...@wso2.com> wrote:
>
>> Hi Senaka,
>> Should not these failures reported as CARBON jira instead of
>> product specific JIRA? Have we changed our process of reporting 
>> JIRAs in C4
>> release? Or am I missing something?
>>
>> Thanks,
>> Charitha
>>
>>
>> On Friday, March 30, 2012, Senaka Fernando wrote:
>>
>>> FYI,  https://wso2.org/jira/browse/REGISTRY-717
>>>
>>> Thanks,
>>> Senaka.
>>>
>>> On Fri, Mar 30, 2012 at 5:35 PM, Senaka Fernando <
>>> sen...@wso2.com> wrote:
>>>
 Hi Subash,

 Can you have a look into this? I tried this out with a
 build starting from orbit -> kernel 

Re: [Dev] Having an Option to enable disable Cassandra Server Startup

[Afkham Azeez]

It looks like we will need a gluing component that will take control of
managing this dependency between Andes & Cassandra. Instead of the 2
components initializing themselves independently and loading configuration
independently, this 3 component should read the conf files (may be a
separate, merged conf file) and then initialize Andes & Cassandra.

On Wed, Apr 4, 2012 at 1:58 PM, Charith Wickramarachchi wrote:

>
>
> On Wed, Apr 4, 2012 at 12:18 PM, Charith Wickramarachchi  > wrote:
>
>> There is one more problem even going with this
>> property/configuration based approach.
>>
>> In Our case Cassandra server must be started before starting andes
>> related features.
>> So if we go with this approach In a Cluster enabled mode User will have
>> to
>>
>> 1) Change the andes-config.xml in which he will enable clustering  (and
>> do other config changes to point to zookeeper , Cassandra server etc )
>> 2) Start the server with that system property used
>> by Cassandra component   (Or if its a conifg change that config file)
>>
>>
>
>
>> 2 places to do the same change. So its ugly.
>>
>>
> May be this is ok. Since one can say they are two independent Tasks
>
> --Charith
>
> I think for BAM same problem will be there.
>>
>> Any ideas to fix this in a proper way ?
>>
>> thanks,
>> Charith
>>
>>
>> On Wed, Apr 4, 2012 at 12:09 PM, Pradeep Fernando wrote:
>>
>>> Hi,
>>>
>>> basically its bundles that get activated. There is not feature concept
>>> in runtime. Configuration based approach is the only way to handle this
>>> kind of scenario. However configuration can be done using,
>>> property/xml file
>>> system property
>>> Some other bundle configuring the target through configuration admin
>>> service.
>>>
>>> thanks,
>>> --Pradeep
>>>
>>
>>
>>
>> --
>> Charith Dhanushka Wickramarachchi
>> Software Engineer
>> WSO2 Inc
>> http://wso2.com/
>>  http://wso2.org/
>>
>> blog
>> http://charithwiki.blogspot.com/
>>
>>  twitter
>> http://twitter.com/charithwiki
>>
>> Mobile : 0776706568
>>
>>
>>
>
>
> --
> Charith Dhanushka Wickramarachchi
> Software Engineer
> WSO2 Inc
> http://wso2.com/
>  http://wso2.org/
>
> blog
> http://charithwiki.blogspot.com/
>
>  twitter
> http://twitter.com/charithwiki
>
> Mobile : 0776706568
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry mounting fails with latest G-Reg/ESB packs

[Evanthika Amarasiri]

I have pointed all DBs to mySQL. The configuration files are attached to
the JIRA.

Regards,
Evanthika


On Wed, Apr 4, 2012 at 1:58 PM, Sumedha Rubasinghe  wrote:

> Were you pointing to an outside database or using the embedded one?
>
>
> On Wed, Apr 4, 2012 at 1:53 PM, Evanthika Amarasiri wrote:
>
>> Hi all,
>>
>> I came across [1], while setting up a registry mount with latest WSO2
>> ESB. The configuration files used (in both ESB and G-Reg instances) are
>> attached to the JIRA.
>>
>> [1] - https://wso2.org/jira/browse/CARBON-12819
>> *
>> *[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get child
>> paths of /_system/governance/permission/admin/manage. Cannot get a
>> connection, pool error Timeout waiting for idle object
>> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool
>> error Timeout waiting for idle object
>> at
>> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
>>
>> at
>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)
>>
>> at
>> org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>>
>> at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>>
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>>
>> at
>> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)
>>
>> at
>> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)
>>
>> at
>> org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:601)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>>
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>>
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>>
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>>
>> at
>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
>>
>> at
>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
>>
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
>>
>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
>> at
>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>>
>> Caused by: java.util.NoSuchElementException: Timeout waiting for idle
>> object
>> at
>> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167)
>>
>> at
>> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
>>
>> ... 28 more
>> [2012-04-04 12:13:55,529] ERROR - UserMgtInitializer While adding
>> management permission :: Resource does not exist at path
>> /_system/governance/permission/admin/manage
>> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
>> Resource does not exist at path /_system/governance/permission/admin/manage
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:437)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>>
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>>
>> at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>>
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRe

Re: [Dev] Registry mounting fails with latest G-Reg/ESB packs

[Senaka Fernando]

Hi Evanthika,

As long as your local DB is running it should not be an issue I believe.
Does this happen always or just once? Also, was this the only SQL exception
that you got?

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 2:02 PM, Evanthika Amarasiri wrote:

> I have pointed all DBs to mySQL. The configuration files are attached to
> the JIRA.
>
> Regards,
> Evanthika
>
>
>
> On Wed, Apr 4, 2012 at 1:58 PM, Sumedha Rubasinghe wrote:
>
>> Were you pointing to an outside database or using the embedded one?
>>
>>
>> On Wed, Apr 4, 2012 at 1:53 PM, Evanthika Amarasiri 
>> wrote:
>>
>>> Hi all,
>>>
>>> I came across [1], while setting up a registry mount with latest WSO2
>>> ESB. The configuration files used (in both ESB and G-Reg instances) are
>>> attached to the JIRA.
>>>
>>> [1] - https://wso2.org/jira/browse/CARBON-12819
>>> *
>>> *[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get child
>>> paths of /_system/governance/permission/admin/manage. Cannot get a
>>> connection, pool error Timeout waiting for idle object
>>> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
>>> pool error Timeout waiting for idle object
>>> at
>>> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
>>>
>>> at
>>> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)
>>>
>>> at
>>> org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>>>
>>> at
>>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>>>
>>> at
>>> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>>>
>>> at
>>> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)
>>>
>>> at
>>> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)
>>>
>>> at
>>> org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
>>>
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
>>>
>>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
>>> at
>>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>>>
>>> Caused by: java.util.NoSuchElementException: Timeout waiting for idle
>>> object
>>> at
>>> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167)
>>>
>>> at
>>> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
>>>
>>> ... 28 more
>>> [2012-04-04 12:13:55,529] ERROR - UserMgtInitializer While adding
>>> management permission :: Resource does not exist at path
>>> /_system/governance/permission/admin/manage
>>> org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
>>> Resource does not exist at path /_system/governance/permission/admin/manage
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:437)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>>>
>>> at
>>> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:

Re: [Dev] Check-in Client using old Jars

[Senaka Fernando]

We should fix the imported versions, by referring to the top-level POM
files.

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 1:49 PM, Dimuthu Leelarathne wrote:

> Hi,
>
> Check-in client requires the following old jars to build.
>
> commons-dbcp.wso2:commons-dbcp:jar:1.2.2.wso2v1 but version on trunk
> 1.4.0.wso2v1
> org.apache.synapse:synapse-securevault:jar:2.1.0-wso2v2 but version trunk
> 2.1.0-wso2v6
>
> thanks,
> dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

[Dev] Continuous Errors after disabling deployment Synchronizer

[Nirodha Pramod]

Hi,

After disabling svn based deployment synchronizer error getting logged in
every 15 seconds repeatedly. It keeps happening even after the server
restarts.
JIRA created at :  https://wso2.org/jira/browse/CARBON-12817


[2012-04-04 12:08:03,505] INFO
{org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
Terminating the synchronizer on file system at:
/home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
[2012-04-04 12:08:10,140] ERROR
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
Deployment synchronization for tenant 0 failed
java.lang.RuntimeException:
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
repository synchronizer has not been engaged for the file path:
/home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:73)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.doDeploymentSynchronization(CarbonDeploymentSchedulerTask.java:105)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:70)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by:
org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
repository synchronizer has not been engaged for the file path:
/home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.getSynchronizer(DeploymentSynchronizerServiceImpl.java:92)
at
org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:69)
... 10 more
[2012-04-04 12:08:25,143] ERROR
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
Deployment synchronization for tenant 0 failed

/Nirodha
-- 
*Nirodha Gallage*
Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Email: niro...@wso2.com   Mobile: +94716429078
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Continuous Errors after disabling deployment Synchronizer

[Afkham Azeez]

How can this happen if deployment synchronizer has been disabled?

On Wed, Apr 4, 2012 at 2:15 PM, Nirodha Pramod  wrote:

> Hi,
>
> After disabling svn based deployment synchronizer error getting logged in
> every 15 seconds repeatedly. It keeps happening even after the server
> restarts.
> JIRA created at :  https://wso2.org/jira/browse/CARBON-12817
>
>
> [2012-04-04 12:08:03,505] INFO
> {org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer} -
> Terminating the synchronizer on file system at:
> /home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
> [2012-04-04 12:08:10,140] ERROR
> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
> Deployment synchronization for tenant 0 failed
> java.lang.RuntimeException:
> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
> repository synchronizer has not been engaged for the file path:
> /home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
> at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:73)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.doDeploymentSynchronization(CarbonDeploymentSchedulerTask.java:105)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:70)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by:
> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
> repository synchronizer has not been engaged for the file path:
> /home/nirodha/WSO2/Carbon4/wso2as-4.5.0-SNAPSHOT/repository/deployment/server/
> at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.getSynchronizer(DeploymentSynchronizerServiceImpl.java:92)
> at
> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:69)
> ... 10 more
> [2012-04-04 12:08:25,143] ERROR
> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
> Deployment synchronization for tenant 0 failed
>
> /Nirodha
> --
> *Nirodha Gallage*
> Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Email: niro...@wso2.com   Mobile: +94716429078
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Registry mounting fails with latest G-Reg/ESB packs

[Charitha Kankanamge]

I too can reproduce this in windows. mounting is broken.

/Charitha

On Wed, Apr 4, 2012 at 2:10 PM, Senaka Fernando  wrote:

> Hi Evanthika,
>
> As long as your local DB is running it should not be an issue I believe.
> Does this happen always or just once? Also, was this the only SQL exception
> that you got?
>
> Thanks,
> Senaka.
>
>
> On Wed, Apr 4, 2012 at 2:02 PM, Evanthika Amarasiri wrote:
>
>> I have pointed all DBs to mySQL. The configuration files are attached to
>> the JIRA.
>>
>> Regards,
>> Evanthika
>>
>>
>>
>> On Wed, Apr 4, 2012 at 1:58 PM, Sumedha Rubasinghe wrote:
>>
>>> Were you pointing to an outside database or using the embedded one?
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:53 PM, Evanthika Amarasiri 
>>> wrote:
>>>
 Hi all,

 I came across [1], while setting up a registry mount with latest WSO2
 ESB. The configuration files used (in both ESB and G-Reg instances) are
 attached to the JIRA.

 [1] - https://wso2.org/jira/browse/CARBON-12819
 *
 *[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get child
 paths of /_system/governance/permission/admin/manage. Cannot get a
 connection, pool error Timeout waiting for idle object
 org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
 pool error Timeout waiting for idle object
 at
 org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)

 at
 org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)

 at
 org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)

 at
 org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)

 at
 org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)

 at
 org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)

 at
 org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)

 at
 org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)

 at
 org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)

 at
 org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)

 at
 org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)

 at
 org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)

 at
 org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)

 at
 org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)

 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

 at java.lang.reflect.Method.invoke(Method.java:601)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)

 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)

 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)

 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)

 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)

 at
 org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)

 at
 org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)

 at
 org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
 at
 org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)

 at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
 at
 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)

 Caused by: java.util.NoSuchElementException: Timeout waiting for idle
 object
 at
 org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1167)

 at
 org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)

 ... 28 more
 [2012-04-04 12:13:55,529] ERROR - UserMgtInitializer While adding
 management permission :: Resource does not exist at path
 /_system/governance/permission/admin/manage
 org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException:
 Resource does not exist at path /_system/governance/permission/admin/manage
 at
 org.wso2.carbon.registry.core.jdbc.handlers.b

Re: [Dev] Having an Option to enable disable Cassandra Server Startup

[Charith Wickramarachchi]

On Wed, Apr 4, 2012 at 2:01 PM, Afkham Azeez  wrote:

> It looks like we will need a gluing component that will take control of
> managing this dependency between Andes & Cassandra. Instead of the 2
> components initializing themselves independently and loading configuration
> independently, this 3 component should read the conf files (may be a
> separate, merged conf file) and then initialize Andes & Cassandra.
>
>
Thanks Azeez this is a good option. We will go ahead with this approach.


regards,
Charith


> On Wed, Apr 4, 2012 at 1:58 PM, Charith Wickramarachchi 
> wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 12:18 PM, Charith Wickramarachchi <
>> char...@wso2.com> wrote:
>>
>>> There is one more problem even going with this
>>> property/configuration based approach.
>>>
>>> In Our case Cassandra server must be started before starting andes
>>> related features.
>>> So if we go with this approach In a Cluster enabled mode User will have
>>> to
>>>
>>> 1) Change the andes-config.xml in which he will enable clustering  (and
>>> do other config changes to point to zookeeper , Cassandra server etc )
>>> 2) Start the server with that system property used
>>> by Cassandra component   (Or if its a conifg change that config file)
>>>
>>>
>>
>>
>>> 2 places to do the same change. So its ugly.
>>>
>>>
>> May be this is ok. Since one can say they are two independent Tasks
>>
>> --Charith
>>
>> I think for BAM same problem will be there.
>>>
>>> Any ideas to fix this in a proper way ?
>>>
>>> thanks,
>>> Charith
>>>
>>>
>>> On Wed, Apr 4, 2012 at 12:09 PM, Pradeep Fernando wrote:
>>>
 Hi,

 basically its bundles that get activated. There is not feature concept
 in runtime. Configuration based approach is the only way to handle this
 kind of scenario. However configuration can be done using,
 property/xml file
 system property
 Some other bundle configuring the target through configuration admin
 service.

 thanks,
 --Pradeep

>>>
>>>
>>>
>>> --
>>> Charith Dhanushka Wickramarachchi
>>> Software Engineer
>>> WSO2 Inc
>>> http://wso2.com/
>>>  http://wso2.org/
>>>
>>> blog
>>> http://charithwiki.blogspot.com/
>>>
>>>  twitter
>>> http://twitter.com/charithwiki
>>>
>>> Mobile : 0776706568
>>>
>>>
>>>
>>
>>
>> --
>> Charith Dhanushka Wickramarachchi
>> Software Engineer
>> WSO2 Inc
>> http://wso2.com/
>>  http://wso2.org/
>>
>> blog
>> http://charithwiki.blogspot.com/
>>
>>  twitter
>> http://twitter.com/charithwiki
>>
>> Mobile : 0776706568
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

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

[Dev] Old jars in BRS

[Dimuthu Leelarathne]

Hi,

Please note that BRS is using old jars in the product build.

Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.4-SNAPSHOT:p2-repo-gen
(2-p2-repo-generation) on project wso2stratos-brs-p2-profile: ERROR: The
repository system is offline but the artifact
org.wso2.carbon:org.apache.synapse.transport.nhttp.feature:zip:2.1.0-wso2v2
is not available in the local repository.


thanks,
dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] Registry mounting fails with latest G-Reg/ESB packs

[Senaka Fernando]

Hi all,

OK, should be something gone wrong in that case. Will have a look a little
later. There were some recent changes to the Registry Kernel to fix Sonar
errors, and may be something wasn't done quite right. We are also planning
to introduce test cases to the integration tests to validate mounting
functionality. So, this wouldn't be repeated in the future.

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 2:40 PM, Charitha Kankanamge wrote:

> I too can reproduce this in windows. mounting is broken.
>
> /Charitha
>
> On Wed, Apr 4, 2012 at 2:10 PM, Senaka Fernando  wrote:
>
>> Hi Evanthika,
>>
>> As long as your local DB is running it should not be an issue I believe.
>> Does this happen always or just once? Also, was this the only SQL exception
>> that you got?
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Apr 4, 2012 at 2:02 PM, Evanthika Amarasiri 
>> wrote:
>>
>>> I have pointed all DBs to mySQL. The configuration files are attached to
>>> the JIRA.
>>>
>>> Regards,
>>> Evanthika
>>>
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:58 PM, Sumedha Rubasinghe wrote:
>>>
 Were you pointing to an outside database or using the embedded one?


 On Wed, Apr 4, 2012 at 1:53 PM, Evanthika Amarasiri >>> > wrote:

> Hi all,
>
> I came across [1], while setting up a registry mount with latest WSO2
> ESB. The configuration files used (in both ESB and G-Reg instances) are
> attached to the JIRA.
>
> [1] - https://wso2.org/jira/browse/CARBON-12819
> *
> *[2012-04-04 12:13:55,518] ERROR - JDBCResourceDAO Failed to get
> child paths of /_system/governance/permission/admin/manage. Cannot get a
> connection, pool error Timeout waiting for idle object
> org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
> pool error Timeout waiting for idle object
> at
> org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:114)
>
> at
> org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
>
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.fillChildren(JDBCResourceDAO.java:766)
>
> at
> org.wso2.carbon.registry.core.CollectionImpl.getContent(CollectionImpl.java:297)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHandler.get(MountHandler.java:386)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.get(HandlerManager.java:2444)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandlerManager.get(UserDefinedHandlerManager.java:200)
>
> at
> org.wso2.carbon.registry.core.jdbc.handlers.HandlerLifecycleManager.get(HandlerLifecycleManager.java:959)
>
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.get(EmbeddedRegistry.java:512)
>
> at
> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.get(CacheBackedRegistry.java:133)
>
> at
> org.wso2.carbon.registry.core.session.UserRegistry.get(UserRegistry.java:514)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.addPermissions(UserMgtInitializer.java:68)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtInitializer.start(UserMgtInitializer.java:43)
>
> at
> org.wso2.carbon.user.mgt.internal.UserMgtDSComponent.activate(UserMgtDSComponent.java:49)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
>
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
>
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:588)
>
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:196)
>
> at
> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:441)
>
> at
> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:213)
>
> at
> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:800)
> at
> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:767)
>
> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
> at
> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>
> Caused by: java.util.NoSuchElementException: Timeout waiting for idle
> object
> at
> org.apache.commons.pool.impl

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #59 has FAILED. Change made by kasunw, charith and nuwan.

[Bamboo]

---
WSO2 Carbon > platform > #59 failed.
---
This build was manually triggered by BambooBuilder.
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PLATFORM-59/


--
Failing Jobs
--
  - Default Job (Default Stage): 1048 tests passed.


--
Code Changes
--
charith (124699):

>removing broker2

kasunw (124704):

>applying the patch providedby amani for fixing a build failure

nuwan (124707):

>object-object temp hack



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] getting denied.system.properties property is not specified error in my stratos local setup

[Manjula Rathnayake]

Hi,

I have changed the Stratos setup script only for AS,IS and Manager. I will
commit once checked for other services as well.

thank you.

>
>> On Wed, Mar 28, 2012 at 2:39 PM, Manjula Rathnayake wrote:
>>
>>>
>>>
>>> On Wed, Mar 28, 2012 at 2:32 PM, Supun Malinga  wrote:
>>>
 Hi Manjula,

 On Wed, Mar 28, 2012 at 2:25 PM, Manjula Rathnayake 
 wrote:

> Hi Supun,
>
> The Stratos setup script is broken at the moment due to changing
> configuration file paths. I will work with Damitha to fix this.
>

>> Just hit me that it wouldn't be that much broken. I was able to start
>> manager fine!
>> Its not easy to configure stratos manually. Running the default AS would
>> work since I need to create few tenants.
>>
>
> seems recent config. file moving isn't done for manager!. That's why it
> works fine.
>
>>
>>
>>> understood.
 Can you explain what this error means so that I can change the property
 files manually for the time being..

>>>
>>> I am not aware of this error. Can you start server without setting up
>>> the Stratos?
>>>

 thanks,

>
> Thank you.
>
> On Wed, Mar 28, 2012 at 2:08 PM, Supun Malinga wrote:
>
>> Hi,
>>
>> This happens after I run the setup script and try to start stratos AS.
>> But the before the stratos setup script run, stratos AS pack started
>> fine. So I would assume some property change done by the setup script 
>> cause
>> this.
>> Would be helpful to know what this error means.
>>
>> error,
>> JAVA_HOME environment variable is set to
>> /home/disk1/Programs/jdk1.6.0_24
>> CARBON_HOME environment variable is set to
>> /home/supun/smoke/stratos/wso2stratos-as-1.1.0-SNAPSHOT
>> Error occurred during initialization of VM
>> java.lang.ExceptionInInitializerError
>> at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
>>  at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
>> Caused by: java.lang.IllegalArgumentException:
>> denied.system.properties property is not specified.
>>  at
>> org.wso2.carbon.bootstrap.CarbonSecurityManager.(CarbonSecurityManager.java:44)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>>  at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>> at java.lang.Class.newInstance0(Class.java:355)
>>  at java.lang.Class.newInstance(Class.java:308)
>> at sun.misc.Launcher.(Launcher.java:80)
>>  at sun.misc.Launcher.(Launcher.java:43)
>> at java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:1338)
>>  at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1320)
>>
>> thanks,
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - sup...@wso2.com 
>> mobile - 071 56 91 321
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Manjula Rathnayaka
> Software Engineer
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



 --
 Supun Malinga,

 Software Engineer,
 WSO2 Inc.
 http://wso2.com
 http://wso2.org
 email - sup...@wso2.com 
 mobile - 071 56 91 321


>>>
>>>
>>> --
>>> Manjula Rathnayaka
>>> Software Engineer
>>> WSO2, Inc.
>>> Mobile:+94 77 743 1987
>>>
>>
>>
>>
>> --
>> Supun Malinga,
>>
>> Software Engineer,
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>> email - sup...@wso2.com 
>> mobile - 071 56 91 321
>>
>>
>
>
> --
> Supun Malinga,
>
> Software Engineer,
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
> email - sup...@wso2.com 
> mobile - 071 56 91 321
>
>


-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tribes clustering is broken in jdk1.7

[Afkham Azeez]

Can you remove that xbootjar and impl.prefix entries in wso2server.sh and
retry?

On Wed, Apr 4, 2012 at 3:59 PM, Charitha Kankanamge wrote:

> java.net.SocketException: bad argument for SO_REUSEADDR;




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon > platform > #59 has FAILED. Change made by kasunw, charith and nuwan.

[Charith Wickramarachchi]

Hi All ,

We will Trigger a Build at 10.00 pm today. With new SVN Checkout and a
Clean maven repo. Please make sure You commit all the Fixes for current
build failures and make sure your *commit does not break the build. *Double
check before you commit any thing. Plan is to have a QA Pack ready by
tomorrow.

thanks,
Charith



On Wed, Apr 4, 2012 at 3:43 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 
> Carbon›
> platform›
> #59
> failed
>
> This build was manually triggered by 
> BambooBuilder
> .
>
> No failed tests found, a possible compilation error.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  Default 
> Job
>  (Default
> Stage)  104 minutes  1048 passed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> all 4 code 
> changes
> nuwan 
> object-object temp hack  124707
> kasunw
> applying the patch providedby amani for fixing a build failure  124704
> charith 
> removing broker2  124699   1 more 
> changes…
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profileor
>  notify
> your 
> administrator
> .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/

blog
http://charithwiki.blogspot.com/

twitter
http://twitter.com/charithwiki

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

[Dev] [Bamboo-Build] WSO2 Carbon > P2-Repo > #22 has FAILED. Change made by 13 authors.

[Bamboo]

---
WSO2 Carbon > P2-Repo > #22 failed.
---
Code has been updated by denis, samisa, kasung, nandika, ishan, subash, lalaji, 
kasunw, eranda, chamara, charith, nirmal, nuwan.
No failed tests found, a possible compilation error.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-P2REPO-22/


--
Failing Jobs
--
  - Default Job (Default Stage): No tests found.


--
Code Changes
--
charith (124699):

>removing broker2

denis (124682):

>Fixed an XPath issue in sample

subash (124727):

>Excluded SchemaTestCase in proper way and removed sec verifier test



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Next ESB version?

[Isabelle Mauny]

All,

We are adding quite a few features to this release, as per latest plan on 
GDocs. Doesn't that justify a 4.5 ? 

Isabelle.
--
Isabelle Mauny
Director, Product Management; WSO2, Inc.;  http://wso2.com/
email: isabe...@wso2.com - mobile: +34 616050684

On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:

> 
> 
> On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:
> 
> 
> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka  wrote:
> Hi all,
> 
> We still haven't decided on version for next ESB release which is based on 
> carbon 4.0.0.
> 
> Latest released ESB version is 4.0.3 and next release will not have huge 
> changes to consider as 5.0.0.
> I'm thinking about 4.[1-5].0
> 
> How about 4.1.0? 
> 
> +1
> 
> Thanks,
> Hiranya
>  
>  
> WDYT?
> 
> -- 
> Thanks,
> Miyuru
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> 
> -- 
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
> 
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
> 
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
> 
> 
> 
> 
> -- 
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
> ___
> 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] [Bamboo-Build] WSO2 Carbon > platform > #59 has FAILED. Change made by kasunw, charith and nuwan.

[Dimuthu Leelarathne]

Hi,

This looks like a time out at Bamboo.


build   04-Apr-2012 03:07:11[ERROR] Failed to execute goal on project
Apache-Synapse: Could not resolve dependencies for project
org.apache.synapse:Apache-Synapse:pom:2.1.0-wso2v6: Failed to collect
dependencies for [jline:jline:jar:0.9.94 (provided),
org.apache.axis2:axis2-transport-local:jar:1.6.1-wso2v2 (test),
org.apache.axis2:axis2-kernel:jar:1.6.1-wso2v2 (compile),
org.apache.axis2:axis2-adb:jar:1.6.1-wso2v2 (compile),
org.apache.axis2:axis2-clustering:jar:1.6.1-wso2v2 (compile),
org.apache.axis2:axis2-mtompolicy:jar:1.6.1-wso2v2 (compile),
org.apache.neethi:neethi:jar:2.0.4-wso2v1 (compile),
org.apache.sandesha2:sandesha2-core:jar:1.6.1-wso2v1 (compile),
commons-logging:commons-logging:jar:1.1.1 (compile), junit:junit:jar:3.8.2
(test), xmlunit:xmlunit:jar:1.1 (test), org.apache.derby:derby:jar:10.4.2.0
(test), xalan:xalan:jar:2.7.1 (compile), xerces:xercesImpl:jar:2.8.1
(compile), rhino:js:jar:1.6R5 (compile),
commons-dbcp:commons-dbcp:jar:1.2.2 (compile),
commons-pool:commons-pool:jar:1.3 (compile), org.apache.bcel:bcel:jar:5.2
(compile), jakarta-regexp:jakarta-regexp:jar:1.4 (compile),
java-cup:java-cup:jar:0.0 (compile), JLex:JLex:jar:0.0 (compile),
org.opensymphony:quartz:jar:1.6.0 (compile), net.sf.saxon:saxon:jar:8.9
(compile), net.sf.saxon:saxon-dom:jar:8.9 (compile),
net.sf.saxon:saxon-xqj:jar:8.9 (compile), commons-cli:commons-cli:jar:1.0
(compile), commons-lang:commons-lang:jar:2.4 (test),
org.wso2.uri.template:wso2-uri-templates:jar:1.0.0 (compile),
org.wso2.caching:wso2caching-core:jar:3.5.0 (compile),
org.wso2.eventing:wso2eventing-api:jar:2.1 (compile)]: Failed to read
artifact descriptor for java-cup:java-cup:jar:0.0: Could not transfer
artifact java-cup:java-cup:pom:0.0 from/to central (
http://repo1.maven.org/maven2): Error transferring file: Connection timed
out -> [Help 1]
build   04-Apr-2012 03:07:11[ERROR] Failed to execute goal on project
webharvest-core: Could not resolve dependencies for project
org.webharvest:webharvest-core:jar:2.0.wso2v1: Failed to collect
dependencies for [rhino:js:jar:1.7R1 (compile), bsh:bsh:jar:1.3.0
(compile), org.htmlcleaner:htmlcleaner:jar:2.1 (compile),
commons-codec:commons-codec:jar:1.3 (compile),
commons-collections:commons-collections:jar:3.2 (compile),
commons-httpclient:commons-httpclient:jar:3.1 (compile),
commons-net:commons-net:jar:2.0 (compile), log4j:log4j:jar:1.2.13
(compile), net.sf.saxon:saxon:jar:8.9 (compile),
commons-email:commons-email:jar:1.2 (compile),
groovy:groovy-all:jar:1.1-rc-1 (compile),
javax.activation:activation:jar:1.1.1 (compile)]: Failed to read artifact
descriptor for commons-email:commons-email:jar:1.2: Could not transfer
artifact commons-email:commons-email:pom:1.2 from/to central (
http://repo1.maven.org/maven2): Error transferring file: Connection timed
out -> [Help 1]


thanks,
dimuthu

On Wed, Apr 4, 2012 at 3:43 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 
> Carbon›
> platform›
> #59
> failed
>
> This build was manually triggered by 
> BambooBuilder
> .
>
> No failed tests found, a possible compilation error.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  Default 
> Job
>  (Default
> Stage)  104 minutes  1048 passed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> all 4 code 
> changes
> nuwan 
> object-object temp hack  124707
> kasunw
> applying the patch providedby amani for fixing a build failure  124704
> charith 
> removing broker2  124699   1 more 
> changes…
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profileor
>  notify
> your 
> admin

Re: [Dev] Next ESB version?

[Paul Fremantle]

I think this sounds like a 4.5.

Paul

On 4 April 2012 12:02, Isabelle Mauny  wrote:

> All,
>
> We are adding quite a few features to this release, as per latest plan on
> GDocs. Doesn't that justify a 4.5 ?
>
> Isabelle.
>  --
> Isabelle Mauny
> Director, Product Management; WSO2, Inc.;  http://wso2.com/
> email: isabe...@wso2.com  - mobile: +34 616050684
>
> On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:
>
>
>
> On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka wrote:
>>
>>> Hi all,
>>>
>>> We still haven't decided on version for next ESB release which is based
>>> on carbon 4.0.0.
>>>
>>> Latest released ESB version is 4.0.3 and next release will not have huge
>>> changes to consider as 5.0.0.
>>> I'm thinking about 4.[1-5].0
>>>
>>> How about 4.1.0?
>>
>
> +1
>
> Thanks,
> Hiranya
>
>
>>
>>
>>> WDYT?
>>>
>>> --
>>> Thanks,
>>> Miyuru
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
> ___
> 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
>
>


-- 
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
p...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Senaka Fernando]

Hi Subash, Vijitha,

If possible also try to find the ordering of this on Bamboo and when we
build. I have a feeling that Bamboo is running this in some other order.

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 2:00 PM, Vijitha Kumara  wrote:

> > Schema Test has excluded not from the pom but from the test class
> itself by removing annotations.
>
> wasn't aware of that, will do as suggested.
>
> On Wed, Apr 4, 2012 at 1:55 PM, Senaka Fernando  wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando  wrote:
>>>
 Hi Vijitha,

 It should include 233 test cases, IIRC, and you will have to uncomment
 the ones that are excluded before you build.

>>>
>>> Schema Test has excluded not from the pom but from the test class itself
>>> by removing annotations. Seems that is the one missing which has 3,4 test
>>> cases.
>>>
>>
>> Oh, that's not done right who ever did that, :(..
>>
>>
>>>  I have refactored it and excluded from the pom.
>>>
>>
>> Great.
>>
>>>
>>> Vijitha, take an up in the integration module, and then remove all
>>> excluded stuff locally and build again. Then you'll get #233.
>>> BTW, I also able to build all the tests on a full svn up.
>>>
>>
>> +1
>>
>> Thanks,
>> Senaka.
>>
>>>
>>>
 Thanks,
 Senaka.


 On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara wrote:

> > I think you did this on a clean repo ? Can you try running all 200+
> integration tests and check, instead of running only those two ?
>
> Initial build also contained all the 230 tests in GReg as the report
> indicates.
>
> But I'm now trying with including all other products as well to see
> whether it makes any difference.
>
> Regards,
>
> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara wrote:
>>
>>> All,
>>>
>>> All the tests related to these two classes passed. Attached the
>>> surefire report with this.
>>>
>>
>> Hi Vijitha,
>>
>> I think you did this on a clean repo ? Can you try running all 200+
>> integration tests and check, instead of running only those two ?
>>
>>
>>>
>>>
>>> Regards,
>>>
>>>
>>> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara wrote:
>>>
 Had an issue with the build, Mail @Dev "Platform build error".


 On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga 
 wrote:

>
>
> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando 
> wrote:
>
>> Hi Vijitha/Subash,
>>
>> Any update on this?
>>
>
> Vijitha was building this on a clean repo. Vijitha , were you able
> to reproduce this ?
>
>
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara 
>> wrote:
>>
>>> I'm looking into this.
>>>
>>> Regards,
>>>
>>> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando <
>>> sen...@wso2.com> wrote:
>>>
 Hi Subash, Vijitha,

 Please test this on a clean M2 repo, and before you start to
 compile edit the POM in the integration tests for G-Reg and make 
 sure you
 enable the excluded tests. If we can reproduce this issue, it 
 shouldn't be
 hard figure out how this broke.

 Thanks,
 Senaka.


 On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando <
 sen...@wso2.com> wrote:

> Hi all,
>
> I have moved it. The new issue can be accessed from
> https://wso2.org/jira/browse/CARBON-12758, and also the old
> issue ID.
>
> Thanks,
> Senaka.
>
>
> On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
> same...@wso2.com> wrote:
>
>> +1. Senaka, please create these issues under CARBON project
>> as L1s. Otherwise, its hard to track these stuff.
>>
>>  Thanks,
>> Sameera.
>>
>> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
>> chari...@wso2.com> wrote:
>>
>>> Hi Senaka,
>>> Should not these failures reported as CARBON jira instead of
>>> product specific JIRA? Have we changed our process of reporting 
>>> JIRAs in C4
>>> release? Or am I missing something?
>>>
>>> Thanks,
>>> Charitha
>>>
>>>
>>> On Friday, March 30, 2012, Senaka Fernando wrote:

[Dev] Next build at 10.00pm(IST) 4th April

[Dimuthu Leelarathne]

Hi all,

We'll be triggering next build at 10.00pm IST.

thanks,
dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] Next build at 10.00pm(IST) 4th April

[Dimuthu Leelarathne]

Please get your fixes in.

On Wed, Apr 4, 2012 at 5:45 PM, Dimuthu Leelarathne wrote:

> Hi all,
>
> We'll be triggering next build at 10.00pm IST.
>
> thanks,
> dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>


-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] Next ESB version?

[Hiranya Jayathilaka]

The only new features we have are:

1. SAP transport with full IDocs support and experimental BAPI support
2. Mediation library support
3. API versioning support
4. Endpoint unification
5. EJB mediator
6. MSMQ support
7. Cloud connectors - LinkedIn, Twitter, SFDC (experimental)
8. XPath 2.0 support (experimental)

We can hopefully squeeze in the message relay stuff too. Other than that
there's a bunch of improvements and rewrites we have done, but technically
they don't count as new features. Does this justify a 4.5?

Thanks,
Hiranya

On Wed, Apr 4, 2012 at 4:46 PM, Paul Fremantle  wrote:

> I think this sounds like a 4.5.
>
> Paul
>
>
> On 4 April 2012 12:02, Isabelle Mauny  wrote:
>
>> All,
>>
>> We are adding quite a few features to this release, as per latest plan on
>> GDocs. Doesn't that justify a 4.5 ?
>>
>> Isabelle.
>>  --
>> Isabelle Mauny
>> Director, Product Management; WSO2, Inc.;  http://wso2.com/
>> email: isabe...@wso2.com  - mobile: +34 616050684
>>
>> On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:
>>
>>
>>
>> On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka wrote:
>>>
 Hi all,

 We still haven't decided on version for next ESB release which is based
 on carbon 4.0.0.

 Latest released ESB version is 4.0.3 and next release will not have
 huge changes to consider as 5.0.0.
 I'm thinking about 4.[1-5].0

 How about 4.1.0?
>>>
>>
>> +1
>>
>> Thanks,
>> Hiranya
>>
>>
>>>
>>>
 WDYT?

 --
 Thanks,
 Miyuru

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


>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Associate Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 71 536 4128
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>> ___
>> 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
>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Tribes clustering is broken in jdk1.7

[Charitha Kankanamge]

After removing xboot and impl.prefix entries from wso2server.bat i was able
to start the cluster on windows. Thanks Azeez.

/Charitha

On Wed, Apr 4, 2012 at 4:10 PM, Afkham Azeez  wrote:

> Can you remove that xbootjar and impl.prefix entries in wso2server.sh and
> retry?
>
>
> On Wed, Apr 4, 2012 at 3:59 PM, Charitha Kankanamge wrote:
>
>> java.net.SocketException: bad argument for SO_REUSEADDR;
>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Next ESB version?

[Isabelle Mauny]

Yes for me.
--
Isabelle Mauny
Director, Product Management; WSO2, Inc.;  http://wso2.com/
email: isabe...@wso2.com - mobile: +34 616050684

On Apr 4, 2012, at 3:11 PM, Hiranya Jayathilaka wrote:

> The only new features we have are:
> 
> 1. SAP transport with full IDocs support and experimental BAPI support
> 2. Mediation library support
> 3. API versioning support
> 4. Endpoint unification
> 5. EJB mediator
> 6. MSMQ support
> 7. Cloud connectors - LinkedIn, Twitter, SFDC (experimental)
> 8. XPath 2.0 support (experimental)
> 
> We can hopefully squeeze in the message relay stuff too. Other than that 
> there's a bunch of improvements and rewrites we have done, but technically 
> they don't count as new features. Does this justify a 4.5?
> 
> Thanks,
> Hiranya
> 
> On Wed, Apr 4, 2012 at 4:46 PM, Paul Fremantle  wrote:
> I think this sounds like a 4.5.
> 
> Paul
> 
> 
> On 4 April 2012 12:02, Isabelle Mauny  wrote:
> All,
> 
> We are adding quite a few features to this release, as per latest plan on 
> GDocs. Doesn't that justify a 4.5 ? 
> 
> Isabelle.
> --
> Isabelle Mauny
> Director, Product Management; WSO2, Inc.;  http://wso2.com/
> email: isabe...@wso2.com - mobile: +34 616050684
> 
> On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:
> 
>> 
>> 
>> On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:
>> 
>> 
>> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka  wrote:
>> Hi all,
>> 
>> We still haven't decided on version for next ESB release which is based on 
>> carbon 4.0.0.
>> 
>> Latest released ESB version is 4.0.3 and next release will not have huge 
>> changes to consider as 5.0.0.
>> I'm thinking about 4.[1-5].0
>> 
>> How about 4.1.0? 
>> 
>> +1
>> 
>> Thanks,
>> Hiranya
>>  
>>  
>> WDYT?
>> 
>> -- 
>> Thanks,
>> Miyuru
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
>> 
>> 
>> 
>> -- 
>> Kasun Indrasiri
>> Associate Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>> 
>> cell: +94 71 536 4128
>> Blog : http://kasunpanorama.blogspot.com/
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> 
>> 
>> 
>> 
>> -- 
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>> ___
>> 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
> 
> 
> 
> 
> -- 
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
> 
> UK: +44 207 096 0336
> US: +1 646 595 7614
> 
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
> 
> wso2.com Lean Enterprise Middleware
> 
> Disclaimer: This communication may contain privileged or other confidential 
> information and is intended exclusively for the addressee/s. If you are not 
> the intended recipient/s, or believe that you may have received this 
> communication in error, please reply to the sender indicating that fact and 
> delete the copy you received and in addition, you should not print, copy, 
> retransmit, disseminate, or otherwise use the information contained in this 
> communication. Internet communications cannot be guaranteed to be timely, 
> secure, error or virus-free. The sender does not accept liability for any 
> errors or omissions.
> 
> 
> 
> 
> -- 
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com

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

Re: [Dev] Tribes clustering is broken in jdk1.7

[Afkham Azeez]

These entries seem to be having issues on JDK7. Removing this will
reintroduce the reverse DNS lookup timeout issue on networks that do not
have reverse DNS setup, at least on JDK 6.

On Wed, Apr 4, 2012 at 7:34 PM, Charitha Kankanamge wrote:

> After removing xboot and impl.prefix entries from wso2server.bat i was
> able to start the cluster on windows. Thanks Azeez.
>
> /Charitha
>
> On Wed, Apr 4, 2012 at 4:10 PM, Afkham Azeez  wrote:
>
>> Can you remove that xbootjar and impl.prefix entries in wso2server.sh and
>> retry?
>>
>>
>> On Wed, Apr 4, 2012 at 3:59 PM, Charitha Kankanamge wrote:
>>
>>> java.net.SocketException: bad argument for SO_REUSEADDR;
>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Next build at 10.00pm(IST) 4th April

[Afkham Azeez]

Why are we manually triggering builds?

On Wed, Apr 4, 2012 at 5:45 PM, Dimuthu Leelarathne wrote:

> Hi all,
>
> We'll be triggering next build at 10.00pm IST.
>
> thanks,
> dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Afkham Azeez]

On Wed, Apr 4, 2012 at 5:23 PM, Senaka Fernando  wrote:

> Hi Subash, Vijitha,
>
> If possible also try to find the ordering of this on Bamboo and when we
> build. I have a feeling that Bamboo is running this in some other order.
>

The order in which tests are executed should not determine the outcome of
the test, ideally. However, if you want to order tests, you can use the
"dependsOn" attribute of the @Test annotation.

>
> Thanks,
> Senaka.
>
>
> On Wed, Apr 4, 2012 at 2:00 PM, Vijitha Kumara  wrote:
>
>> > Schema Test has excluded not from the pom but from the test class
>> itself by removing annotations.
>>
>> wasn't aware of that, will do as suggested.
>>
>> On Wed, Apr 4, 2012 at 1:55 PM, Senaka Fernando  wrote:
>>
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga wrote:
>>>


 On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando wrote:

> Hi Vijitha,
>
> It should include 233 test cases, IIRC, and you will have to uncomment
> the ones that are excluded before you build.
>

 Schema Test has excluded not from the pom but from the test class
 itself by removing annotations. Seems that is the one missing which has 3,4
 test cases.

>>>
>>> Oh, that's not done right who ever did that, :(..
>>>
>>>
  I have refactored it and excluded from the pom.

>>>
>>> Great.
>>>

 Vijitha, take an up in the integration module, and then remove all
 excluded stuff locally and build again. Then you'll get #233.
 BTW, I also able to build all the tests on a full svn up.

>>>
>>> +1
>>>
>>> Thanks,
>>> Senaka.
>>>


> Thanks,
> Senaka.
>
>
> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara wrote:
>
>> > I think you did this on a clean repo ? Can you try running all 200+
>> integration tests and check, instead of running only those two ?
>>
>> Initial build also contained all the 230 tests in GReg as the report
>> indicates.
>>
>> But I'm now trying with including all other products as well to see
>> whether it makes any difference.
>>
>> Regards,
>>
>> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara wrote:
>>>
 All,

 All the tests related to these two classes passed. Attached the
 surefire report with this.

>>>
>>> Hi Vijitha,
>>>
>>> I think you did this on a clean repo ? Can you try running all 200+
>>> integration tests and check, instead of running only those two ?
>>>
>>>


 Regards,


 On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara wrote:

> Had an issue with the build, Mail @Dev "Platform build error".
>
>
> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga  > wrote:
>
>>
>>
>> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando 
>> wrote:
>>
>>> Hi Vijitha/Subash,
>>>
>>> Any update on this?
>>>
>>
>> Vijitha was building this on a clean repo. Vijitha , were you
>> able to reproduce this ?
>>
>>
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara >> > wrote:
>>>
 I'm looking into this.

 Regards,

 On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando <
 sen...@wso2.com> wrote:

> Hi Subash, Vijitha,
>
> Please test this on a clean M2 repo, and before you start to
> compile edit the POM in the integration tests for G-Reg and make 
> sure you
> enable the excluded tests. If we can reproduce this issue, it 
> shouldn't be
> hard figure out how this broke.
>
> Thanks,
> Senaka.
>
>
> On Fri, Mar 30, 2012 at 8:12 PM, Senaka Fernando <
> sen...@wso2.com> wrote:
>
>> Hi all,
>>
>> I have moved it. The new issue can be accessed from
>> https://wso2.org/jira/browse/CARBON-12758, and also the old
>> issue ID.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Fri, Mar 30, 2012 at 7:53 PM, Sameera Jayasoma <
>> same...@wso2.com> wrote:
>>
>>> +1. Senaka, please create these issues under CARBON project
>>> as L1s. Otherwise, its hard to track these stuff.
>>>
>>>  Thanks,
>>> Sameera.
>>>
>>> On Fri, Mar 30, 2012 at 7:10 PM, Charitha Kankanamge <
>>> chari...@wso2.com> wrote:
>>>
>>>

[Dev] Sonar - somebody introduced a Blocker today

[Afkham Azeez]

http://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-kernel?severity=BLOCKER#

Also, the critical count has increased despite the effort some of us have
been putting in to reduce it.

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sonar - somebody introduced a Blocker today

[Afkham Azeez]

Sorry false alarm. A Sonar admin has now enabled the "Sonar way with
FindBugs" profile, which has more compliance rules, hence the bug count has
increased.


On Wed, Apr 4, 2012 at 8:31 PM, Afkham Azeez  wrote:

>
> http://wso2.org/sonar/drilldown/violations/org.wso2.carbon:carbon-kernel?severity=BLOCKER#
>
> Also, the critical count has increased despite the effort some of us have
> been putting in to reduce it.
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Getting javax.activation from the JDK

[Isuru Suriarachchi]

Hi all,

Currently we get the javax.activation package from the following artifact
and it comes through axiom.


javax.activation
activation


But with the CXF integration, I found that this implementation of
javax.activation doesn't work for CXF and it only works with the API and
the implementation provided by the JDK. So I removed the javax.activation
export from axiom and took it from the JDK. And also I tested Axis2 MTOM
support after this change and it worked fine.

I'm going to commit this change and if you find any issue which is caused
by this change, please let me know. Basically if some bundle is in
INSTALLED state and when you try to start it if you see the following
error, please let me know..

osgi> start 156
org.osgi.framework.BundleException: The bundle
"org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156]" could
not be resolved. Reason: Missing Constraint: Import-Package:
javax.activation; version="[1.1.0,2.0.0)"
 at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
 at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

You can get this fixed by adding the following config into the particular
bundle..


javax.activation.*;version="[0.0.0, 1.0.0)"


I fixed all such bundles I found. But there can be more..

Thanks,
~Isuru

-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

[Dev] Potential bug in OSGiBundleDeployer.java

[Afkham Azeez]

Sameera,
Sonar found the following code segment (
http://wso2.org/sonar/drilldown/violations/2?&rule=findbugs%3ADB_DUPLICATE_SWITCH_CLAUSES&rule_sev=CRITICAL&severity=CRITICAL#
).

   public void bundleChanged(BundleEvent event) {
Bundle bundle = event.getBundle();

switch (event.getType()) {
case BundleEvent.STARTED:
if (context.getBundle() != bundle) {
registry.register(event.getBundle());
}
break;

case BundleEvent.STOPPED:
if (context.getBundle() != bundle) {
registry.register(event.getBundle());
}
break;
}
}

As can be seen, for bot STARTED & STOPPED events, we
call  registry.register(event.getBundle()). Is this correct?

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Potential bug in ProvisioningUtils.java

[Afkham Azeez]

Pradeep,
Please check and verify
http://wso2.org/sonar/drilldown/violations/2?&rule=findbugs%3ADB_DUPLICATE_BRANCHES&rule_sev=CRITICAL&severity=CRITICAL#

-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Potential bug in ProvisioningUtils.java

[Pradeep Fernando]

Hi,

I think, it is a TODO (TODO: comment is there). Developer hasn't
implemented the show latest functionality.

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

Re: [Dev] Potential bug in ProvisioningUtils.java

[Afkham Azeez]

Weren't you the last person to modify that code?

On Wed, Apr 4, 2012 at 9:45 PM, Pradeep Fernando  wrote:

> Hi,
>
> I think, it is a TODO (TODO: comment is there). Developer hasn't
> implemented the show latest functionality.
>
> --Pradeep.
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Subash Chaturanga]

On Wed, Apr 4, 2012 at 8:20 PM, Afkham Azeez  wrote:

>
>
> On Wed, Apr 4, 2012 at 5:23 PM, Senaka Fernando  wrote:
>
>> Hi Subash, Vijitha,
>>
>> If possible also try to find the ordering of this on Bamboo and when we
>> build. I have a feeling that Bamboo is running this in some other order.
>>
>
Senaka, I don't think it is a defined order. We can order a set of tests by
adding dependencies (which we already does in GReg testng stuff), and other
than those, AFAIK for testng, its a set of 200+ individual pieces to run
randomly. BTW, is $subject hits in builder machine ?


>
>
The order in which tests are executed should not determine the outcome of
> the test, ideally. However, if you want to order tests, you can use the
> "dependsOn" attribute of the @Test annotation.
>

Yes Azeez, we already using that only in necessary places. For instance in
service test cases the edit service test depends on add service test and
etc.

Senaka, If order really matters (which is a possible in this case), there
is only *one way to overcome this issue (which will make sure there will be
no failures occur based on the ordering in future.), that is to add
dependencies to each and every methods within each test case (then this
will be similar to the JUnit test class behavior). Because GReg didn't face
such random failures in JUnit time. WDYT ?

Thanks
.

>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Apr 4, 2012 at 2:00 PM, Vijitha Kumara  wrote:
>>
>>> > Schema Test has excluded not from the pom but from the test class
>>> itself by removing annotations.
>>>
>>> wasn't aware of that, will do as suggested.
>>>
>>> On Wed, Apr 4, 2012 at 1:55 PM, Senaka Fernando  wrote:
>>>


 On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga wrote:

>
>
> On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando wrote:
>
>> Hi Vijitha,
>>
>> It should include 233 test cases, IIRC, and you will have to
>> uncomment the ones that are excluded before you build.
>>
>
> Schema Test has excluded not from the pom but from the test class
> itself by removing annotations. Seems that is the one missing which has 
> 3,4
> test cases.
>

 Oh, that's not done right who ever did that, :(..


>  I have refactored it and excluded from the pom.
>

 Great.

>
> Vijitha, take an up in the integration module, and then remove all
> excluded stuff locally and build again. Then you'll get #233.
> BTW, I also able to build all the tests on a full svn up.
>

 +1

 Thanks,
 Senaka.

>
>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara wrote:
>>
>>> > I think you did this on a clean repo ? Can you try running all
>>> 200+ integration tests and check, instead of running only those two ?
>>>
>>> Initial build also contained all the 230 tests in GReg as the report
>>> indicates.
>>>
>>> But I'm now trying with including all other products as well to see
>>> whether it makes any difference.
>>>
>>> Regards,
>>>
>>> On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga 
>>> wrote:
>>>


 On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara wrote:

> All,
>
> All the tests related to these two classes passed. Attached the
> surefire report with this.
>

 Hi Vijitha,

 I think you did this on a clean repo ? Can you try running all 200+
 integration tests and check, instead of running only those two ?


>
>
> Regards,
>
>
> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara 
> wrote:
>
>> Had an issue with the build, Mail @Dev "Platform build error".
>>
>>
>> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga <
>> sub...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando >> > wrote:
>>>
 Hi Vijitha/Subash,

 Any update on this?

>>>
>>> Vijitha was building this on a clean repo. Vijitha , were you
>>> able to reproduce this ?
>>>
>>>

 Thanks,
 Senaka.


 On Sun, Apr 1, 2012 at 8:10 PM, Vijitha Kumara <
 viji...@wso2.com> wrote:

> I'm looking into this.
>
> Regards,
>
> On Fri, Mar 30, 2012 at 8:33 PM, Senaka Fernando <
> sen...@wso2.com> wrote:
>
>> Hi Subash, Vijitha,
>>
>> Please test this on a clean M2 repo, and before you start to
>> compile edit the POM in the integration tests for G-Reg and make 
>> sure y

Re: [Dev] Getting javax.activation from the JDK

[Afkham Azeez]

This WILL break a lot of stuff. Please don't commit this at this stage. Can
you please delay this commit and run a full platform build first?

Thanks
Azeez

On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi  wrote:

> Hi all,
>
> Currently we get the javax.activation package from the following artifact
> and it comes through axiom.
>
> 
> javax.activation
> activation
> 
>
> But with the CXF integration, I found that this implementation of
> javax.activation doesn't work for CXF and it only works with the API and
> the implementation provided by the JDK. So I removed the javax.activation
> export from axiom and took it from the JDK. And also I tested Axis2 MTOM
> support after this change and it worked fine.
>
> I'm going to commit this change and if you find any issue which is caused
> by this change, please let me know. Basically if some bundle is in
> INSTALLED state and when you try to start it if you see the following
> error, please let me know..
>
> osgi> start 156
> org.osgi.framework.BundleException: The bundle
> "org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156]" could
> not be resolved. Reason: Missing Constraint: Import-Package:
> javax.activation; version="[1.1.0,2.0.0)"
>  at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
>  at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
>
> You can get this fixed by adding the following config into the particular
> bundle..
>
> 
> javax.activation.*;version="[0.0.0, 1.0.0)"
> 
>
> I fixed all such bundles I found. But there can be more..
>
> Thanks,
> ~Isuru
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Next ESB version?

[Dushan Abeyruwan]

Hi
  By looking at the amount of features to be included with next release  I
would probably say ESB 5.0 will be more satiable, but ESB 4.5, not bad but
it will be my second choice

cheers;
Dushan

On Wed, Apr 4, 2012 at 7:44 PM, Isabelle Mauny  wrote:

> Yes for me.
>
> --
> Isabelle Mauny
> Director, Product Management; WSO2, Inc.;  http://wso2.com/
> email: isabe...@wso2.com  - mobile: +34 616050684
>
> On Apr 4, 2012, at 3:11 PM, Hiranya Jayathilaka wrote:
>
> The only new features we have are:
>
> 1. SAP transport with full IDocs support and experimental BAPI support
> 2. Mediation library support
> 3. API versioning support
> 4. Endpoint unification
> 5. EJB mediator
> 6. MSMQ support
> 7. Cloud connectors - LinkedIn, Twitter, SFDC (experimental)
> 8. XPath 2.0 support (experimental)
>
> We can hopefully squeeze in the message relay stuff too. Other than that
> there's a bunch of improvements and rewrites we have done, but technically
> they don't count as new features. Does this justify a 4.5?
>
> Thanks,
> Hiranya
>
> On Wed, Apr 4, 2012 at 4:46 PM, Paul Fremantle  wrote:
>
>> I think this sounds like a 4.5.
>>
>> Paul
>>
>>
>> On 4 April 2012 12:02, Isabelle Mauny  wrote:
>>
>>> All,
>>>
>>> We are adding quite a few features to this release, as per latest plan
>>> on GDocs. Doesn't that justify a 4.5 ?
>>>
>>> Isabelle.
>>>  --
>>> Isabelle Mauny
>>> Director, Product Management; WSO2, Inc.;  http://wso2.com/
>>> email: isabe...@wso2.com  - mobile: +34 616050684
>>>
>>> On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:
>>>
>>>
>>>
>>> On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri  wrote:
>>>


 On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka wrote:

> Hi all,
>
> We still haven't decided on version for next ESB release which is
> based on carbon 4.0.0.
>
> Latest released ESB version is 4.0.3 and next release will not have
> huge changes to consider as 5.0.0.
> I'm thinking about 4.[1-5].0
>
> How about 4.1.0?

>>>
>>> +1
>>>
>>> Thanks,
>>> Hiranya
>>>
>>>


> WDYT?
>
> --
> Thanks,
> Miyuru
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Kasun Indrasiri
 Associate Technical Lead
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 71 536 4128
 Blog : http://kasunpanorama.blogspot.com/

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


>>>
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Associate Technical Lead;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>> ___
>>> 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
>>>
>>>
>>
>>
>> --
>> Paul Fremantle
>> CTO and Co-Founder, WSO2
>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>
>> UK: +44 207 096 0336
>> US: +1 646 595 7614
>>
>> blog: http://pzf.fremantle.org
>> twitter.com/pzfreo
>> p...@wso2.com
>>
>> wso2.com Lean Enterprise Middleware
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, retransmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Products > #28 has FAILED (1 tests failed). Change made by sumedha.

[Subash Chaturanga]

On Tue, Apr 3, 2012 at 11:54 AM, Senaka Fernando  wrote:

> Hi all,
>
> Thanks for creating this issue. We are recompiling the entire trunk on a
> clean repo, which the builder does not do; and will double check on these
> issues. Srinath, it has to connect to the internet to do a schema import
> from URL (we have disabled file URLs and we can't enable that just to run a
> test).
>
> Anyway this test just failed only once and I was able to uncover the
> actual reason as to why this would have failed.
>
> Assert.assertEquals(2, schemas.length);
>
> and, the length was three. This clearly means that there were 3 schemas on
> the registry when we expected there to be 2. Now, the reason for this is an
> issue of ordering tests and clean-up,
>

What do you mean by clean-up(I mean clean up what) ? . I did a search and
found there are 2, 3 other places that uses the same schema
(purchasing.xsd).
If this is a threading issue, using three dummy xsds (which have 3
different target name spaces)  should avoid this ? isn't it ?

Also regarding the WSDLTestCase failure we have along with a handler test
failure, that WSDLTest  also using the BizService.wsdl which has the
dependency on the very same purchasing.xsd.


> and I believe I was initially correct with my assumption that Bamboo did
> things differently or did not clean-up properly. We can look into this and
> sort this out leisurely.
>
> Thanks,
> Senaka.
>
>
> On Tue, Apr 3, 2012 at 8:57 AM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> On Tue, Apr 3, 2012 at 8:54 AM, Charith Wickramarachchi
>>  wrote:
>> >
>> >
>> > On Tue, Apr 3, 2012 at 8:52 AM, Selvaratnam Uthaiyashankar
>> >  wrote:
>> >>
>> >> On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
>> >>  wrote:
>> >> > Hi Senaka ,
>> >> >
>> >> > Last night I commented out this test case and triggered a build
>> starting
>> >> > from Kernel. Please find the Blocker created for this in [1]
>> >> >
>> >> > [1]https://wso2.org/jira/browse/REGISTRY-718
>> >>
>> >> Charith,
>> >>
>> >> This issue should go to Carbon JIRA. Only new features and roadmap
>> >> items should go to product specific Jira.
>> >
>> >
>> > Noted. Will follow this guideline in the future. Sorry for the
>> confusion.
>>
>> No worries. I have already moved the issue [1].
>>
>> Shankar
>>
>> [1] https://wso2.org/jira/browse/CARBON-12774
>>
>> >
>> > thanks,
>> > Charith
>> >>
>> >>
>> >>
>> >> Shankar
>> >>
>> >>
>> >> >
>> >> >
>> >> > thanks,
>> >> > Charith
>> >> >
>> >> > On Tue, Apr 3, 2012 at 2:50 AM, Senaka Fernando 
>> wrote:
>> >> >>
>> >> >> Hi Dimuthu,
>> >> >>
>> >> >> If you checked on the latest packs, the test is passing on Bamboo
>> right
>> >> >> now. This should be an intermittent connection issue (or something
>> >> >> related)
>> >> >> when fetching the schemas.
>> >> >>
>> >> >> Thanks,
>> >> >> Senaka.
>> >> >>
>> >> >>
>> >> >> On Mon, Apr 2, 2012 at 11:02 PM, Dimuthu Leelarathne
>> >> >> 
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi,
>> >> >>>
>> >> >>> Please have a look at this and provide a solution. If you can't
>> find a
>> >> >>> proper solution soon, let's comment out the test case and create a
>> L1
>> >> >>> for
>> >> >>> it.
>> >> >>>
>> >> >>> thanks,
>> >> >>> dimuthu
>> >> >>>
>> >> >>>
>> >> >>> On Mon, Apr 2, 2012 at 2:31 PM, Afkham Azeez 
>> wrote:
>> >> 
>> >>  Just got through the test code, and think about the cases in which
>> >>  this
>> >>  assertion failure can occur. Don't be hasty to blame Bamboo. If
>> there
>> >>  are
>> >>  threading issues, they may manifest on some environments but not
>> >>  others.
>> >> 
>> >> 
>> >>  On Mon, Apr 2, 2012 at 2:15 PM, Senaka Fernando 
>> >>  wrote:
>> >> >
>> >> > Hi Pradeep,
>> >> >
>> >> > It is not intermittent. But, how is this not reproducible
>> locally?
>> >> > And,
>> >> > how did this just start happening without any changes to the
>> code?
>> >> > Subash/Vijitha are working on a build of the whole platform on a
>> >> > clean repo.
>> >> > We'll be able to make a decision on the reliability of Bamboo
>> after
>> >> > that.
>> >> >
>> >> > Thanks,
>> >> > Senaka.
>> >> >
>> >> > On Mon, Apr 2, 2012 at 2:11 PM, Pradeep Fernando <
>> prad...@wso2.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> we had a config issue in bamboo. This is not intermittent.
>> Someone
>> >> >> has
>> >> >> to fix it. Yes bamboo is reliable.
>> >> >>
>> >> >> --Pradeep
>> >> >>
>> >> >> ___
>> >> >> Dev mailing list
>> >> >> Dev@wso2.org
>> >> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Senaka Fernando
>> >> > Product Manager - WSO2 Governance Registry;
>> >> > Associate Technical Lead; WSO2 Inc.; http://wso2.com
>> >> > Member; Apache Software Foundation; htt

Re: [Dev] Potential bug in ProvisioningUtils.java

[Pradeep Fernando]

On Wed, Apr 4, 2012 at 9:47 PM, Afkham Azeez  wrote:

> Weren't you the last person to modify that code?
>
> hmm... looks like its me. I did this during equinox migration. (porting to
new p2-api). I will have a look.

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Products > #28 has FAILED (1 tests failed). Change made by sumedha.

[Afkham Azeez]

Senaka, Bamboo doesn't do anything differently. It is dumb & just calls
Maven. What you are seeing is an issue in the tests.

--
Afkham Azeez
Sent from my phone
On Apr 3, 2012 11:55 AM, "Senaka Fernando"  wrote:

> Hi all,
>
> Thanks for creating this issue. We are recompiling the entire trunk on a
> clean repo, which the builder does not do; and will double check on these
> issues. Srinath, it has to connect to the internet to do a schema import
> from URL (we have disabled file URLs and we can't enable that just to run a
> test).
>
> Anyway this test just failed only once and I was able to uncover the
> actual reason as to why this would have failed.
>
> Assert.assertEquals(2, schemas.length);
>
> and, the length was three. This clearly means that there were 3 schemas on
> the registry when we expected there to be 2. Now, the reason for this is an
> issue of ordering tests and clean-up, and I believe I was initially correct
> with my assumption that Bamboo did things differently or did not clean-up
> properly. We can look into this and sort this out leisurely.
>
> Thanks,
> Senaka.
>
> On Tue, Apr 3, 2012 at 8:57 AM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> On Tue, Apr 3, 2012 at 8:54 AM, Charith Wickramarachchi
>>  wrote:
>> >
>> >
>> > On Tue, Apr 3, 2012 at 8:52 AM, Selvaratnam Uthaiyashankar
>> >  wrote:
>> >>
>> >> On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
>> >>  wrote:
>> >> > Hi Senaka ,
>> >> >
>> >> > Last night I commented out this test case and triggered a build
>> starting
>> >> > from Kernel. Please find the Blocker created for this in [1]
>> >> >
>> >> > [1]https://wso2.org/jira/browse/REGISTRY-718
>> >>
>> >> Charith,
>> >>
>> >> This issue should go to Carbon JIRA. Only new features and roadmap
>> >> items should go to product specific Jira.
>> >
>> >
>> > Noted. Will follow this guideline in the future. Sorry for the
>> confusion.
>>
>> No worries. I have already moved the issue [1].
>>
>> Shankar
>>
>> [1] https://wso2.org/jira/browse/CARBON-12774
>>
>> >
>> > thanks,
>> > Charith
>> >>
>> >>
>> >>
>> >> Shankar
>> >>
>> >>
>> >> >
>> >> >
>> >> > thanks,
>> >> > Charith
>> >> >
>> >> > On Tue, Apr 3, 2012 at 2:50 AM, Senaka Fernando 
>> wrote:
>> >> >>
>> >> >> Hi Dimuthu,
>> >> >>
>> >> >> If you checked on the latest packs, the test is passing on Bamboo
>> right
>> >> >> now. This should be an intermittent connection issue (or something
>> >> >> related)
>> >> >> when fetching the schemas.
>> >> >>
>> >> >> Thanks,
>> >> >> Senaka.
>> >> >>
>> >> >>
>> >> >> On Mon, Apr 2, 2012 at 11:02 PM, Dimuthu Leelarathne
>> >> >> 
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi,
>> >> >>>
>> >> >>> Please have a look at this and provide a solution. If you can't
>> find a
>> >> >>> proper solution soon, let's comment out the test case and create a
>> L1
>> >> >>> for
>> >> >>> it.
>> >> >>>
>> >> >>> thanks,
>> >> >>> dimuthu
>> >> >>>
>> >> >>>
>> >> >>> On Mon, Apr 2, 2012 at 2:31 PM, Afkham Azeez 
>> wrote:
>> >> 
>> >>  Just got through the test code, and think about the cases in which
>> >>  this
>> >>  assertion failure can occur. Don't be hasty to blame Bamboo. If
>> there
>> >>  are
>> >>  threading issues, they may manifest on some environments but not
>> >>  others.
>> >> 
>> >> 
>> >>  On Mon, Apr 2, 2012 at 2:15 PM, Senaka Fernando 
>> >>  wrote:
>> >> >
>> >> > Hi Pradeep,
>> >> >
>> >> > It is not intermittent. But, how is this not reproducible
>> locally?
>> >> > And,
>> >> > how did this just start happening without any changes to the
>> code?
>> >> > Subash/Vijitha are working on a build of the whole platform on a
>> >> > clean repo.
>> >> > We'll be able to make a decision on the reliability of Bamboo
>> after
>> >> > that.
>> >> >
>> >> > Thanks,
>> >> > Senaka.
>> >> >
>> >> > On Mon, Apr 2, 2012 at 2:11 PM, Pradeep Fernando <
>> prad...@wso2.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> we had a config issue in bamboo. This is not intermittent.
>> Someone
>> >> >> has
>> >> >> to fix it. Yes bamboo is reliable.
>> >> >>
>> >> >> --Pradeep
>> >> >>
>> >> >> ___
>> >> >> Dev mailing list
>> >> >> Dev@wso2.org
>> >> >> http://wso2.org/cgi-bin/mailman/listinfo/dev
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Senaka Fernando
>> >> > Product Manager - WSO2 Governance Registry;
>> >> > Associate Technical Lead; WSO2 Inc.; http://wso2.com
>> >> > Member; Apache Software Foundation; http://apache.org
>> >> >
>> >> > E-mail: senaka AT wso2.com
>> >> > P: +1 408 754 7388; ext: 51736; M: +94 77 322 1818
>> >> > Linked-In: http://linkedin.com/in/senakafernando
>> >> >
>> >> > Lean . Enterprise . Middleware
>> >> >
>> >> 
>> >> 
>> >> 
>> >>  --
>> >>  Afkham A

Re: [Dev] Old jars in BRS

[Ishara Karunarathna]

Hi,

I changed the version 2 to 6, and it build fine.

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

[Dev] sonar-profile in platform/pom.xml

[Kathiravelu Pradeeban]

Hi Maheshika and others,
Is Sonar-profile defined in platform/pom.xml used somewhere? I notice, it
has "core" defined as a module, which doesn't exist. Is that intentional?


  sonar-profile
  

   bamboo
   sonar

  
  
*core
components
*  



Regards,
Pradeeban.

-- 
Kathiravelu Pradeeban.
Software Engineer.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Products > #28 has FAILED (1 tests failed). Change made by sumedha.

[Senaka Fernando]

Hi all,

It probably is an issue with the tests, but, the problem is that we can't
reproduce them locally in our setups for some reason (its either the JDK
version, either the type of machine or something) that introduces some
randomness. This is why I was concerned about cleaning up a lot, just to
ensure that Bamboo does exactly what we generally do in the build or
whether it does something different.

Thanks,
Senaka.

On Wed, Apr 4, 2012 at 5:45 PM, Afkham Azeez  wrote:

> Senaka, Bamboo doesn't do anything differently. It is dumb & just calls
> Maven. What you are seeing is an issue in the tests.
>
> --
> Afkham Azeez
> Sent from my phone
> On Apr 3, 2012 11:55 AM, "Senaka Fernando"  wrote:
>
>> Hi all,
>>
>> Thanks for creating this issue. We are recompiling the entire trunk on a
>> clean repo, which the builder does not do; and will double check on these
>> issues. Srinath, it has to connect to the internet to do a schema import
>> from URL (we have disabled file URLs and we can't enable that just to run a
>> test).
>>
>> Anyway this test just failed only once and I was able to uncover the
>> actual reason as to why this would have failed.
>>
>> Assert.assertEquals(2, schemas.length);
>>
>> and, the length was three. This clearly means that there were 3 schemas
>> on the registry when we expected there to be 2. Now, the reason for this is
>> an issue of ordering tests and clean-up, and I believe I was initially
>> correct with my assumption that Bamboo did things differently or did not
>> clean-up properly. We can look into this and sort this out leisurely.
>>
>> Thanks,
>> Senaka.
>>
>> On Tue, Apr 3, 2012 at 8:57 AM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> On Tue, Apr 3, 2012 at 8:54 AM, Charith Wickramarachchi
>>>  wrote:
>>> >
>>> >
>>> > On Tue, Apr 3, 2012 at 8:52 AM, Selvaratnam Uthaiyashankar
>>> >  wrote:
>>> >>
>>> >> On Tue, Apr 3, 2012 at 8:50 AM, Charith Wickramarachchi
>>> >>  wrote:
>>> >> > Hi Senaka ,
>>> >> >
>>> >> > Last night I commented out this test case and triggered a build
>>> starting
>>> >> > from Kernel. Please find the Blocker created for this in [1]
>>> >> >
>>> >> > [1]https://wso2.org/jira/browse/REGISTRY-718
>>> >>
>>> >> Charith,
>>> >>
>>> >> This issue should go to Carbon JIRA. Only new features and roadmap
>>> >> items should go to product specific Jira.
>>> >
>>> >
>>> > Noted. Will follow this guideline in the future. Sorry for the
>>> confusion.
>>>
>>> No worries. I have already moved the issue [1].
>>>
>>> Shankar
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-12774
>>>
>>> >
>>> > thanks,
>>> > Charith
>>> >>
>>> >>
>>> >>
>>> >> Shankar
>>> >>
>>> >>
>>> >> >
>>> >> >
>>> >> > thanks,
>>> >> > Charith
>>> >> >
>>> >> > On Tue, Apr 3, 2012 at 2:50 AM, Senaka Fernando 
>>> wrote:
>>> >> >>
>>> >> >> Hi Dimuthu,
>>> >> >>
>>> >> >> If you checked on the latest packs, the test is passing on Bamboo
>>> right
>>> >> >> now. This should be an intermittent connection issue (or something
>>> >> >> related)
>>> >> >> when fetching the schemas.
>>> >> >>
>>> >> >> Thanks,
>>> >> >> Senaka.
>>> >> >>
>>> >> >>
>>> >> >> On Mon, Apr 2, 2012 at 11:02 PM, Dimuthu Leelarathne
>>> >> >> 
>>> >> >> wrote:
>>> >> >>>
>>> >> >>> Hi,
>>> >> >>>
>>> >> >>> Please have a look at this and provide a solution. If you can't
>>> find a
>>> >> >>> proper solution soon, let's comment out the test case and create
>>> a L1
>>> >> >>> for
>>> >> >>> it.
>>> >> >>>
>>> >> >>> thanks,
>>> >> >>> dimuthu
>>> >> >>>
>>> >> >>>
>>> >> >>> On Mon, Apr 2, 2012 at 2:31 PM, Afkham Azeez 
>>> wrote:
>>> >> 
>>> >>  Just got through the test code, and think about the cases in
>>> which
>>> >>  this
>>> >>  assertion failure can occur. Don't be hasty to blame Bamboo. If
>>> there
>>> >>  are
>>> >>  threading issues, they may manifest on some environments but not
>>> >>  others.
>>> >> 
>>> >> 
>>> >>  On Mon, Apr 2, 2012 at 2:15 PM, Senaka Fernando >> >
>>> >>  wrote:
>>> >> >
>>> >> > Hi Pradeep,
>>> >> >
>>> >> > It is not intermittent. But, how is this not reproducible
>>> locally?
>>> >> > And,
>>> >> > how did this just start happening without any changes to the
>>> code?
>>> >> > Subash/Vijitha are working on a build of the whole platform on a
>>> >> > clean repo.
>>> >> > We'll be able to make a decision on the reliability of Bamboo
>>> after
>>> >> > that.
>>> >> >
>>> >> > Thanks,
>>> >> > Senaka.
>>> >> >
>>> >> > On Mon, Apr 2, 2012 at 2:11 PM, Pradeep Fernando <
>>> prad...@wso2.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> Hi,
>>> >> >>
>>> >> >> we had a config issue in bamboo. This is not intermittent.
>>> Someone
>>> >> >> has
>>> >> >> to fix it. Yes bamboo is reliable.
>>> >> >>
>>> >> >> --Pradeep
>>> >> >>
>>> >> >> ___
>>> >> >> Dev mailing list
>>> >> >> Dev@wso2

[Dev] [maven-antrun-plugin:1.7] Parameter tasks is deprecated, use target instead

[Kathiravelu Pradeeban]

Hi,
$Subject is yet another best practice. In product pom's, we are still using
, instead of .
Will commit these changes to the product profiles. Just updating the list
for a record.

   
org.apache.maven.plugins
maven-antrun-plugin
1.1


   ...

*
* ...
*  
*





-- 
Kathiravelu Pradeeban.
Software Engineer.
Cloud Technologies Team.
WSO2 Inc.

Blog: [Llovizna] http://kkpradeeban.blogspot.com/
M: +94 776 477 976


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

[Dev] [Bamboo-Build] WSO2 Carbon > Orbit > #71 was SUCCESSFUL

[Bamboo]

---
WSO2 Carbon > Orbit > #71 was successful.
---
This build was manually triggered by BambooBuilder.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONKERNELBUILD-71/



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting javax.activation from the JDK

[Isuru Suriarachchi]

On Wed, Apr 4, 2012 at 9:50 PM, Afkham Azeez  wrote:

> This WILL break a lot of stuff. Please don't commit this at this stage.
> Can you please delay this commit and run a full platform build first?


No I fixed all breaks. I've already ran a full build up to AS without any
issue. Even if we find issues related to this, it will be very easy to fix.
So I think this won't cause any problems. WDYT??

Thanks,
~Isuru


>
> Thanks
> Azeez
>
> On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi  wrote:
>
>> Hi all,
>>
>> Currently we get the javax.activation package from the following artifact
>> and it comes through axiom.
>>
>> 
>> javax.activation
>> activation
>> 
>>
>> But with the CXF integration, I found that this implementation of
>> javax.activation doesn't work for CXF and it only works with the API and
>> the implementation provided by the JDK. So I removed the javax.activation
>> export from axiom and took it from the JDK. And also I tested Axis2 MTOM
>> support after this change and it worked fine.
>>
>> I'm going to commit this change and if you find any issue which is caused
>> by this change, please let me know. Basically if some bundle is in
>> INSTALLED state and when you try to start it if you see the following
>> error, please let me know..
>>
>> osgi> start 156
>> org.osgi.framework.BundleException: The bundle
>> "org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156]" could
>> not be resolved. Reason: Missing Constraint: Import-Package:
>> javax.activation; version="[1.1.0,2.0.0)"
>>  at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
>>
>> You can get this fixed by adding the following config into the particular
>> bundle..
>>
>> 
>> javax.activation.*;version="[0.0.0, 1.0.0)"
>> 
>>
>> I fixed all such bundles I found. But there can be more..
>>
>> Thanks,
>> ~Isuru
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

Re: [Dev] Next ESB version?

[Hiranya Jayathilaka]

I don't see any significant additions to call this 5.0. Let's go with 4.5.

Thanks,
Hiranya

On Wed, Apr 4, 2012 at 9:53 PM, Dushan Abeyruwan  wrote:

> Hi
>   By looking at the amount of features to be included with next release  I
> would probably say ESB 5.0 will be more satiable, but ESB 4.5, not bad but
> it will be my second choice
>
> cheers;
> Dushan
>
>
> On Wed, Apr 4, 2012 at 7:44 PM, Isabelle Mauny  wrote:
>
>> Yes for me.
>>
>>  --
>> Isabelle Mauny
>> Director, Product Management; WSO2, Inc.;  http://wso2.com/
>> email: isabe...@wso2.com  - mobile: +34 616050684
>>
>> On Apr 4, 2012, at 3:11 PM, Hiranya Jayathilaka wrote:
>>
>> The only new features we have are:
>>
>> 1. SAP transport with full IDocs support and experimental BAPI support
>> 2. Mediation library support
>> 3. API versioning support
>> 4. Endpoint unification
>> 5. EJB mediator
>> 6. MSMQ support
>> 7. Cloud connectors - LinkedIn, Twitter, SFDC (experimental)
>> 8. XPath 2.0 support (experimental)
>>
>> We can hopefully squeeze in the message relay stuff too. Other than that
>> there's a bunch of improvements and rewrites we have done, but technically
>> they don't count as new features. Does this justify a 4.5?
>>
>> Thanks,
>> Hiranya
>>
>> On Wed, Apr 4, 2012 at 4:46 PM, Paul Fremantle  wrote:
>>
>>> I think this sounds like a 4.5.
>>>
>>> Paul
>>>
>>>
>>> On 4 April 2012 12:02, Isabelle Mauny  wrote:
>>>
 All,

 We are adding quite a few features to this release, as per latest plan
 on GDocs. Doesn't that justify a 4.5 ?

 Isabelle.
  --
 Isabelle Mauny
 Director, Product Management; WSO2, Inc.;  http://wso2.com/
 email: isabe...@wso2.com  - mobile: +34 616050684

 On Apr 4, 2012, at 9:57 AM, Hiranya Jayathilaka wrote:



 On Wed, Apr 4, 2012 at 11:09 AM, Kasun Indrasiri wrote:

>
>
> On Tue, Apr 3, 2012 at 3:06 PM, Miyuru Wanninayaka wrote:
>
>> Hi all,
>>
>> We still haven't decided on version for next ESB release which is
>> based on carbon 4.0.0.
>>
>> Latest released ESB version is 4.0.3 and next release will not have
>> huge changes to consider as 5.0.0.
>> I'm thinking about 4.[1-5].0
>>
>> How about 4.1.0?
>

 +1

 Thanks,
 Hiranya


>
>
>> WDYT?
>>
>> --
>> Thanks,
>> Miyuru
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Associate Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Hiranya Jayathilaka
 Associate Technical Lead;
 WSO2 Inc.;  http://wso2.org
 E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
 Blog: http://techfeast-hiranya.blogspot.com
 ___
 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


>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> p...@wso2.com
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>>
>>
>>
>> --
>> Hiranya Jayathilaka
>> Associate Technical Lead;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Dushan Abeyruwan
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http:

Re: [Dev] Class loading issues when deploying JAXWS webapps in latest AS

[Isuru Suriarachchi]

Hi Charitha,

I ran a full build and ran all JAX-WS samples on AS. All are working on
Linux + JDK 1.6. I'll try the samples on JDK 1.7. That should be the issue
here..

Thanks,
~Isuru

On Wed, Apr 4, 2012 at 1:12 PM, Isuru Suriarachchi  wrote:

> I'll have a look into this..
>
> Thanks,
> ~Isuru
>
> On Wed, Apr 4, 2012 at 10:26 AM, Yumani Ranaweera  wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 9:43 AM, Yumani Ranaweera  wrote:
>>
>>>
>>>
>>> On Tue, Apr 3, 2012 at 10:46 PM, Charitha Kankanamge 
>>> wrote:
>>>
 Btw, I'm on windows.
>>>
>>>
>>>
>>> Getting the same exceptions in Ubuntu also.
>>
>>
>>
>> But its only async_jaxws that failed for me. jaxrs_basic worked and
>> only failure was this [1].
>>
>> [1] - https://wso2.org/jira/browse/CARBON-12809
>>
>> -Yumani
>>
>>
>>>
>>> Thanks,
>>> Yumani
>>>
>>>
>>>
>>>
>>> --
>>> Yumani Ranaweera
>>> Associate Technical Lead - QA
>>> WSO2, Inc. - http://wso2.org
>>>
>>> Email : yum...@wso2.com
>>> Cell: +94 077 7795242
>>> Blog   : http://yumani.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Yumani Ranaweera
>> Associate Technical Lead - QA
>> WSO2, Inc. - http://wso2.org
>>
>> Email : yum...@wso2.com
>> Cell: +94 077 7795242
>> Blog   : http://yumani.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>


-- 
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/

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

[Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #156 has FAILED (1 tests failed). Change made by kasung, charith and dimuthul.

[Bamboo]

---
WSO2 Carbon > Kernel > #156 failed.
---
This build was manually triggered by BambooBuilder.
1/2793 tests failed.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-CARBONCOREKERNELBUILD-156/


--
Failing Jobs
--
  - Default Job (Default Stage): 1 of 2793 tests failed.


--
Code Changes
--
kasung (124748):

>Fixing the issue in data-services. This fix was suggested by PrabathA.
>
>

charith (124731):

>adding shanshot repos

dimuthul (124733):

>Fixing Carbon CARBON-10640
>
>



--
Tests
--
New Test Failures (1)
   - ServerRestartTestCase: Server restart

--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting javax.activation from the JDK

[Afkham Azeez]

Please run all product builds with integration tests. We have just one more
day before the break

--
Afkham Azeez
Sent from my phone
On Apr 4, 2012 10:39 PM, "Isuru Suriarachchi"  wrote:

>
>
> On Wed, Apr 4, 2012 at 9:50 PM, Afkham Azeez  wrote:
>
>> This WILL break a lot of stuff. Please don't commit this at this stage.
>> Can you please delay this commit and run a full platform build first?
>
>
> No I fixed all breaks. I've already ran a full build up to AS without any
> issue. Even if we find issues related to this, it will be very easy to fix.
> So I think this won't cause any problems. WDYT??
>
> Thanks,
> ~Isuru
>
>
>>
>> Thanks
>> Azeez
>>
>> On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi wrote:
>>
>>> Hi all,
>>>
>>> Currently we get the javax.activation package from the following
>>> artifact and it comes through axiom.
>>>
>>> 
>>> javax.activation
>>> activation
>>> 
>>>
>>> But with the CXF integration, I found that this implementation of
>>> javax.activation doesn't work for CXF and it only works with the API and
>>> the implementation provided by the JDK. So I removed the javax.activation
>>> export from axiom and took it from the JDK. And also I tested Axis2 MTOM
>>> support after this change and it worked fine.
>>>
>>> I'm going to commit this change and if you find any issue which is
>>> caused by this change, please let me know. Basically if some bundle is in
>>> INSTALLED state and when you try to start it if you see the following
>>> error, please let me know..
>>>
>>> osgi> start 156
>>> org.osgi.framework.BundleException: The bundle
>>> "org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156]" could
>>> not be resolved. Reason: Missing Constraint: Import-Package:
>>> javax.activation; version="[1.1.0,2.0.0)"
>>>  at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
>>> at
>>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
>>>
>>> You can get this fixed by adding the following config into the
>>> particular bundle..
>>>
>>> 
>>> javax.activation.*;version="[0.0.0, 1.0.0)"
>>> 
>>>
>>> I fixed all such bundles I found. But there can be more..
>>>
>>> Thanks,
>>> ~Isuru
>>>
>>> --
>>> Isuru Suriarachchi
>>> Technical Lead
>>> WSO2 Inc. http://wso2.com
>>> email : is...@wso2.com
>>> blog : http://isurues.wordpress.com/
>>>
>>> lean . enterprise . middleware
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Isuru Suriarachchi
> Technical Lead
> WSO2 Inc. http://wso2.com
> email : is...@wso2.com
> blog : http://isurues.wordpress.com/
>
> lean . enterprise . middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #156 has FAILED (1 tests failed). Change made by kasung, charith and dimuthul.

[Shammi Jayasinghe]

Hi Pradeep,

   This kernel build is failed due to an integration test failure. There
seems to be a problem in opening the port 9565. I have attached
the sure-fire report of that. Could you please have a look.

Thanks
Shammi

On Wed, Apr 4, 2012 at 11:31 PM, Bamboo  wrote:

>  [image: Failed]  WSO2 
> Carbon›
> Kernel›
> #156
> failed
>
> This build was manually triggered by 
> BambooBuilder
> .
>
> *1/2793* tests failed.
>   Failing 
> Jobs
> Job Duration Tests[image: Failed]  Default 
> Job
>  (Default
> Stage)  63 minutes  1 of 2793 failed  
> Logs|
> Artifacts
>  Code
> Changes
>   View
> all 4 code 
> changes
> kasung 
> Code reformatting
>
>  124752
> kasung
> Fixing the issue in data-services. This fix was suggested by PrabathA.
>
>  124748
> dimuthul
> Fixing Carbon 
> CARBON-10640
>
>  124733   1 more 
> changes…
> Tests
>   View
> full test 
> details
>1
> New Test Failures  Test Job ServerRestartTestCase 
> testServerRestart
>   Default
> Job
>  View
> Online
> | Add 
> Comments
>
> This message was sent by Atlassian 
> Bamboo
> .
>
> If you wish to stop receiving these emails edit your user 
> profileor
>  notify
> your 
> administrator
> .
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,*

Shammi Jayasinghe*
Senior Software Engineer; WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
---
Test set: TestSuite
---
Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 520.718 sec 
<<< FAILURE!
testServerRestart(org.wso2.carbon.integration.tests.ServerRestartTestCase)  
Time elapsed: 318.645 sec  <<< FAILURE!
java.lang.RuntimeException: Port 9565 is not open
at 
org.wso2.carbon.integration.framework.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:106)
at 
org.wso2.carbon.integration.framework.utils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:93)
at 
org.wso2.carbon.integration.framework.TestServerManager.startServer(TestServerManager.java:79)
at 
org.wso2.carbon.integration.tests.CarbonTestServerManager.startServer(CarbonTestServerManager.java:48)
at 
org.wso2.carbon.integration.tests.ServerRestartTestCase.startServerForRestartTest(ServerRestartTestCase.java:83)
at 
org.wso2.carbon.integration.tests.ServerRestartTestCase.testServerRestart(ServerRestartTestCase.java:65)

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

Re: [Dev] Getting javax.activation from the JDK

[Sameera Jayasoma]

HI Azeez,

We had an offline discussion on this. This is the best solution for the
problem that Isuru is facing. We should have done the same thing for the
javax.xml.soap packages.

Thanks,
Sameera.

On Thu, Apr 5, 2012 at 12:12 AM, Afkham Azeez  wrote:

> Please run all product builds with integration tests. We have just one
> more day before the break
>
> --
> Afkham Azeez
> Sent from my phone
> On Apr 4, 2012 10:39 PM, "Isuru Suriarachchi"  wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 9:50 PM, Afkham Azeez  wrote:
>>
>>> This WILL break a lot of stuff. Please don't commit this at this stage.
>>> Can you please delay this commit and run a full platform build first?
>>
>>
>> No I fixed all breaks. I've already ran a full build up to AS without any
>> issue. Even if we find issues related to this, it will be very easy to fix.
>> So I think this won't cause any problems. WDYT??
>>
>> Thanks,
>> ~Isuru
>>
>>
>>>
>>> Thanks
>>> Azeez
>>>
>>> On Wed, Apr 4, 2012 at 8:36 PM, Isuru Suriarachchi wrote:
>>>
 Hi all,

 Currently we get the javax.activation package from the following
 artifact and it comes through axiom.

 
 javax.activation
 activation
 

 But with the CXF integration, I found that this implementation of
 javax.activation doesn't work for CXF and it only works with the API and
 the implementation provided by the JDK. So I removed the javax.activation
 export from axiom and took it from the JDK. And also I tested Axis2 MTOM
 support after this change and it worked fine.

 I'm going to commit this change and if you find any issue which is
 caused by this change, please let me know. Basically if some bundle is in
 INSTALLED state and when you try to start it if you see the following
 error, please let me know..

 osgi> start 156
 org.osgi.framework.BundleException: The bundle
 "org.wso2.carbon.dataservices.fileupload.stub_4.0.0.SNAPSHOT [156]" could
 not be resolved. Reason: Missing Constraint: Import-Package:
 javax.activation; version="[1.1.0,2.0.0)"
  at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
 at
 org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
  at
 org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)

 You can get this fixed by adding the following config into the
 particular bundle..

 
 javax.activation.*;version="[0.0.0, 1.0.0)"
 

 I fixed all such bundles I found. But there can be more..

 Thanks,
 ~Isuru

 --
 Isuru Suriarachchi
 Technical Lead
 WSO2 Inc. http://wso2.com
 email : is...@wso2.com
 blog : http://isurues.wordpress.com/

 lean . enterprise . middleware


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


>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: **http://twitter.com/afkham_azeez*
>>> *
>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>> *
>>> *
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>
>>
>> --
>> Isuru Suriarachchi
>> Technical Lead
>> WSO2 Inc. http://wso2.com
>> email : is...@wso2.com
>> blog : http://isurues.wordpress.com/
>>
>> lean . enterprise . middleware
>>
>>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #156 has FAILED (1 tests failed). Change made by kasung, charith and dimuthul.

[Sameera Jayasoma]

Hi Shammi,

Can this be a bind exception? There might be some java processes running on
the same port.

Thanks,
Sameera.

On Thu, Apr 5, 2012 at 12:16 AM, Shammi Jayasinghe  wrote:

> Hi Pradeep,
>
>This kernel build is failed due to an integration test failure. There
> seems to be a problem in opening the port 9565. I have attached
> the sure-fire report of that. Could you please have a look.
>
> Thanks
> Shammi
>
> On Wed, Apr 4, 2012 at 11:31 PM, Bamboo  wrote:
>
>>  [image: Failed]  WSO2 
>> Carbon›
>> Kernel›
>> #156
>> failed
>>
>> This build was manually triggered by 
>> BambooBuilder
>> .
>>
>> *1/2793* tests failed.
>>   Failing 
>> Jobs
>> Job
>> Duration Tests[image: Failed]  Default 
>> Job
>>  (Default
>> Stage)  63 minutes  1 of 2793 failed  
>> Logs|
>> Artifacts
>>  Code
>> Changes
>>   View
>> all 4 code 
>> changes
>> kasung 
>> Code reformatting
>>
>>  124752
>> kasung
>> Fixing the issue in data-services. This fix was suggested by PrabathA.
>>
>>  124748
>> dimuthul
>> Fixing Carbon 
>> CARBON-10640
>>
>>  124733   1 more 
>> changes…
>> Tests
>>   View
>> full test 
>> details
>>1
>> New Test Failures   Test Job ServerRestartTestCase 
>> testServerRestart
>>   Default
>> Job
>>  View
>> Online
>> | Add 
>> Comments
>>
>> This message was sent by Atlassian 
>> Bamboo
>> .
>>
>> If you wish to stop receiving these emails edit your user 
>> profileor
>>  notify
>> your 
>> administrator
>> .
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>
>


-- 
Sameera Jayasoma
Technical Lead and Product Manager, WSO2 Carbon

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://tech.jayasoma.org

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #156 has FAILED (1 tests failed). Change made by kasung, charith and dimuthul.

[Shammi Jayasinghe]

On Thu, Apr 5, 2012 at 12:24 AM, Sameera Jayasoma  wrote:

> Hi Shammi,
>
> Can this be a bind exception? There might be some java processes running
> on the same port.
>

Hi Sameera,
 I also suspected that . But could not find any process binded on port
9565.

bamboo@db6237242:~/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1$
netstat -tulpn
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address   Foreign Address
State   PID/Program name
tcp0  0 127.0.0.1:250.0.0.0:*
LISTEN  -
tcp0  0 0.0.0.0:19840.0.0.0:*
LISTEN  -
tcp0  0 0.0.0.0:56660.0.0.0:*
LISTEN  -
tcp0  0 127.0.0.1:3306  0.0.0.0:*
LISTEN  -
tcp6   0  0 :::80   :::*
LISTEN  -
tcp6   0  0 :::42642:::*
LISTEN  7507/java
tcp6   0  0 ::: :::*
LISTEN  23729/java
tcp6   0  0 ::1:25  :::*
LISTEN  -
tcp6   0  0 :::1984 :::*
LISTEN  -
tcp6   0  0 66.240.237.242:54663:::*
LISTEN  23729/java
udp0  0 0.0.0.0:44811   0.0.0.0:*
-
udp0  0 0.0.0.0:45088   0.0.0.0:*
-
udp0  0 0.0.0.0:161 0.0.0.0:*
-
udp0  0 0.0.0.0:53530.0.0.0:*
-
udp6   0  0 :::54268
:::*7507/java
udp6   0  0 :::54441
:::*-
udp6   0  0 :::43720
:::*7507/java
udp6   0  0 :::5353
:::*-

Thanks
Shammi

>
> Thanks,
> Sameera.
>
>
> On Thu, Apr 5, 2012 at 12:16 AM, Shammi Jayasinghe wrote:
>
>> Hi Pradeep,
>>
>>This kernel build is failed due to an integration test failure. There
>> seems to be a problem in opening the port 9565. I have attached
>> the sure-fire report of that. Could you please have a look.
>>
>> Thanks
>> Shammi
>>
>> On Wed, Apr 4, 2012 at 11:31 PM, Bamboo  wrote:
>>
>>>  [image: Failed]  WSO2 
>>> Carbon›
>>> Kernel›
>>> #156
>>> failed
>>>
>>> This build was manually triggered by 
>>> BambooBuilder
>>> .
>>>
>>> *1/2793* tests failed.
>>>   Failing 
>>> Jobs
>>> Job
>>> Duration Tests[image: Failed]  Default 
>>> Job
>>>  (Default
>>> Stage)  63 minutes  1 of 2793 failed  
>>> Logs|
>>> Artifacts
>>>  Code
>>> Changes
>>>   View
>>> all 4 code 
>>> changes
>>> kasung 
>>> Code reformatting
>>>
>>>  124752
>>> kasung
>>> Fixing the issue in data-services. This fix was suggested by PrabathA.
>>>
>>>  124748
>>> dimuthul
>>> Fixing Carbon 
>>> CARBON-10640
>>>
>>>  124733   1 more 
>>> changes…
>>> Tests
>>>   View
>>> full test 
>>> details
>>>1
>>> New Test Failures   Test Job ServerRestartTestCase 
>>> testServerRestart
>>>   Default
>>> Job
>>>  View
>>> Online
>>> | Add 
>>> Comments
>>>
>>> This message was sent by Atlassian 
>>> Bamboo

Re: [Dev] [API Manager] Async support when approval is in place

[Prabath Siriwardena]

Hi Paul,

>From the next Carbon release we have the support for adding handlers
for privilege actions.[e.g. Add User, Change Permission, Remove User] - and
the corresponding services need to declare it's privilege actions - so
anyone can write a handler to handle/control the privilege action. If it is
'Add User' - initiate a work flow from the handler and add the user to the
system after the approval.

+1 for the suggestion - and I guess we can do this with same above
approach..

Will add this to the API Management road map for post 1.0...

Thanks & regards,
-Prabath

On Tue, Apr 3, 2012 at 1:54 PM, Paul Fremantle  wrote:

> At some point we need to have a hook out to an approval process to
> "approve" API keys. For example, I apply, but we want to vet users, or
> integrate into a marketing campaign and BANT qualify before we approve
> their use of our APIs.
>
> When there is an approval process for an API key, there needs to be an
> async model to get the API Key back to the user.
> This should support two approaches:
> 1. Email the user the key (in an email that uses a template that can be
> modified)
> 2. The user should also be able to login and see their key. This should
> also apply to the case where they are issued immediately.
>
> In fact I think it might be better to always assume this is async. So if
> the approval is automatic, I would just get the email straight away.
>
> Paul
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> p...@wso2.com
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

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

Re: [Dev] FindBugs & Sonar on jaggery

[Samisa Abeysinghe]

I have fixed it to the point below, using Sonar way with FindBugs profile.

Need to do some code reviews where CC is high and NCSS is high.

Also, this code need loads of unit testing.
Violations
40 [image:
-2-green-small]
Rules compliance
97.4%[image:
2-green-small]

On Wed, Apr 4, 2012 at 5:16 AM, Samisa Abeysinghe  wrote:

> Folks,
>I have fixed loads of Sonar & FindBugs reported issues on Jaggery
> component.
>
>The code compiles but I might have broken some functionality here and
> there. This is due to lack of unit tests (there is no way I can verify the
> tests as there are no unit tests)
>
>In case functionality is broken, please talk to me, without reverting
> to buggy code again. This is because, I have fixed many serious
> issues including file closings not handled etc. I am still in the process
> of fixing.
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>  Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] BPEL Problem with pick activity

[Leslier López Nicot]

Hi all.

I'm designing a process with a Pick activity. This process invoke an 
asynchronous service, it obtain the response and use the pick to give an 
ok message or if 20 sec pass and we don´t have it send a timeout message.


The problem is that the process execute, invoke the asynchronous 
service, obtain the response correctly with the correlation set define, 
but the pick don´t execute the onMessage activity, and always do the 
onAlarm activity.


The correlation define in the wsdl consist in 2 propertyAlias, one with 
the initial request and one with the response of the asynchronous 
service. In the beginning of the process I initiate the correlation set, 
in the receive activity, I use the correlation set but the initiation is 
set to no. It works fine. Also in the onMessage of the Pick I use the 
same set with initiation set to no, but it doesn't seem to work correctly.




part=/"payload"/ propertyName=/"tns:correlatorProp"/>


/tns:input



part=/"payload"/ propertyName=/"tns:correlatorProp"/>


/ns1:nombre





10mo. ANIVERSARIO DE LA CREACION DE LA UNIVERSIDAD DE LAS CIENCIAS 
INFORMATICAS...
CONECTADOS AL FUTURO, CONECTADOS A LA REVOLUCION

http://www.uci.cu
http://www.facebook.com/universidad.uci
http://www.flickr.com/photos/universidad_uci___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] namespace mismatch require http://authentication.services.core.carbon.wso2.org found http://ws.apache.org/commons/ns/payload in API MGT login

[Sumedha Rubasinghe]

On a latest SVN up, I started getting following when trying to login to API
Mgt console.

[2012-04-05 01:39:58,910] ERROR - RPCMessageReceiver Exception occurred
while trying to invoke service method login
org.apache.axis2.AxisFault: namespace mismatch require
http://authentication.services.core.carbon.wso2.org found
http://ws.apache.org/commons/ns/payload
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:190)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)


Problem disappeared when I disabled "relay" module from axis2.xml as
explain in https://wso2.org/jira/browse/ESBJAVA-938 .
Any idea why this start appearing ?

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

[Dev] [Bamboo-Build] WSO2 Carbon > platform > #60 was SUCCESSFUL (with 1980 tests). Change made by 19 authors.

[Bamboo]

---
WSO2 Carbon > platform > #60 was successful.
---
This build was manually triggered by BambooBuilder.
1980 tests in total.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PLATFORM-60/


--
Code Changes
--
sanjeewa (124765):

>commiting ec2 independent autoscaler

sanjeewa (124749):

>commiting pom need to modify as in trunk

dimuthul (124755):

>fixing p2 repo generation by fixing/removing some feature versions



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] When shutting down a Carbon Server - java.lang.IndexOutOfBoundsException: Source does not fit in dest

[Sumedha Rubasinghe]

Getting bellow mentioned when shutting down a latest Carbon server. Any
pointers as to why?

[2012-04-05 03:24:42,366]  INFO - HttpCoreNIOSender HTTP Sender Shutdown
[2012-04-05 03:24:42,367] ERROR - CarbonServerManager Exception occurred
while shutting down listeners
java.lang.IndexOutOfBoundsException: Source does not fit in dest
at java.util.Collections.copy(Collections.java:531)
at
org.apache.axis2.engine.AxisConfiguration.getObserversList(AxisConfiguration.java:1316)
at
org.apache.synapse.transport.nhttp.HttpCoreNIOListener.destroy(HttpCoreNIOListener.java:456)
at
org.apache.axis2.engine.ListenerManager.destroy(ListenerManager.java:290)
at
org.wso2.carbon.core.init.CarbonServerManager.stopListenerManager(CarbonServerManager.java:631)

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

Re: [Dev] When shutting down a Carbon Server - java.lang.IndexOutOfBoundsException: Source does not fit in dest

[Senaka Fernando]

Hi Sumedha,

On Thu, Apr 5, 2012 at 3:26 AM, Sumedha Rubasinghe  wrote:

> Getting bellow mentioned when shutting down a latest Carbon server. Any
> pointers as to why?
>
> [2012-04-05 03:24:42,366]  INFO - HttpCoreNIOSender HTTP Sender Shutdown
> [2012-04-05 03:24:42,367] ERROR - CarbonServerManager Exception occurred
> while shutting down listeners
> java.lang.IndexOutOfBoundsException: Source does not fit in dest
> at java.util.Collections.copy(Collections.java:531)
> at
> org.apache.axis2.engine.AxisConfiguration.getObserversList(AxisConfiguration.java:1316)
> * at
> org.apache.synapse.transport.nhttp.HttpCoreNIOListener.destroy(HttpCoreNIOListener.java:456)
> *
>

Is this any carbon server or ESB?

Thanks,
Senaka.


> at
> org.apache.axis2.engine.ListenerManager.destroy(ListenerManager.java:290)
> at
> org.wso2.carbon.core.init.CarbonServerManager.stopListenerManager(CarbonServerManager.java:631)
>
> --
> /sumedha
> +94 773017743
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Senaka Fernando*
Product Manager - WSO2 Governance Registry;
Associate Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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

Re: [Dev] When shutting down a Carbon Server - java.lang.IndexOutOfBoundsException: Source does not fit in dest

[Dimuthu Leelarathne]

Hi all,

On Thu, Apr 5, 2012 at 3:26 AM, Sumedha Rubasinghe  wrote:

> Getting bellow mentioned when shutting down a latest Carbon server. Any
> pointers as to why?
>
> [2012-04-05 03:24:42,366]  INFO - HttpCoreNIOSender HTTP Sender Shutdown
> [2012-04-05 03:24:42,367] ERROR - CarbonServerManager Exception occurred
> while shutting down listeners
> java.lang.IndexOutOfBoundsException: Source does not fit in dest
> at java.util.Collections.copy(Collections.java:531)
> at
> org.apache.axis2.engine.AxisConfiguration.getObserversList(AxisConfiguration.java:1316)
> at
> org.apache.synapse.transport.nhttp.HttpCoreNIOListener.destroy(HttpCoreNIOListener.java:456)
> at
> org.apache.axis2.engine.ListenerManager.destroy(ListenerManager.java:290)
> at
> org.wso2.carbon.core.init.CarbonServerManager.stopListenerManager(CarbonServerManager.java:631)
>
>
This is a change done by me to Axis2 couple of days ago, and I committed
with all test cases passing and no build failures. I will check what is
happening.

thanks,
dimuthu


> --
> /sumedha
> +94 773017743
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] When shutting down a Carbon Server - java.lang.IndexOutOfBoundsException: Source does not fit in dest

[Sumedha Rubasinghe]

On Thu, Apr 5, 2012 at 4:28 AM, Senaka Fernando  wrote:

> Hi Sumedha,
>
> On Thu, Apr 5, 2012 at 3:26 AM, Sumedha Rubasinghe wrote:
>
>> Getting bellow mentioned when shutting down a latest Carbon server. Any
>> pointers as to why?
>>
>> [2012-04-05 03:24:42,366]  INFO - HttpCoreNIOSender HTTP Sender Shutdown
>> [2012-04-05 03:24:42,367] ERROR - CarbonServerManager Exception occurred
>> while shutting down listeners
>> java.lang.IndexOutOfBoundsException: Source does not fit in dest
>> at java.util.Collections.copy(Collections.java:531)
>> at
>> org.apache.axis2.engine.AxisConfiguration.getObserversList(AxisConfiguration.java:1316)
>> * at
>> org.apache.synapse.transport.nhttp.HttpCoreNIOListener.destroy(HttpCoreNIOListener.java:456)
>> *
>>
>
> Is this any carbon server or ESB?
>

Sorry.. should have been more precise. This is  API Mgt product with ESB
features installed.
/sumedha


>
> Thanks,
> Senaka.
>
>
>> at
>> org.apache.axis2.engine.ListenerManager.destroy(ListenerManager.java:290)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.stopListenerManager(CarbonServerManager.java:631)
>>
>> --
>> /sumedha
>> +94 773017743
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


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

Re: [Dev] [Architecture] API Manager - Pre alpha 1 available for download

[Sumedha Rubasinghe]

On Tue, Apr 3, 2012 at 11:35 AM, Afkham Azeez  wrote:

>
>
> On Tue, Apr 3, 2012 at 4:25 AM, Samisa Abeysinghe  wrote:
>
>>
>>
>> On Mon, Apr 2, 2012 at 8:38 AM, Sumedha Rubasinghe wrote:
>>
>>> Pre alpha 1 pack of WSO2 API Manager can be downloaded from -
>>> http://people.wso2.com/~sumedha/builds/am/02-04-2012/wso2am-1.0.0-SNAPSHOT.zip
>>>
>>> A README on how to test functionality is available inside
>>> samples/TwitterSearch (also available @
>>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/apimgt/modules/samples/TwitterSearch/README.txt
>>>  )
>>>
>>
>> 1. When will this work on Windows? In which milestone?
>> 2. What is the plan to fix the re-start steps mentioned in this README?
>> In which milestone?
>> 3. Why do I need ant? (copy libs I guess) Can we ship with Jars copied?
>> For the DB in samples, can we pre-ship an H2 DB populated?
>> 4. What does APIPopulator.sh do? It looks a back-box to me.
>>
>
> That name in camel case for an sh/bat file looks very ugly. Perhap
> api-populator.sh/bat?
>

Sorry Azeez. Saw this just now. We have packed and uploaded the next
distro. Will fix this on next pack.
/sumedha


>
>>
>>> We welcome feedback in the form of JIRA issues via
>>> https://wso2.org/jira/browse/APISTORE
>>>
>>
>> What version am I supposed to fix report issues against in this Jira?
>>
>>
>>>
>>> --
>>> API Team
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>
> *
> *
> *Lean . Enterprise . Middleware*
>
>


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

[Dev] API Manager 1.0.0-M2-RC1 available for download

[Sumedha Rubasinghe]

First release candidate of API Manager 1.0.0-M2 can be downloaded from
http://people.wso2.com/~sumedha/builds/am/04-04-2012/wso2am-1.0.0-M2-RC1.zip.

Major changes on this release are,
- In-line documentation content editing
- Global level 'My Subscription' listing
- Improvements to 'Add API' page
- Stabilization on underlying registry access for storage

We welcome feedback in the form of JIRA issues via
https://wso2.org/jira/browse/APISTORE
Please select '1.0.0-M2-RC1' as the effected version.

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

[Dev] [Bamboo-Build] WSO2 Carbon > P2-Repo > #23 was SUCCESSFUL. Change made by 13 authors.

[Bamboo]

---
WSO2 Carbon > P2-Repo > #23 was successful.
---
Code has been updated by denis, samisa, dimuthul, amilam, ranga, anjana, suho, 
madhuka, sanjeewa, chamara, isharak, suresh, nuwan.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-P2REPO-23/


--
Code Changes
--
sanjeewa (124749):

>commiting pom need to modify as in trunk

sanjeewa (124765):

>commiting ec2 independent autoscaler

dimuthul (124755):

>fixing p2 repo generation by fixing/removing some feature versions



--
This message is automatically generated by Atlassian Bamboo___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BackwardAssociationHandlerTestCase and WSDLTestCase are failing in G-Reg

[Vijitha Kumara]

Ideally, tests should not worry about any ordering of the run time engine
which invokes them as they should be independent of each other. The tests
involves multiple test methods (if any) need to be combined to form a
single unit of test(s) so that what ever ordering (or any context switching
etc...) would not interfere the result of the test.

Anyway I'm doing another build with the changes from Subash, let's see...

On Wed, Apr 4, 2012 at 9:48 PM, Subash Chaturanga  wrote:

>
>
> On Wed, Apr 4, 2012 at 8:20 PM, Afkham Azeez  wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 5:23 PM, Senaka Fernando  wrote:
>>
>>> Hi Subash, Vijitha,
>>>
>>> If possible also try to find the ordering of this on Bamboo and when we
>>> build. I have a feeling that Bamboo is running this in some other order.
>>>
>>
> Senaka, I don't think it is a defined order. We can order a set of tests
> by adding dependencies (which we already does in GReg testng stuff), and
> other than those, AFAIK for testng, its a set of 200+ individual pieces to
> run randomly. BTW, is $subject hits in builder machine ?
>
>
>>
>>
>  The order in which tests are executed should not determine the outcome of
>> the test, ideally. However, if you want to order tests, you can use the
>> "dependsOn" attribute of the @Test annotation.
>>
>
> Yes Azeez, we already using that only in necessary places. For instance in
> service test cases the edit service test depends on add service test and
> etc.
>
> Senaka, If order really matters (which is a possible in this case), there
> is only *one way to overcome this issue (which will make sure there will be
> no failures occur based on the ordering in future.), that is to add
> dependencies to each and every methods within each test case (then this
> will be similar to the JUnit test class behavior). Because GReg didn't face
> such random failures in JUnit time. WDYT ?
>
> Thanks
> .
>
>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Wed, Apr 4, 2012 at 2:00 PM, Vijitha Kumara  wrote:
>>>
 > Schema Test has excluded not from the pom but from the test class
 itself by removing annotations.

 wasn't aware of that, will do as suggested.

 On Wed, Apr 4, 2012 at 1:55 PM, Senaka Fernando wrote:

>
>
> On Wed, Apr 4, 2012 at 1:54 PM, Subash Chaturanga wrote:
>
>>
>>
>> On Wed, Apr 4, 2012 at 1:41 PM, Senaka Fernando wrote:
>>
>>> Hi Vijitha,
>>>
>>> It should include 233 test cases, IIRC, and you will have to
>>> uncomment the ones that are excluded before you build.
>>>
>>
>> Schema Test has excluded not from the pom but from the test class
>> itself by removing annotations. Seems that is the one missing which has 
>> 3,4
>> test cases.
>>
>
> Oh, that's not done right who ever did that, :(..
>
>
>>  I have refactored it and excluded from the pom.
>>
>
> Great.
>
>>
>> Vijitha, take an up in the integration module, and then remove all
>> excluded stuff locally and build again. Then you'll get #233.
>> BTW, I also able to build all the tests on a full svn up.
>>
>
> +1
>
> Thanks,
> Senaka.
>
>>
>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Wed, Apr 4, 2012 at 1:35 PM, Vijitha Kumara wrote:
>>>
 > I think you did this on a clean repo ? Can you try running all
 200+ integration tests and check, instead of running only those two ?

 Initial build also contained all the 230 tests in GReg as the
 report indicates.

 But I'm now trying with including all other products as well to see
 whether it makes any difference.

 Regards,

 On Tue, Apr 3, 2012 at 5:48 PM, Subash Chaturanga 
 wrote:

>
>
> On Tue, Apr 3, 2012 at 5:37 PM, Vijitha Kumara 
> wrote:
>
>> All,
>>
>> All the tests related to these two classes passed. Attached the
>> surefire report with this.
>>
>
> Hi Vijitha,
>
> I think you did this on a clean repo ? Can you try running all
> 200+ integration tests and check, instead of running only those two ?
>
>
>>
>>
>> Regards,
>>
>>
>> On Tue, Apr 3, 2012 at 8:52 AM, Vijitha Kumara 
>> wrote:
>>
>>> Had an issue with the build, Mail @Dev "Platform build error".
>>>
>>>
>>> On Tue, Apr 3, 2012 at 8:49 AM, Subash Chaturanga <
>>> sub...@wso2.com> wrote:
>>>


 On Tue, Apr 3, 2012 at 3:53 AM, Senaka Fernando <
 sen...@wso2.com> wrote:

> Hi Vijitha/Subash,
>
> Any update on this?
>

 Vijitha was building this on a clean repo. Vijitha , were you
>>

[Dev] Carbon 4.0.0 - Alpha2 packs

[Dimuthu Leelarathne]

Hi RMs,

Please smoke these packs available here. The revision number of the build
is 124767.

http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-37/artifact

We hope to release these packs as Carbon 4.0 Alpha2 within today.

thanks,
dimuthu

-- 
Dimuthu Leelarathne
Technical Lead

WSO2, Inc. (http://wso2.com)
email: dimut...@wso2.com

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

Re: [Dev] [Bamboo-Build] WSO2 Carbon > Kernel > #156 has FAILED (1 tests failed). Change made by kasung, charith and dimuthul.

[Charith Wickramarachchi]

If we look at the current way we have implemented our integration tests we
can't actually be sure Whether this is happening or not.
If we look at products integration test modules it contain many test cases.

So what they do is

1) Start server

2) Run test

3) Shutdown sever.

So within a product integration test phase this happens multiple times.


In Bamboo after each product build we run a script to kill the running
carbon processors. But still if some thing went wrong inside a given
integration test module that will still may leave running carbon processors
which will cause other tests to fail within the module.

So i think we have two options to Fix this properly

1) Have an Abstract Test which all the test classes will extend from which
will cleanup the carbon servers in the pre test condition (Each test case
will do a super call in their local test pre condition ) or some thing like
that.

2) Using testng  and force to run a before test suite action which will
cleanup running carbon processors. IIRC in testng.xml we can have some
thing like that.



thanks,
Charith


On Thu, Apr 5, 2012 at 12:28 AM, Shammi Jayasinghe  wrote:

>
>
> On Thu, Apr 5, 2012 at 12:24 AM, Sameera Jayasoma wrote:
>
>> Hi Shammi,
>>
>> Can this be a bind exception? There might be some java processes running
>> on the same port.
>>
>
> Hi Sameera,
>  I also suspected that . But could not find any process binded on port
> 9565.
>
> bamboo@db6237242:~/Bamboo-3.4/source-repository/build-dir/WSO2CARBON-CARBONCOREKERNELBUILD-JOB1$
> netstat -tulpn
> (Not all processes could be identified, non-owned process info
>  will not be shown, you would have to be root to see it all.)
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreign Address
> State   PID/Program name
> tcp0  0 127.0.0.1:250.0.0.0:*
> LISTEN  -
> tcp0  0 0.0.0.0:19840.0.0.0:*
> LISTEN  -
> tcp0  0 0.0.0.0:56660.0.0.0:*
> LISTEN  -
> tcp0  0 127.0.0.1:3306  0.0.0.0:*
> LISTEN  -
> tcp6   0  0 :::80   :::*
> LISTEN  -
> tcp6   0  0 :::42642:::*
> LISTEN  7507/java
> tcp6   0  0 ::: :::*
> LISTEN  23729/java
> tcp6   0  0 ::1:25  :::*
> LISTEN  -
> tcp6   0  0 :::1984 :::*
> LISTEN  -
> tcp6   0  0 66.240.237.242:54663:::*
> LISTEN  23729/java
> udp0  0 0.0.0.0:44811   0.0.0.0:*
> -
> udp0  0 0.0.0.0:45088   0.0.0.0:*
> -
> udp0  0 0.0.0.0:161 0.0.0.0:*
> -
> udp0  0 0.0.0.0:53530.0.0.0:*
> -
> udp6   0  0 :::54268
> :::*7507/java
> udp6   0  0 :::54441
> :::*-
> udp6   0  0 :::43720
> :::*7507/java
> udp6   0  0 :::5353
> :::*-
>
> Thanks
> Shammi
>
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Thu, Apr 5, 2012 at 12:16 AM, Shammi Jayasinghe wrote:
>>
>>> Hi Pradeep,
>>>
>>>This kernel build is failed due to an integration test failure. There
>>> seems to be a problem in opening the port 9565. I have attached
>>> the sure-fire report of that. Could you please have a look.
>>>
>>> Thanks
>>> Shammi
>>>
>>> On Wed, Apr 4, 2012 at 11:31 PM, Bamboo  wrote:
>>>
  [image: Failed]  WSO2 
 Carbon›
 Kernel›
 #156
 failed

 This build was manually triggered by 
 BambooBuilder
 .

 *1/2793* tests failed.
   Failing 
 Jobs
 Job
 Duration Tests[image: Failed]  Default 
 Job
  (Default
 Stage)  63 minutes  1 of 2793 failed  
 Logs|
 Artifacts
  Code
 Changes
   View
 all 4 code 
 changes
 kasung 
 Code reformatting

  124752
 kasung

[Dev] should change as

[Ajith Vitharana]

Hi all,

We have  enabled the resource *revisioning*  in registry xml.
But the parameter defined as  <*version*ResourcesOnChange>.



<*versioning*Properties>true
<*versioning*Comments>true
<*versioning*Tags>true
<*versioning*Ratings>true

/trunk/services/


<*version*ResourcesOnChange>true

Thanks
-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Another nhttp transport test failure

[Afkham Azeez]

---
Test set: TestSuite
---
Tests run: 10, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 358.11 sec
<<< FAILURE!
testWSDLRequest(org.wso2.esb.integration.nhttp.WSDLRequestTestCase)  Time
elapsed: 30.459 sec  <<< FAILURE!
org.apache.axis2.AxisFault: Read timed out
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
 at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:449)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:276)
 at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
 at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
 at
org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
at
org.wso2.esb.integration.ESBIntegrationTestCase.updateESBConfiguration(ESBIntegrationTestCase.java:253)
 at
org.wso2.esb.integration.ESBIntegrationTestCase.loadESBConfigurationFromClasspath(ESBIntegrationTestCase.java:202)
at
org.wso2.esb.integration.nhttp.WSDLRequestTestCase.testWSDLRequest(WSDLRequestTestCase.java:39)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
 at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:798)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:755)
 at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
 at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
at
org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
 at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
 at
org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
at
org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
 at
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
 at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
 at
org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
at
org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
 ... 45 more
testReturnServerIP(org.wso2.esb.integration.nhttp.ReturnServerIPTestCase)
 Time elapsed: 30.169 sec  <<< FAILURE!


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Comments for registry configurations in G-Reg.

[Ajith Vitharana]

Hi All,

We have following  configuration in registry.xml (G-Reg)

1) DB configuration
2) 18 handler configurations
3) Indexing configuration
4) Mounting configuration
5) Resource revisioning configuration
6) Static configurations

But we haven't added any comments describing those configurations . ??
I created L1 to fix this issue. https://wso2.org/jira/browse/CARBON-12840
-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94714631794


wso2registry
false
true
/


jdbc:h2:repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE;LOCK_TIMEOUT=6
wso2carbon
wso2carbon
org.h2.Driver
50
6
5




.*





.*





application/vnd.apache.synapse





application/vnd.wso2.esb





application/vnd.apache.axis2





application/vnd.wso2.wsas







/trunk/schemas/
	

/trunk/wsdls/
	

/trunk/policies/
	


application/wsdl+xml




application/wsdl+xml
application/xsd+xml
50


/trunk/schemas/


/trunk/wsdls/

	
application/vnd.wso2.governance-archive






dev
qa
live


application/vnd.wso2-service+xml







dev
qa
live


application/vnd.wso2-process+xml





application/vnd.wso2-sla+xml





Created
Tested
Deployed


application/vnd.wso2-smart-link





application/vnd.wso2-people+xml




	
/trunk/policies/
	

application/policy+xml






/trunk/schemas/


application/x-xsd+xml





application/vnd.wso2-hyperlink




application/vnd.wso2.endpoint

/trunk/endpoints/














300
60

/_system/local/repository/components/org.wso2.carbon.registry/indexing/lastaccesstime


















true
true
true
true

/trunk/services/

		
true

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

Re: [Dev] sonar-profile in platform/pom.xml

[Dushan Abeyruwan]

Hi
  Yes noted I hv removed it from my local setup, and you are correct we
will remove core module from the sonar profile in platform

cheers
Dushan


On Wed, Apr 4, 2012 at 10:21 PM, Kathiravelu Pradeeban
wrote:

> Hi Maheshika and others,
> Is Sonar-profile defined in platform/pom.xml used somewhere? I notice, it
> has "core" defined as a module, which doesn't exist. Is that intentional?
>
> 
>   sonar-profile
>   
> 
>bamboo
>sonar
> 
>   
>   
> *core
> components
> *  
> 
>
>
> Regards,
> Pradeeban.
>
> --
> Kathiravelu Pradeeban.
> Software Engineer.
> Cloud Technologies Team.
> WSO2 Inc.
>
> Blog: [Llovizna] http://kkpradeeban.blogspot.com/
> M: +94 776 477 976
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dushan Abeyruwan
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r124781 - in carbon/platform/trunk/products: apimgt/modules/distribution/product gs2/modules/distribution/product gs2/modules/distribution/service gs2/

[Sumedha Rubasinghe]

Pradeeban,
This fix broken API Mgt product build.
/sumedha

On Thu, Apr 5, 2012 at 2:30 AM,  wrote:

> Author: pradeeban
> Date: Wed Apr  4 17:00:28 2012
> New Revision: 124781
> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=124781
>
> Log:
> Fixing the maven3 warnings of gs2 and apimgt. These weren't found in the
> main-build, as they are not included in the products/pom.xml.
>
>
> Modified:
>
> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>   carbon/platform/trunk/products/gs2/modules/distribution/product/pom.xml
>   carbon/platform/trunk/products/gs2/modules/distribution/service/pom.xml
>
> carbon/platform/trunk/products/gs2/modules/integration/gs-integration-tests/pom.xml
>   carbon/platform/trunk/products/gs2/modules/p2-profile-gen/service/pom.xml
>
> Modified:
> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
> URL:
> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml?rev=124781&r1=124780&r2=124781&view=diff
>
> ==
> ---
> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>  (original)
> +++
> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>  Wed Apr  4 17:00:28 2012
> @@ -94,7 +94,7 @@
> run
> 
> 
> -
> +
>  value="target/docs-temp"/>
> 
> 
> @@ -148,52 +148,14 @@
> 
> 
> 
> -
> +
> 
> 
> -
> -
> -
> -
> -org.apache.maven.plugins
> -maven-site-plugin
> -3.0
> -   
> -
> -
> -org.apache.maven.plugins
> -maven-project-info-reports-plugin
> -2.4
> -
> -
> -
> -index
> -
> -
> -
> -
> -
> -
> -
> -
> -package
> -
> -site
> -
> -
> -
> -
> -
> -
> -org.apache.maven.plugins
> -maven-antrun-plugin
> -1.1
> -
> 
> clean_target
> install
> 
> -
> +
> 
>  dir="target/dependency-maven-plugin-markers"/>
> 
> @@ -201,21 +163,12 @@
> 
> 
> 
> -
> +
> 
> 
> run
> 
> 
> -
> -
> -
> -
> -org.apache.maven.plugins
> -maven-antrun-plugin
> -1.1
> -
> -
> 
> create-API-manager-database
> package
> @@ -223,7 +176,7 @@
> run
> 
> 
> -
> +
> 
> 
> 
> @@ -244,11 +197,42 @@
> 
>  message="# END
> "/>
> -
> +
> 
> 
> 
> +
> +
> +
> +org.apache.maven.plugins
> +maven-site-plugin
> +3.0
> +   
> +
> +
> +org.apache.maven.plugins
> +maven-project-info-reports-plugin
> +2.4
> +
> +
> +
> +index
> +
> +
> +
> +

Re: [Dev] Another nhttp transport test failure

[Hiranya Jayathilaka]

If this happens consistently then somebody has broken it. Can you send the
server logs?

On Thu, Apr 5, 2012 at 10:25 AM, Afkham Azeez  wrote:

>
> ---
> Test set: TestSuite
>
> ---
> Tests run: 10, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 358.11
> sec <<< FAILURE!
> testWSDLRequest(org.wso2.esb.integration.nhttp.WSDLRequestTestCase)  Time
> elapsed: 30.459 sec  <<< FAILURE!
> org.apache.axis2.AxisFault: Read timed out
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>  at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>  at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:449)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:276)
>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
>  at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>  at
> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
> at
> org.wso2.esb.integration.ESBIntegrationTestCase.updateESBConfiguration(ESBIntegrationTestCase.java:253)
>  at
> org.wso2.esb.integration.ESBIntegrationTestCase.loadESBConfigurationFromClasspath(ESBIntegrationTestCase.java:202)
> at
> org.wso2.esb.integration.nhttp.WSDLRequestTestCase.testWSDLRequest(WSDLRequestTestCase.java:39)
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
>  at
> com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
> at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
>  at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:798)
> at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:755)
>  at
> com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>  at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
> at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
>  at org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
> at
> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
>  at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
>  at
> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
> at
> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
>  at
> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
>  at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>  at
> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
> at
> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
>  ... 45 more
> testReturnServerIP(org.wso2.esb.integration.nhttp.ReturnServerIPTestCase)
>  Time elapsed: 30.169 sec  <<< FAILURE!
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
>


-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon 4.0.0 - Alpha2 packs

[Manjula Rathnayake]

Hi,

Regarding Stratos Manager, we get exceptions when trying to login using
created tenants. I have attached the error log.

Thank you.

On Thu, Apr 5, 2012 at 8:46 AM, Dimuthu Leelarathne wrote:

> Hi RMs,
>
> Please smoke these packs available here. The revision number of the build
> is 124767.
>
>
> http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PRODUCTS-JOB1-37/artifact
>
> We hope to release these packs as Carbon 4.0 Alpha2 within today.
>
> thanks,
> dimuthu
>
> --
> Dimuthu Leelarathne
> Technical Lead
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
>
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Manjula Rathnayaka
Software Engineer
WSO2, Inc.
Mobile:+94 77 743 1987
[2012-04-05 09:49:22,364]  INFO 
{org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator} -  
'admin' logged out at [2012-04-05 09:49:22,0364]
[2012-04-05 09:49:30,969]  INFO {org.apache.xml.security.signature.Reference} - 
 Verification successful for URI "#ojingnccfkhbkphhodheeobjdblafpaaekmgodhi"
[2012-04-05 09:49:31,228]  INFO 
{org.wso2.carbon.core.internal.permission.update.PermissionUpdater} -  
Permission cache updated for tenant 1
[2012-04-05 09:49:31,242] manj...@mb1.com [1] [WSO2 Stratos Manager] INFO 
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} -  
'manj...@mb1.com [1]' logged in at [2012-04-05 09:49:31,0242] from IP address 
SAML2 SSO Authentication
[2012-04-05 09:49:31,346] manj...@mb1.com [1] [WSO2 Stratos Manager] INFO 
{org.wso2.carbon.dashboard.dashboardpopulator.GadgetPopulator} -  Couldn't find 
a Dashboard XML at 
'/media/work/stratos/wso2stratos-manager-1.1.0-SNAPSHOT/repository/resources/dashboard/dashboard.xml'.
 Giving up dashboard population for tenant : 1
[2012-04-05 09:49:31,532]  INFO 
{org.wso2.carbon.core.multitenancy.TenantAxisConfigurator} -  Creating tenant 
AxisConfiguration for tenant: mb1.com[1]
[2012-04-05 09:49:31,534] @mb1.com [1] [WSO2 Stratos Manager]ERROR 
{org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager} -  
metafiles directory for services must exist.
[2012-04-05 09:49:31,534] @mb1.com [1] [WSO2 Stratos Manager]ERROR 
{org.wso2.carbon.core.persistence.PersistenceFactory} -  Error while 
initializing the ModulePersistenceManager instance
org.apache.axis2.AxisFault: metafiles directory for services must exist. May be 
AxisConfiguration does not have the repository url set.
at 
org.wso2.carbon.core.persistence.file.ServiceGroupFilePersistenceManager.(ServiceGroupFilePersistenceManager.java:55)
at 
org.wso2.carbon.core.persistence.PersistenceFactory.getServiceGroupFilePM(PersistenceFactory.java:130)
at 
org.wso2.carbon.security.deployment.SecurityDeploymentInterceptor.init(SecurityDeploymentInterceptor.java:148)
at 
org.wso2.carbon.security.deployment.SecurityDeploymentInterceptor$1.createdAxisConfiguration(SecurityDeploymentInterceptor.java:124)
at 
org.wso2.carbon.core.multitenancy.TenantAxisConfigurator.populateAxisConfiguration(TenantAxisConfigurator.java:286)
at 
org.wso2.carbon.core.multitenancy.TenantAxisConfigurator.populateAxisConfig(TenantAxisConfigurator.java:239)
at 
org.wso2.carbon.core.multitenancy.TenantAxisConfigurator.getAxisConfiguration(TenantAxisConfigurator.java:184)
at 
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
at 
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.createTenantConfigurationContext(TenantAxisUtils.java:286)
at 
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantConfigurationContext(TenantAxisUtils.java:121)
at 
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.getTenantAxisConfiguration(TenantAxisUtils.java:101)
at 
org.wso2.carbon.activation.module.ActivationHandler.invoke(ActivationHandler.java:87)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at 
org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
at 
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:67)
at javax.servlet.http.HttpServlet

Re: [Dev] When shutting down a Carbon Server - java.lang.IndexOutOfBoundsException: Source does not fit in dest

[Afkham Azeez]

This error can be seen while running ESB integration tests as well.

On Thu, Apr 5, 2012 at 3:26 AM, Sumedha Rubasinghe  wrote:

> Getting bellow mentioned when shutting down a latest Carbon server. Any
> pointers as to why?
>
> [2012-04-05 03:24:42,366]  INFO - HttpCoreNIOSender HTTP Sender Shutdown
> [2012-04-05 03:24:42,367] ERROR - CarbonServerManager Exception occurred
> while shutting down listeners
> java.lang.IndexOutOfBoundsException: Source does not fit in dest
> at java.util.Collections.copy(Collections.java:531)
> at
> org.apache.axis2.engine.AxisConfiguration.getObserversList(AxisConfiguration.java:1316)
> at
> org.apache.synapse.transport.nhttp.HttpCoreNIOListener.destroy(HttpCoreNIOListener.java:456)
> at
> org.apache.axis2.engine.ListenerManager.destroy(ListenerManager.java:290)
> at
> org.wso2.carbon.core.init.CarbonServerManager.stopListenerManager(CarbonServerManager.java:631)
>
> --
> /sumedha
> +94 773017743
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Commits] [Carbon-platform] svn commit r124781 - in carbon/platform/trunk/products: apimgt/modules/distribution/product gs2/modules/distribution/product gs2/modules/distribution/service gs2/

[Kasun Weranga]

Hi,

I reverted the changes that has been done for APIMGT
(apimgt/modules/distribution/product/pom.xml), since this gives some issues
after building the pack.

Thanks,
KasunW

On Thu, Apr 5, 2012 at 10:51 AM, Sumedha Rubasinghe wrote:

> Pradeeban,
> This fix broken API Mgt product build.
> /sumedha
>
> On Thu, Apr 5, 2012 at 2:30 AM,  wrote:
>
>> Author: pradeeban
>> Date: Wed Apr  4 17:00:28 2012
>> New Revision: 124781
>> URL: http://wso2.org/svn/browse/wso2?view=rev&revision=124781
>>
>> Log:
>> Fixing the maven3 warnings of gs2 and apimgt. These weren't found in the
>> main-build, as they are not included in the products/pom.xml.
>>
>>
>> Modified:
>>
>> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>>   carbon/platform/trunk/products/gs2/modules/distribution/product/pom.xml
>>   carbon/platform/trunk/products/gs2/modules/distribution/service/pom.xml
>>
>> carbon/platform/trunk/products/gs2/modules/integration/gs-integration-tests/pom.xml
>>
>> carbon/platform/trunk/products/gs2/modules/p2-profile-gen/service/pom.xml
>>
>> Modified:
>> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>> URL:
>> http://wso2.org/svn/browse/wso2/carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml?rev=124781&r1=124780&r2=124781&view=diff
>>
>> ==
>> ---
>> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>>  (original)
>> +++
>> carbon/platform/trunk/products/apimgt/modules/distribution/product/pom.xml
>>  Wed Apr  4 17:00:28 2012
>> @@ -94,7 +94,7 @@
>> run
>> 
>> 
>> -
>> +
>> > value="target/docs-temp"/>
>> 
>> 
>> @@ -148,52 +148,14 @@
>> 
>> 
>> 
>> -
>> +
>> 
>> 
>> -
>> -
>> -
>> -
>> -org.apache.maven.plugins
>> -maven-site-plugin
>> -3.0
>> -   
>> -
>> -
>> -org.apache.maven.plugins
>> -
>>  maven-project-info-reports-plugin
>> -2.4
>> -
>> -
>> -
>> -index
>> -
>> -
>> -
>> -
>> -
>> -
>> -
>> -
>> -package
>> -
>> -site
>> -
>> -
>> -
>> -
>> -
>> -
>> -org.apache.maven.plugins
>> -maven-antrun-plugin
>> -1.1
>> -
>> 
>> clean_target
>> install
>> 
>> -
>> +
>> 
>> > dir="target/dependency-maven-plugin-markers"/>
>> 
>> @@ -201,21 +163,12 @@
>> 
>> 
>> 
>> -
>> +
>> 
>> 
>> run
>> 
>> 
>> -
>> -
>> -
>> -
>> -org.apache.maven.plugins
>> -maven-antrun-plugin
>> -1.1
>> -
>> -
>> 
>> create-API-manager-database
>> package
>> @@ -223,7 +176,7 @@
>> run
>> 
>> 
>> -
>> +
>> 
>> > refid="maven.compile.classpath"/>
>> 
>> @@ -244,11 +197,42 @@
>> 
>> > message="#
>> END "/>
>> -
>> +
>> 
>> 
>> 
>> +
>> +
>> +
>> +org.apache.maven.plugins
>> +maven-site-plugin
>> +

Re: [Dev] Carbon 4.0.0 - Alpha2 packs

[Lalaji Sureshika]

Hi,

Regarding MS pack, I'm getting following PersistanceManager related
exceptions[1] for each samples during the server start up.And for each
mashup saving/uploading I'm getting same exceptions.However this exception
is different from the exception we got from the last time bamboo build MS
pack.


[1] [2012-04-05 11:57:21,781] ERROR -  Exception in persisting the
transaction admin/sudoku
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:883)
at
org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.commitTransaction(AbstractFilePersistenceManager.java:63)
at
org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:295)
at
org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:283)
at
org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:653)
at
org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:407)
at
org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:606)
at
org.wso2.carbon.mashup.jsservices.deployer.JSDeployer.deploy(JSDeployer.java:191)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
at
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:461)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:370)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:263)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2012-04-05 11:57:21,782] ERROR -  Unable to handle new service addition.
Service: admin/sudoku
org.wso2.carbon.core.persistence.PersistenceException: Exception in
persisting the transaction admin/sudoku
at
org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.handleExceptionWithRollback(AbstractFilePersistenceManager.java:286)
at
org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.commitTransaction(AbstractFilePersistenceManager.java:78)
at
org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:295)
at
org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:283)
at
org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:653)
at
org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:407)
at
org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:606)
at
org.wso2.carbon.mashup.jsservices.deployer.JSDeployer.deploy(JSDeployer.java:191)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
at
org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:461)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:370)
at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:263)
at
org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
at
org.eclipse.osgi.framework.intern

Re: [Dev] Another nhttp transport test failure

[Hiranya Jayathilaka]

Looks like Bamboo builds are running fine:
http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBON-PRODUCTS-38

The above completed just now.

Thanks,
Hiranya

On Thu, Apr 5, 2012 at 10:59 AM, Hiranya Jayathilaka wrote:

> If this happens consistently then somebody has broken it. Can you send the
> server logs?
>
>
> On Thu, Apr 5, 2012 at 10:25 AM, Afkham Azeez  wrote:
>
>>
>> ---
>> Test set: TestSuite
>>
>> ---
>> Tests run: 10, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 358.11
>> sec <<< FAILURE!
>> testWSDLRequest(org.wso2.esb.integration.nhttp.WSDLRequestTestCase)  Time
>> elapsed: 30.459 sec  <<< FAILURE!
>> org.apache.axis2.AxisFault: Read timed out
>> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>  at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
>> at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
>>  at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:449)
>> at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:276)
>>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
>>  at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
>>  at
>> org.wso2.carbon.mediation.configadmin.stub.ConfigServiceAdminStub.updateConfiguration(ConfigServiceAdminStub.java:1340)
>> at
>> org.wso2.esb.integration.ESBIntegrationTestCase.updateESBConfiguration(ESBIntegrationTestCase.java:253)
>>  at
>> org.wso2.esb.integration.ESBIntegrationTestCase.loadESBConfigurationFromClasspath(ESBIntegrationTestCase.java:202)
>> at
>> org.wso2.esb.integration.nhttp.WSDLRequestTestCase.testWSDLRequest(WSDLRequestTestCase.java:39)
>> Caused by: java.net.SocketTimeoutException: Read timed out
>> at java.net.SocketInputStream.socketRead0(Native Method)
>> at java.net.SocketInputStream.read(SocketInputStream.java:129)
>>  at
>> com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
>> at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
>>  at
>> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:798)
>> at
>> com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:755)
>>  at
>> com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
>> at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>>  at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
>> at
>> org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
>>  at
>> org.apache.commons.httpclient.HttpParser.readLine(HttpParser.java:106)
>> at
>> org.apache.commons.httpclient.HttpConnection.readLine(HttpConnection.java:1116)
>>  at
>> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.readLine(MultiThreadedHttpConnectionManager.java:1413)
>>  at
>> org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1973)
>> at
>> org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
>>  at
>> org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
>> at
>> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
>>  at
>> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>> at
>> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
>>  at
>> org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:621)
>> at
>> org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
>>  ... 45 more
>> testReturnServerIP(org.wso2.esb.integration.nhttp.ReturnServerIPTestCase)
>>  Time elapsed: 30.169 sec  <<< FAILURE!
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> Hiranya Jayathilaka
> Associate Technical Lead;
> WSO2 Inc.;  http://wso2.org
> E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>



-- 
Hiranya Jayathilaka
Associate Technical Lead;
WSO2 Inc.;  http://wso2.org
E-mail: hira...@wso2.com;  Mobile: +94 77 633 3491
Blog: http://techfeast-hirany

Re: [Dev] Carbon 4.0.0 - Alpha2 packs

[Kishanthan Thangarajah]

On Thu, Apr 5, 2012 at 12:04 PM, Lalaji Sureshika  wrote:

> Hi,
>
> Regarding MS pack, I'm getting following PersistanceManager related
> exceptions[1] for each samples during the server start up.And for each
> mashup saving/uploading I'm getting same exceptions.However this exception
> is different from the exception we got from the last time bamboo build MS
> pack.
>
>
> [1] [2012-04-05 11:57:21,781] ERROR -  Exception in persisting the
> transaction admin/sudoku
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
>  at java.io.File.createNewFile(File.java:883)
> at
> org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.commitTransaction(AbstractFilePersistenceManager.java:63)
>  at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:295)
> at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:283)
>  at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:653)
> at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:407)
>  at
> org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:606)
> at
> org.wso2.carbon.mashup.jsservices.deployer.JSDeployer.deploy(JSDeployer.java:191)
>  at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
>  at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
>  at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:461)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
>  at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:370)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:263)
> at
> org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:117)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> [2012-04-05 11:57:21,782] ERROR -  Unable to handle new service addition.
> Service: admin/sudoku
> org.wso2.carbon.core.persistence.PersistenceException: Exception in
> persisting the transaction admin/sudoku
> at
> org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.handleExceptionWithRollback(AbstractFilePersistenceManager.java:286)
>  at
> org.wso2.carbon.core.persistence.file.AbstractFilePersistenceManager.commitTransaction(AbstractFilePersistenceManager.java:78)
> at
> org.wso2.carbon.core.persistence.ServicePersistenceManager.handleNewServiceAddition(ServicePersistenceManager.java:295)
>  at
> org.wso2.carbon.core.deployment.DeploymentInterceptor.serviceUpdate(DeploymentInterceptor.java:283)
> at
> org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:653)
>  at
> org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:407)
> at
> org.apache.axis2.deployment.DeploymentEngine.addServiceGroup(DeploymentEngine.java:606)
>  at
> org.wso2.carbon.mashup.jsservices.deployer.JSDeployer.deploy(JSDeployer.java:191)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>  at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:810)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>  at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
>  at
> org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:139)
> at
> org.wso2.carbon.core.CarbonAxisConfigurator.loadServices(CarbonAxisConfigurator.java:461)
>  at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:95)
> at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarb

Re: [Dev] Carbon 4.0.0 - Alpha2 packs

[Afkham Azeez]

Not really related to this error, but this is an example of not following
logging best practices. During my WSO2 Software Development Process
presentation I did for the new batch, I stressed on the importance of
logging all contextual information when logging errors. This has not been
followed in the case of at least AbstractFilePersistenceManager.  We just
have a message "java.io.IOException: No such file or directory". At least
you could have printed the name of the file. Also, I see a yellow warning
bar at line 63 in IDEA where the code reads "f.createNewFile(); //creates a
file only if it does not exist". Please do not ignore such warnings &
follow all best practices.

On Thu, Apr 5, 2012 at 12:04 PM, Lalaji Sureshika  wrote:

> AbstractFilePersistenceManager




-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* **
email: **az...@wso2.com* * cell: +94 77 3320919
blog: **http://blog.afkham.org* *
twitter: **http://twitter.com/afkham_azeez*
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev