Re: [Dev] [ESB] How to configure BAM Profile outside the Dashboard?

[Shavantha Weerasinghe]

Hi imesh

We can tryout this  approach during 4.8.1 testing

Regards,shavantha
On Jan 24, 2014 6:21 PM, "Imesh Gunaratne"  wrote:

> Hi,
>
> I found a better approach than using the G-Reg check-in tool.
> We could create a CAR archive including a Registry Resources Project and
> deploy the CAR file directly in the ESB.
>
> Thanks
>
>
> On Thu, Jan 23, 2014 at 5:00 PM, Imesh Gunaratne  wrote:
>
>> Hi,
>>
>> I was able to do the following with G-Reg check-in tool and successfully
>> configure the BAM Server Profile outside the ESB Dashboard:
>>
>> 1. Start a fresh ESB instance.
>> 2. Checkout _system/config path to a local folder (A1) using check in
>> client.
>> 3. Create bamServerProfiles folder at A1.
>> 4. Copy BAM Server Profile file to above bamServerProfiles folder.
>> 5. Add bamServerProfiles using check in client.
>> 6. Check in changes using check in client.
>>
>> Thanks
>> Imesh
>>
>>
>> On Thu, Jan 23, 2014 at 10:22 AM, Imesh Gunaratne  wrote:
>>
>>> Hi,
>>>
>>> As I found BAM Profiles in ESB are stored in the registry (ESB 4.8.0).
>>> Is there a way to configure this without accessing the ESB Dashboard (if
>>> we could export the required configuration to a file)?
>>>
>>> I tried to use the G-Reg check-in tool but it was not successful with
>>> the H2 database.
>>>
>>> Thanks
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Technical Lead
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: http://imesh.gunaratne.org
>>> Lean . Enterprise . Middleware
>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Technical Lead
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: http://imesh.gunaratne.org
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.gunaratne.org
> 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] Shouldn't we be switching to SLf4J for Carbon 5?

[Senaka Fernando]

Hi all,

+1 for moving to SLF4J. See the following. [1] is the post from the creator
of JCL, :).

[1] http://radio-weblogs.com/0122027/2003/08/15.html
[2]
http://v4forums.wordpress.com/2008/12/27/slf4j-vs-jcl-dynamic-binding-vs-static-binding/
[3]
http://stackoverflow.com/questions/3222895/why-is-commons-logging-believed-to-be-unpopular

Thanks,
Senaka.


On Sat, Jan 25, 2014 at 6:32 AM, Afkham Azeez  wrote:

>
>
>
> On Fri, Jan 24, 2014 at 11:39 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> With C5 logging framework (based on Pax Logging [1]), the log4j is used
>> as the logging back-end. But the framework support number of logging API's
>> and SLF4J is also one of that. This allows us to use any logging API in the
>> components we develop with C5.
>>
>> IMO, its a matter of deciding which API to use and follow it as a best
>> practice. I'm +1 on using SLF4J.
>>
>
> Excellent! Let's start converting all the log statements to slf4j syntax.
>
>
>>
>> Thanks,
>> Kishanthan.
>> [1] https://ops4j1.jira.com/wiki/display/paxlogging/Pax+Logging
>>
>>
>> On Fri, Jan 24, 2014 at 9:23 PM, Afkham Azeez  wrote:
>>
>>> The most appealing feature to me is the parametrized log messages, and
>>> there is no need to wrap statements in if(log.isDebugEnabled()),
>>> isInfoEnabled() and so on.
>>>
>>>
>>> On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez  wrote:
>>>
 http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/

 We should go with SLF4J


 On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga wrote:

>
>
> I'm not quite sure whether we can really compare SLF4J with Log4J
> where SLF4J is a logging API while Log4J is a logging implementation (
> Log4J can be used with SLF4J and most common SLF4J binding as well),
> instead we should compare SLF4J API with Commons-Logging API. In my POV
> recent versions of both SLF4J and Commons-Logging are more or less 
> similar.
> I don't have any objection to use SLF4J but have we consider JUL ?
>
>
> Please refer required dependencies for each option.
>
> - Commons-logging -  Need 2 dependencies on runtime as
>  Commons-logging API and implementation ( e.g -  SLF4J API,
> Commons-logging-LOG4J bridge)
> - SLF4J  -  Need 3 dependencies on run time as  SLF4J
> API, SLF4J-X binding, X logging framework ( e.g  - SLF4J API,
> SLF4J-LOG4J binding , LOG4J )
> - JUL -  0 dependencies just JDK
>
> If there is no found limitations I would prefer to use JUL and worth
> to consider it before make a conclusion.
>
> Thanks !
>
>
>  On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez  wrote:
>
>>  I was reading
>> http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html&;
>>  we could remove a lot of boiler
>> plate code, and bring in any logging implementation if we use SLF4J.
>> Thoughts?
>>
>> --
>> *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 <%2B94%2077%203320919> 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
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


 --
 *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 <%2B94%2077%203320919> 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 <%2B94%2077%203320919> blog: *
>>> *http://blog.afkham.org* 
>>> * twitter: 
>>> **http://twitter.com/afkham_az

Re: [Dev] Please provide an update on stabilizing the current branches & chunks?

[Krishantha Samaraweera]

Hi Isuruwan,

The actual issue is with APIM 1.6 profile generation.

I could see the following lines in log. Because of generated build is
unstable, server start-up at integration tests failed.

build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile
Generation .. FAILURE [4:41.977s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile
Generation Parent ... SUCCESS [1.697s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox
 SUCCESS [2.548s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution
... SUCCESS [3:20.956s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution
Parent  SUCCESS [0.112s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration Test
Module  FAILURE [7:41.465s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration UI
Test Module . FAILURE [9:10.559s]
build   24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration Tests
.. SUCCESS [0.840s]

Thanks,

Krishantha.



On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath  wrote:

> Hi Krishantha,
>
> I executed all chunks with the with the feature to run UI tests remotely.
> Chunk02 was successfully built but there were failures in chunk05 and
> chunk06 [1] . Noted the following exception in APIM UI tests in chunk06:
>
> error 24-Jan-2014 02:17:51at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> error 24-Jan-2014 02:17:51Caused by: java.lang.RuntimeException: Port 
> 9763 is not open
> error 24-Jan-2014 02:17:51at 
> org.wso2.carbon.automation.core.utils.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:111)
> error 24-Jan-2014 02:17:51at 
> org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:133)
> error 24-Jan-2014 02:17:51at 
> org.wso2.carbon.automation.core.ServerGroupManager.startServer(ServerGroupManager.java:92)
> error 24-Jan-2014 02:17:51at 
> org.wso2.carbon.automation.core.ServerGroupManager.startServersForBuilder(ServerGroupManager.java:98)
>
> Could this be an infrastructure issue with the remote UI test server and 
> bamboo builder?
>
> [1] http://wso2.org/bamboo/browse/TEST001
>
> Regards!
>
>
>
> On Wed, Jan 22, 2014 at 12:04 PM, Isuruwan Herath wrote:
>
>> Yes, rebuilding the failures did not give the mentioned error again. As
>> the UI tests have been worked around I'm running bamboo plans again from
>> chunk02 and let's see if the p2-profile-gen fails again. Thanks for looking
>> into this.
>>
>> Cheers!
>> Isuruwan
>>
>>
>> On Wed, Jan 22, 2014 at 11:51 AM, Lasantha Fernando wrote:
>>
>>>
>>>
>>>
>>> On 21 January 2014 12:55, Isuruwan Herath  wrote:
>>>
 Hi Lasantha,

 Following is the error occurred in Bamboo log [1] :

 [ERROR] Failed to execute goal
 org.wso2.maven:carbon-p2-plugin:1.5.3:p2-profile-gen
 (p2-profile-generation-for-gateway-manager-profile) on project
 am-p2-profile: P2 publisher return code was 137 -> [Help 1]

 Bamboo plan is configured to build from chunk06 folder in branch.

 [1] http://wso2.org/bamboo/browse/TEST001-EPC6-1/log

>>>
>>> Hi Isuruwan,
>>>
>>> Asked for the logs since thought I might have made a mistake in creating
>>> the tag for chunk-06. I did verify it in a clean repo build. AFAIK, there
>>> were some changes done to the p2-repo after the tag was created. But no
>>> changes were done to the product builds. Guess those commits also need to
>>> go into the tag.
>>>
>>> Anyway, looks like the current build failure in chunk-06 is due to UI
>>> integration tests.
>>>
>>> Thanks,
>>> Lasantha
>>>
>>>
>>>

 Regards!



 On Tue, Jan 21, 2014 at 11:28 AM, Lasantha Fernando 
 wrote:

> Hi Isuruwan,
>
> Can you post the error you encountered in building chunk-06? Are you
> building from the chunk-06 tag?
>
> Thanks,
> Lasantha
>
>
> On 21 January 2014 10:45, Afkham Azeez  wrote:
>
>>  Krishantha,
>> If the UI tests cannot be fixed by EOD today, let's disable them
>> until we find a proper solution.
>>
>>
>> On Tue, Jan 21, 2014 at 10:28 AM, Isuruwan Herath 
>> wrote:
>>
>>> Hi Azeez,
>>> I created plans and executed all released chunks under Bamboo plan
>>> TEST 4.2.0. Apart from the failure in 'WSO2 API Manager - P2
>>> Profile Generation' (noted yesterday) in chunk06 other failures are 
>>> related
>>> to UI integration tests (in chunk02, chunk05, chunk06). Krishantha is
>>> working on the failures in UI tests to run them remotely (I see chunk02 
>>> is
>>> being built at the moment). If we get that through we can run all plans
>>> once more and confirm all released chunks are clean.
>>>
>>> Regards!
>>> Isuruwan
>>>
>>>
>>> 

Re: [Dev] Shouldn't we be switching to SLf4J for Carbon 5?

[Afkham Azeez]

Nice! Carbon 5 team, please add a RedMine item to track migration to SLF4J


On Sun, Jan 26, 2014 at 9:56 AM, Senaka Fernando  wrote:

> Hi all,
>
> +1 for moving to SLF4J. See the following. [1] is the post from the
> creator of JCL, :).
>
> [1] http://radio-weblogs.com/0122027/2003/08/15.html
> [2]
> http://v4forums.wordpress.com/2008/12/27/slf4j-vs-jcl-dynamic-binding-vs-static-binding/
> [3]
> http://stackoverflow.com/questions/3222895/why-is-commons-logging-believed-to-be-unpopular
>
> Thanks,
> Senaka.
>
>
> On Sat, Jan 25, 2014 at 6:32 AM, Afkham Azeez  wrote:
>
>>
>>
>>
>> On Fri, Jan 24, 2014 at 11:39 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> With C5 logging framework (based on Pax Logging [1]), the log4j is used
>>> as the logging back-end. But the framework support number of logging API's
>>> and SLF4J is also one of that. This allows us to use any logging API in the
>>> components we develop with C5.
>>>
>>> IMO, its a matter of deciding which API to use and follow it as a best
>>> practice. I'm +1 on using SLF4J.
>>>
>>
>> Excellent! Let's start converting all the log statements to slf4j syntax.
>>
>>
>>>
>>> Thanks,
>>> Kishanthan.
>>> [1] https://ops4j1.jira.com/wiki/display/paxlogging/Pax+Logging
>>>
>>>
>>> On Fri, Jan 24, 2014 at 9:23 PM, Afkham Azeez  wrote:
>>>
 The most appealing feature to me is the parametrized log messages, and
 there is no need to wrap statements in if(log.isDebugEnabled()),
 isInfoEnabled() and so on.


 On Fri, Jan 24, 2014 at 9:21 PM, Afkham Azeez  wrote:

> http://glauche.de/2009/09/09/java-util-logging-vs-slf4j/
>
> We should go with SLF4J
>
>
> On Fri, Jan 24, 2014 at 8:59 PM, Sagara Gunathunga wrote:
>
>>
>>
>> I'm not quite sure whether we can really compare SLF4J with Log4J
>> where SLF4J is a logging API while Log4J is a logging implementation (
>> Log4J can be used with SLF4J and most common SLF4J binding as well),
>> instead we should compare SLF4J API with Commons-Logging API. In my POV
>> recent versions of both SLF4J and Commons-Logging are more or less 
>> similar.
>> I don't have any objection to use SLF4J but have we consider JUL ?
>>
>>
>> Please refer required dependencies for each option.
>>
>> - Commons-logging -  Need 2 dependencies on runtime as
>>  Commons-logging API and implementation ( e.g -  SLF4J API,
>> Commons-logging-LOG4J bridge)
>> - SLF4J  -  Need 3 dependencies on run time as  SLF4J
>> API, SLF4J-X binding, X logging framework ( e.g  - SLF4J API,
>> SLF4J-LOG4J binding , LOG4J )
>> - JUL -  0 dependencies just JDK
>>
>> If there is no found limitations I would prefer to use JUL and worth
>> to consider it before make a conclusion.
>>
>> Thanks !
>>
>>
>>  On Fri, Jan 24, 2014 at 6:26 PM, Afkham Azeez wrote:
>>
>>>  I was reading
>>> http://javarevisited.blogspot.com/2013/08/why-use-sl4j-over-log4j-for-logging-in.html&;
>>>  we could remove a lot of boiler
>>> plate code, and bring in any logging implementation if we use
>>> SLF4J. Thoughts?
>>>
>>> --
>>> *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 <%2B94%2077%203320919> 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
>>>
>>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
>
> --
> *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 <%2B94%2077%203320919> 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.

Re: [Dev] Please provide an update on stabilizing the current branches & chunks?

[Krishantha Samaraweera]

Hi Isuruwan,

Chunk 05 build failures are due to some backend/UI test failures. Seems
like teams have released the products with integration test failures.
Fixing those failure are not possible because code cannot be committed .
And even skipping failure cases though testNG xml will take lot of effort
because need to rewrite testNG xml and include all classes and exclude
failure classes (TestNg supports only for class exclusion).

Best option available now is to use
testFailureIgnoreproperty.
You can set this property with maven build command and ignore
test failures to get the build passed.

*DSS Backend failures - *

build 23-Jan-201 23:45:42 Failed tests:
initialize(org.wso2.carbon.dss.samples.test.EventingSampleTestCase)
build 23-Jan-2014 23:45:42
selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
expected: but was:
build 23-Jan-2014 23:45:42
selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
expected: but was:
build 23-Jan-2014 23:45:42
selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
expected: but was:
build 23-Jan-2014 23:45:42
selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
expected: but was:
build 23-Jan-2014 23:45:42
selectOperation(org.wso2.carbon.dss.samples.test.WebResourceSampleTestCase):
expected: but was:
*build 23-Jan-2014 23:45:42 Tests run: 221, Failures: 6, Errors: 0,
Skipped: 4*

*AS Backend Test failures - *

Failed tests:
testUpdateStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByUserTestCase):
Server returned HTTP response code: 500 for URL:
https://localhost:9443/services/StudentService/student/automationStudent
build 23-Jan-2014 22:14:05
testGetResourceAfterDelete(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByInvalidUser):
User belongs to invalid group was able to get the resource expected [true]
but found [false]
build 23-Jan-2014 22:14:05
testAddNewStudent(org.wso2.carbon.integration.rest.test.poxsecurity.POXSecurityByAdminTestCase):
Server returned HTTP response code: 500 for URL:
https://localhost:9443/services/StudentService/students
build 23-Jan-2014 22:14:05
testEmailJaggery(jaggery.integration.tests.emailhostobject.EmailHostObjectTestCase):
Input stream failure expected object to not be null
build 23-Jan-2014 22:14:05
*build 23-Jan-2014 22:14:05 Tests run: 216, Failures: 4, Errors: 0,
Skipped: 5*

*AS UI test failures -*

build 23-Jan-2014 22:20:43 Failed tests:
uploadSpringWebApplicationTest(org.wso2.carbon.integration.test.ui.webapp.spring.SpringWebApplicationDeploymentTestCase):
Web Application uploading failed expected: but was:
build 23-Jan-2014 22:20:43
build 23-Jan-2014 22:20:43 Tests run: 15, Failures: 1, Errors: 0, Skipped: 2

Thanks,
Krishantha.


On Sun, Jan 26, 2014 at 11:40 AM, Krishantha Samaraweera <
krishan...@wso2.com> wrote:

> Hi Isuruwan,
>
> The actual issue is with APIM 1.6 profile generation.
>
> I could see the following lines in log. Because of generated build is
> unstable, server start-up at integration tests failed.
>
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile Generation 
> .. FAILURE [4:41.977s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - P2 Profile Generation 
> Parent ... SUCCESS [1.697s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - BAM Toolbox 
>  SUCCESS [2.548s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution 
> ... SUCCESS [3:20.956s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Distribution Parent 
>  SUCCESS [0.112s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration Test 
> Module  FAILURE [7:41.465s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration UI Test 
> Module . FAILURE [9:10.559s]
> build 24-Jan-2014 03:02:03[INFO] WSO2 API Manager - Integration Tests 
> .. SUCCESS [0.840s]
>
> Thanks,
>
> Krishantha.
>
>
>
> On Fri, Jan 24, 2014 at 5:59 PM, Isuruwan Herath wrote:
>
>> Hi Krishantha,
>>
>> I executed all chunks with the with the feature to run UI tests remotely.
>> Chunk02 was successfully built but there were failures in chunk05 and
>> chunk06 [1] . Noted the following exception in APIM UI tests in chunk06:
>>
>> error24-Jan-2014 02:17:51at 
>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>> error24-Jan-2014 02:17:51Caused by: java.lang.RuntimeException: 
>> Port 9763 is not open
>> error24-Jan-2014 02:17:51at 
>> org.wso2.carbon.automation.core.utils.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:111)
>> error24-Jan-2014 02:17:51at 
>> org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:133)
>> error24-Jan-2014 02