Re: [Dev] Usage of "tocommonauth" property in OAuth2 Authorize Endpoint
Hi Isura,
AFAIR Asanthi reported those issues.
Regards,
Aparna
On Mon, Nov 6, 2017 at 9:17 AM, Isura Karunaratne wrote:
> Hi Aparna,
>
> Do we have the stack trace of the error you observed?
>
> Thanks
> Isura.
>
> On Wed, Nov 1, 2017 at 2:41 PM, Aparna Karunarathna
> wrote:
>
>> Hi Isura, Ishara,
>>
>> During the perf test cycles, we have observed some test failures in
>> OAuth2 flows with tocommonauth=true parameter and AFAIR Johan explained
>> there was mail to revert it back use the commonauth endpoint.
>>
>> Regards,
>> Aparna.
>>
>> On Sat, Oct 28, 2017 at 10:45 AM, Ishara Karunarathna
>> wrote:
>>
>>> Hi Isura,
>>>
>>>
>>>
>>> On Fri, Oct 27, 2017 at 7:43 PM, Isura Karunaratne
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> If the "tocommonauth" property value is true, the
>>>> authentication response from the login page will forward to the commonauth
>>>> endpoint through OAuth2 Authorize Endpoint.
>>>>
>>>>
>>>>- IIRC, this was done to reduce the number of redirection in OAuth
>>>>flow, but I think it is better to handle all the login response from the
>>>>commonauth endpoint.
>>>>
>>>> This is used in SAML flow as well to reduce the redirections.
>>>
>>>>
>>>>- Do we need to continue supporting this or shall we remove this?
>>>>
>>>>
>>>> At the moment In IS components we are not setting this parameter, but
>>> there are some other components Eg App manager using this (may be customers
>>> might have implemented authenticators with this parameter).
>>> Do you see any issues supporting this ?
>>> If not I think its better to keep this.
>>>
>>> -Ishara
>>>
>>>> String isToCommonOauth =
>>>> request.getParameter(FrameworkConstants.RequestParams.TO_COMMONAUTH);
>>>>
>>>> if ("true".equals(isToCommonOauth) && flowStatus == null) {
>>>> try {
>>>> return sendRequestToFramework(request, response);
>>>> } catch (ServletException | IOException e) {
>>>> log.error("Error occurred while sending request to authentication
>>>> framework.");
>>>> return
>>>> Response.status(HttpServletResponse.SC_INTERNAL_SERVER_ERROR).build();
>>>> }
>>>> }
>>>>
>>>>
>>>>
>>>> Thanks
>>>> Isura.
>>>>
>>>> --
>>>>
>>>> *Isura Dilhara Karunaratne*
>>>> Associate Technical Lead | WSO2
>>>> Email: is...@wso2.com
>>>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>>>> Blog : http://isurad.blogspot.com/
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Ishara Karunarathna
>>> Associate Technical Lead
>>> WSO2 Inc. - lean . enterprise . middleware | wso2.com
>>>
>>> email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile:
>>> +94717996791 <071%20799%206791>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Regards,*
>>
>> *Aparna Karunarathna.*
>>
>>
>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533
>> <071%20400%202533>*
>>
>> * <http://wso2.com/signature>*
>>
>
>
>
> --
>
> *Isura Dilhara Karunaratne*
> Associate Technical Lead | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810 <077%20225%204810>
> Blog : http://isurad.blogspot.com/
>
>
>
>
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
* <http://wso2.com/signature>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Usage of "tocommonauth" property in OAuth2 Authorize Endpoint
Hi Isura, Ishara,
During the perf test cycles, we have observed some test failures in OAuth2
flows with tocommonauth=true parameter and AFAIR Johan explained there was
mail to revert it back use the commonauth endpoint.
Regards,
Aparna.
On Sat, Oct 28, 2017 at 10:45 AM, Ishara Karunarathna
wrote:
> Hi Isura,
>
>
>
> On Fri, Oct 27, 2017 at 7:43 PM, Isura Karunaratne wrote:
>
>> Hi all,
>>
>> If the "tocommonauth" property value is true, the authentication response
>> from the login page will forward to the commonauth endpoint through OAuth2
>> Authorize Endpoint.
>>
>>
>>- IIRC, this was done to reduce the number of redirection in OAuth
>>flow, but I think it is better to handle all the login response from the
>>commonauth endpoint.
>>
>> This is used in SAML flow as well to reduce the redirections.
>
>>
>>- Do we need to continue supporting this or shall we remove this?
>>
>>
>> At the moment In IS components we are not setting this parameter, but
> there are some other components Eg App manager using this (may be customers
> might have implemented authenticators with this parameter).
> Do you see any issues supporting this ?
> If not I think its better to keep this.
>
> -Ishara
>
>> String isToCommonOauth =
>> request.getParameter(FrameworkConstants.RequestParams.TO_COMMONAUTH);
>>
>> if ("true".equals(isToCommonOauth) && flowStatus == null) {
>> try {
>> return sendRequestToFramework(request, response);
>> } catch (ServletException | IOException e) {
>> log.error("Error occurred while sending request to authentication
>> framework.");
>> return
>> Response.status(HttpServletResponse.SC_INTERNAL_SERVER_ERROR).build();
>> }
>> }
>>
>>
>>
>> Thanks
>> Isura.
>>
>> --
>>
>> *Isura Dilhara Karunaratne*
>> Associate Technical Lead | WSO2
>> Email: is...@wso2.com
>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>> Blog : http://isurad.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Ishara Karunarathna
> Associate Technical Lead
> WSO2 Inc. - lean . enterprise . middleware | wso2.com
>
> email: isha...@wso2.com, blog: isharaaruna.blogspot.com, mobile:
> +94717996791 <071%20799%206791>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
* <http://wso2.com/signature>*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Docker ReadMe is unclear
Hi All, Docker images creating steps are not clear. I have configured the K8S cluster and then started creating the docker images. In order to do that, I followed the link [1] ReadMe, after executing the last command "git submodule update" there's no way to find out what to do next? Seems like this is common to all docker repos. [1] https://github.com/wso2/docker-is/tree/release-5.3.0 -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* * <http://wso2.com/signature>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Chathurika De Silva
Hi All, It's my pleasure to announce Chathurika De Silva as a WSO2 Committer. She is an active member of EE team and has given a great contribution to ESB, BPS, BRS, App Factory product releases. Congratulations Chathurika and keep up the good work...! -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* * <http://wso2.com/signature>* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM 2.0] Revoked access and revoked refresh tokens returning with http response header
Hi Nuwan, Kavitha was asking, RevokedAccessToken & RevokedRefreshToken are getting in the header because it was requested requirement by APIM team [1] ? Jira [1] says it's a bad implementation. So are we going to fix[2] ? [1] https://wso2.org/jira/browse/IDENTITY-4112 [2] https://wso2.org/jira/browse/APIMANAGER-5098 Regards, Aparna. On Fri, Jun 24, 2016 at 5:44 PM, Nuwan Dias wrote: > Can you explain what the issue here is? You have raised the ticket as a > bug but you've forgotten to describe what the bug actually is? > > On Fri, Jun 24, 2016 at 5:39 PM, Kavitha Subramaniyam > wrote: > >> Hi apim team, >> A jira has been raised to track this issue in [1] >> >> [1] https://wso2.org/jira/browse/APIMANAGER-5098 >> >> Thanks, >> >> On Thu, Jun 23, 2016 at 6:31 PM, Kavitha Subramaniyam >> wrote: >> >>> Hi team, >>> Highly appreciate your update on this. >>> >>> Thanks, >>> >>> On Wed, Jun 22, 2016 at 2:28 PM, Kavitha Subramaniyam >>> wrote: >>> >>>> Hi team, >>>> >>>> I observed that both revoked access and revoked refresh tokens were >>>> returning in http response header [3]. >>>> setup : IS as KM >>>> - apim 2.0.0 17th nightly build >>>> - IS 5.2.0 19th build >>>> - Token encryption enabled >>>> >>>> Could you please confirm that this behavior is not resolved purposely >>>> in apim 2.0.0 due to the reasons discussed in mail thread [1], or it has >>>> been solved? >>>> Find an identity jira was raised for IS issue [2] >>>> >>>> [1] Revoked Access Token and Revoked Refresh Token returned back in >>>> token revoke endpoint response >>>> >>>> [2] https://wso2.org/jira/browse/IDENTITY-4112 >>>> >>>> [3] >>>> >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1 >>>> 200 OK >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> AuthorizedUser: WSO2.ORG/admin@carbon.super >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> Cache-Control: no-store >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date: >>>> Wed, 22 Jun 2016 08:39:00 GMT >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma: >>>> no-cache >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89 >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> RevokedRefreshToken: >>>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU= >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> Content-Type: text/html >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << >>>> Content-Length: 0 >>>> [2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server: >>>> WSO2 Carbon Server >>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1 >>>> 200 OK >>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << >>>> RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89 >>>> [2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << >>>> AuthorizedUser: WSO2.ORG/admin@carbon.super >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << >>>> RevokedRefreshToken: >>>> h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU= >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << >>>> Content-Type: text/html >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma: >>>> no-cache >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << >>>> Cache-Control: no-store >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date: >>>> Wed, 22 Jun 2016 08:39:00 GMT >>>> [2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << >>>> Transfer-Encoding: chunked >>>> >>>> >>>> >>>> >>>> >>>> Thanks, >>>> >>>> -- >>>> Kavitha.S >>>> *Software Engineer -QA* >>>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194> >>>> kavi...@wso2.com >>>> >>> >>> >>> >>> -- >>> Kavitha.S >>> *Software Engineer -QA* >>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194> >>> kavi...@wso2.com >>> >> >> >> >> -- >> Kavitha.S >> *Software Engineer -QA* >> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194> >> kavi...@wso2.com >> > > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM Automations tests are disabled
Observed duplicate automation test cases [1] [2].
[1]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/other/APIInvocationFailureTestCase.java
[2]
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/token/InvalidTokenTestCase.java
Regards,
Aparna.
On Tue, May 3, 2016 at 9:46 AM, Nuwan Dias wrote:
>
>
> On Mon, May 2, 2016 at 10:44 PM, Aparna Karunarathna
> wrote:
>
>> Hi Nuwan,
>>
>> We have seen a lot of discrepancies in the automation test, so it would
>> be good if you guys can fix those before the release.
>>
>
> If you can report whatever discrepancies you encounter that would be easy
> for us to fix. Yes, we need to fix them, but its always a battle between
> time and priorities. Right now we won't be putting a lot of focused effort
> on validating ~500 test cases because in a few months time we anyway have
> to re-write these tests to be on top of C5.
>
>>
>> Regards,
>> Aparna
>>
>> On Mon, May 2, 2016 at 6:36 PM, Nuwan Dias wrote:
>>
>>> Not sure why this was disabled. Maybe its because it uses the deprecated
>>> YouTube API (it no longer works). These are very old tests coming even
>>> before the wso2-dev repo days. So can't recall its entire history.
>>>
>>> However, there is a new test case called CopyNewVersionTestCase that
>>> covers this scenario. So we haven't lost on coverage by disabling it.
>>>
>>> We have ~500 tests in the product now. And some of these are pretty old.
>>> Yes, we need to refine and remove obsolete ones and we do that as we
>>> encounter them. We will do this refining as priorities allow us to.
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Mon, May 2, 2016 at 5:59 PM, Dharshana Warusavitharana <
>>> dharsha...@wso2.com> wrote:
>>>
>>>> Hi APIM team,
>>>>
>>>> Please add comments when you are disabling tests like this. Or remove
>>>> test completely if they are obsolete please remove them from the suite.
>>>> And i see invalid test method description here.
>>>>
>>>> Please fix these ASAP.
>>>>
>>>> Thank you,
>>>> Dharshana.
>>>>
>>>> On Mon, May 2, 2016 at 5:19 PM, Yasassri Ratnayake
>>>> wrote:
>>>>
>>>>> Hi APIM Team,
>>>>>
>>>>> Observed the following test case at [1]. As shown below most test
>>>>> mrethods are disabled except for 2 in this test class and I couldn't find
>>>>> any comment explaining why these tests were disabled. Can we look into
>>>>> these and get them enabled?
>>>>>
>>>>>
>>>>> @Test(groups = {"wso2.am"}, description = "API visibility", enabled =
>>>>> false)
>>>>> public void copyAPILifeCycleTestCase() throws Exception {
>>>>>
>>>>>
>>>>> [1] -
>>>>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/other/APIApplicationLifeCycleTestCase.java#L363
>>>>>
>>>>>
>>>>> With Regards,
>>>>> --
>>>>> Yasassri Ratnayake
>>>>> Software Engineer - QA
>>>>> WSO2 Inc ; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>> *Mobile : +94715933168 <%2B94715933168>*
>>>>> *Blogs : http://yasassriratnayake.blogspot.com
>>>>> <http://yasassriratnayake.blogspot.com/>*
>>>>> *http://wso2logs.blogspot.com
>>>>> <http://wso2logs.blogspot.com>*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Dharshana Warusavitharana
>>>> Senior Software Engineer , Test Automation
>>>> WSO2 Inc. http://wso2.com
>>>> email : dharsha...@wso2.com
>>>> Tel : +94 11 214 5345
>>>> Fax :+94 11 2145300
>>>> cell : +94770342233
>>>> blog : http://dharshanaw.blogspot.com
>>>>
>>>> lean . enterprise . middleware
>>>>
>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Technical Lead - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>>
>> --
>> *Regards,*
>>
>> *Aparna Karunarathna.*
>>
>>
>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>*
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM Automations tests are disabled
Hi Nuwan,
We have seen a lot of discrepancies in the automation test, so it would be
good if you guys can fix those before the release.
Regards,
Aparna
On Mon, May 2, 2016 at 6:36 PM, Nuwan Dias wrote:
> Not sure why this was disabled. Maybe its because it uses the deprecated
> YouTube API (it no longer works). These are very old tests coming even
> before the wso2-dev repo days. So can't recall its entire history.
>
> However, there is a new test case called CopyNewVersionTestCase that
> covers this scenario. So we haven't lost on coverage by disabling it.
>
> We have ~500 tests in the product now. And some of these are pretty old.
> Yes, we need to refine and remove obsolete ones and we do that as we
> encounter them. We will do this refining as priorities allow us to.
>
> Thanks,
> NuwanD.
>
> On Mon, May 2, 2016 at 5:59 PM, Dharshana Warusavitharana <
> dharsha...@wso2.com> wrote:
>
>> Hi APIM team,
>>
>> Please add comments when you are disabling tests like this. Or remove
>> test completely if they are obsolete please remove them from the suite.
>> And i see invalid test method description here.
>>
>> Please fix these ASAP.
>>
>> Thank you,
>> Dharshana.
>>
>> On Mon, May 2, 2016 at 5:19 PM, Yasassri Ratnayake
>> wrote:
>>
>>> Hi APIM Team,
>>>
>>> Observed the following test case at [1]. As shown below most test
>>> mrethods are disabled except for 2 in this test class and I couldn't find
>>> any comment explaining why these tests were disabled. Can we look into
>>> these and get them enabled?
>>>
>>>
>>> @Test(groups = {"wso2.am"}, description = "API visibility", enabled =
>>> false)
>>> public void copyAPILifeCycleTestCase() throws Exception {
>>>
>>>
>>> [1] -
>>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/java/org/wso2/am/integration/tests/other/APIApplicationLifeCycleTestCase.java#L363
>>>
>>>
>>> With Regards,
>>> --
>>> Yasassri Ratnayake
>>> Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <%2B94715933168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> <http://yasassriratnayake.blogspot.com/>*
>>> *http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>*
>>>
>>
>>
>>
>> --
>>
>> Dharshana Warusavitharana
>> Senior Software Engineer , Test Automation
>> WSO2 Inc. http://wso2.com
>> email : dharsha...@wso2.com
>> Tel : +94 11 214 5345
>> Fax :+94 11 2145300
>> cell : +94770342233
>> blog : http://dharshanaw.blogspot.com
>>
>> lean . enterprise . middleware
>>
>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Wrong Test method name
Hi All,
While doing the API Manager test case mapping, observed $subject has used.
Both method names should be changed to *testAddDocumentToAnAPISupportUrl()
and **testAddDocumentToAnAPIPublicUrl()*
class:
APIM623AddDocumentationToAnAPIWithDocTypePublicForumThroughPublisherRestAPITestCase.java
*@Test(groups = {"wso2.am <http://wso2.am>"}, description = "Add
Documentation To An API With Type support forum And" + " Source Url through
the publisher rest API ")*
*public void testAddDocumentToAnAPISupportInline() throws Exception {*
class
:
APIM625AddDocumentationToAnAPIWithDocTypeSupportForumThroughPublisherRestAPITestCase.java
*@Test(groups = {"wso2.am <http://wso2.am>"}, description = "Add
Documentation To An API With Type " +"public forum And" + " Source Url
through the publisher rest API ")*
*public void testAddDocumentToAnAPIPublicInline() **throws Exception {*
It would be good to update the Test method names.
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Asanthi Kulasinghe
Hi All, It's my pleasure to announce Asanthi Kulasinghe as a WSO2 Committer. Asanthi is an active member of QA team and has given a great contribution to API Manager, App Manager, ESB product releases and API Manager, ESB service packs. Congratulations Asanthi and keep up the good work...! -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [QA] Question on API-M gateway node maximum concurrent threads
Hi Nuwan, Understood your concern Nuwan, I'm the one who proposed to add peak load for few hours( ~ 4 hours) and check the memory growth, GC , exceptions etc in Gateway and KM sides. In here we are not trying to hit the server with max load, just want to check the server behavior. :) If you are not agreeing to this, will do proper long running test for 2 weeks with load that you suggested and will share the results with you. Then 3rd week will do some ad-hoc test like we suggested and check server behavior. WDYT? Regards, Aparna. On Fri, Jan 8, 2016 at 11:01 AM, Nuwan Dias wrote: > Hi Aparna, > > I'm totally +1 for the long running test. But my concern is that Pubudu is > planning for a strange test. It doesn't look like a typical long running > test. See his comment on the last reply "*generate a relatively higher > number of threads lets say for a few hours of the day and stop it on daily > basis*". The idea I get from this is that you're trying to hit the server > at max load and then stop... hit it at max again and stop... likewise. > Maybe I'm getting the wrong message but the information you've requested is > for the max threads count and not the moderate threads count. > > IMO to mimick a real world scenario you should be hitting the sever with a > moderate load (about 50 threads max) for a long time period. Not with a > peak load (250 threads) for several hours. And we should monitor the > servers during this period in order to have insight of any issues that may > occur. The closer we get to the real world occurrence, the more valuable > the outcome of our efforts would be. > > Thanks, > NuwanD. > > On Fri, Jan 8, 2016 at 10:47 AM, Aparna Karunarathna > wrote: > >> Hi Nuwan, >> >> Objective of doing a long running test after the release is, in the >> release time we won't be able to execute a long running test for couple of >> weeks. Because sometime we have to stop the test to change the packs or >> integrate with other product with setup or to enable some configs to test a >> feature, etc. Most of the time we are getting some cloud issue as >> well(resource issues and set of nodes were getting slow). So most of time >> we were able to run the long running test for day or 2 days. >> >> Therefor we thought of doing a proper long running test against the GA >> pack for 3 weeks. Last year we did long running test after the release for >> couple of releases and then we shared our findings(memory growth, >> exceptions, warnings, etc) with dev teams. So if we can identify a bug at >> this stage then we can prepare a fix. >> >> Regards, >> Aparna. >> >> >> >> On Fri, Jan 8, 2016 at 9:22 AM, Nuwan Dias wrote: >> >>> >>> >>> On Fri, Jan 8, 2016 at 7:03 AM, Pubudu Priyashan >>> wrote: >>> >>>> Hi Nuwan, >>>> >>>> The idea is not to keep the peak level constant throughout the duration >>>> of the long running test but, to generate a relatively higher number of >>>> threads lets say for a few hours of the day and stop it on daily basis. >>>> >>> >>> What is the objective of this test? From what I understand, its not a >>> performance test and its not a typical long running test as well. So can >>> you explain what you're trying to achieve and how it benefits the product >>> or any other? When doing performance tests the peak thread count we hit was >>> around 250 and you can use it if you want. But its better to do it with a >>> plan and clear objective. >>> >>> >>>> Appreciate if you could suggest a number for the peak thread count per >>>> single gateway node so we can monitor the behaviour. >>>> >>>> Currently we don't have scripts to support the scenario you suggested. >>>> We will start working on this and create relevant scripts and update you >>>> once we have tested the scenario you have mentioned. Thanks. >>>> >>>> Cheers, >>>> Pubudu. >>>> >>>> Pubudu D.P >>>> Senior Software Engineer - QA Team | WSO2 inc. >>>> Mobile : +94775464547 >>>> >>>> On Thu, Jan 7, 2016 at 4:01 PM, Nuwan Dias wrote: >>>> >>>>> Hi Pubudu, >>>>> >>>>> I don't think its useful to do a long running test at peak load >>>>> because it doesn't happen in reality. Any system can hit peaks, but it >>>>> would be a momentary occurrence rather than a long running situation. >>>>> >
Re: [Dev] [QA] Question on API-M gateway node maximum concurrent threads
Hi Nuwan, Objective of doing a long running test after the release is, in the release time we won't be able to execute a long running test for couple of weeks. Because sometime we have to stop the test to change the packs or integrate with other product with setup or to enable some configs to test a feature, etc. Most of the time we are getting some cloud issue as well(resource issues and set of nodes were getting slow). So most of time we were able to run the long running test for day or 2 days. Therefor we thought of doing a proper long running test against the GA pack for 3 weeks. Last year we did long running test after the release for couple of releases and then we shared our findings(memory growth, exceptions, warnings, etc) with dev teams. So if we can identify a bug at this stage then we can prepare a fix. Regards, Aparna. On Fri, Jan 8, 2016 at 9:22 AM, Nuwan Dias wrote: > > > On Fri, Jan 8, 2016 at 7:03 AM, Pubudu Priyashan wrote: > >> Hi Nuwan, >> >> The idea is not to keep the peak level constant throughout the duration >> of the long running test but, to generate a relatively higher number of >> threads lets say for a few hours of the day and stop it on daily basis. >> > > What is the objective of this test? From what I understand, its not a > performance test and its not a typical long running test as well. So can > you explain what you're trying to achieve and how it benefits the product > or any other? When doing performance tests the peak thread count we hit was > around 250 and you can use it if you want. But its better to do it with a > plan and clear objective. > > >> Appreciate if you could suggest a number for the peak thread count per >> single gateway node so we can monitor the behaviour. >> >> Currently we don't have scripts to support the scenario you suggested. We >> will start working on this and create relevant scripts and update you once >> we have tested the scenario you have mentioned. Thanks. >> >> Cheers, >> Pubudu. >> >> Pubudu D.P >> Senior Software Engineer - QA Team | WSO2 inc. >> Mobile : +94775464547 >> >> On Thu, Jan 7, 2016 at 4:01 PM, Nuwan Dias wrote: >> >>> Hi Pubudu, >>> >>> I don't think its useful to do a long running test at peak load because >>> it doesn't happen in reality. Any system can hit peaks, but it would be a >>> momentary occurrence rather than a long running situation. >>> >>> What would be more useful is to do the long running test under moderate >>> load. This would mimick many real world scenarios. Therefore I would >>> recommend to have the concurrency at 50 threads, using about 1000 access >>> tokens and run the test in such a way that it renews its access tokens from >>> time to time (either when they expire or once every 45 minutes or so). >>> >>> We should also configure the Java Flight Recorder (remotely, to avoid >>> filling up the file system) so that we would have insight into issues if >>> any. Also please make sure that the back-end system you front through the >>> gateway is stable and can withhold the tests. >>> >>> Thanks, >>> NuwanD. >>> >>> On Thu, Jan 7, 2016 at 3:18 PM, Pubudu Priyashan >>> wrote: >>> >>>> >>>> Hi Nuwan, >>>> >>>> We are planning to start a long running test on the API-M 1.10.0 >>>> released pack. As a part of this we need to simulate a peak time in gateway >>>> worker nodes (by sending a large number of concurrent threads) could you >>>> please let us know what is the maximum expected limit of concurrent threads >>>> that we can be served in a single gateway worker node? We will then set up >>>> the long-running tests accordingly. Thanks! >>>> >>>> Cheers, >>>> Pubudu D.P >>>> Senior Software Engineer - QA Team | WSO2 inc. >>>> Mobile : +94775464547 >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Technical Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard
Actually I have used another Nginx to resolve my issue, not a permanent solution. AFAIU this is getting due to httpclient 4.3.1 doesn't support SNI. @IsuruU, Shouldn't it upgrade to httpclient 4.3.2 ? Regards, Aparna. On Fri, Nov 20, 2015 at 11:24 AM, Malintha Adikari wrote: > Hi Aprana, > > I am getting the same issue while accessing APIM distributed cluster nodes > fronted through loadbalancer(nginx) instance. Did you able to solve this > issue ? If so how did you solve it ? > > Regards, > Malintha > > On Wed, Oct 28, 2015 at 2:09 PM, Isuru Udana wrote: > >> Hi Aparna, >> >> Bundles are coming from features, whatever version defined in the product >> pom have no relationship for that. >> >> Thanks. >> >> On Wed, Oct 28, 2015 at 11:20 AM, Aparna Karunarathna >> wrote: >> >>> Hi Isuru, >>> >>> I checked version from the ESB master branch pom[1]. >>> >>> 4.1.2 >>> >>> [1] https://github.com/wso2/product-esb/blob/master/pom.xml >>> >>> Regards, >>> Aparna. >>> >>> On Tue, Oct 27, 2015 at 5:41 AM, Isuru Udana wrote: >>> >>>> Hi Aparna, >>>> >>>> We are using 4.3.1. >>>> >>>> >>>> Thanks. >>>> >>>> On Mon, Oct 26, 2015 at 10:36 AM, Aparna Karunarathna >>>> wrote: >>>> >>>>> Hi Kasun/Isuru, >>>>> >>>>> Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to >>>>> newer version? >>>>> >>>>> @Deep, Thanks for the clarification. >>>>> >>>>> Regards, >>>>> Aparna >>>>> >>>>> On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa >>>>> wrote: >>>>> >>>>>> Hi Aparna, >>>>>> >>>>>> This can happen when the client does not send the SNI[1][2] to the >>>>>> server side to select the proper HTTPS virtual host. In this case NGINX >>>>>> reverse proxy created in the vhost. Most of the modern browsers send SNI >>>>>> to >>>>>> server, therefore you will not observe this when you make the request >>>>>> via a >>>>>> modern browser. >>>>>> >>>>>> Most of the new Java HTTP client libraries also support SNI. As an >>>>>> example, Apache httpclient library support SNI from version 4.3.2 [3]. If >>>>>> you use a library which does not support SNI, you will get this error for >>>>>> HTTPS call going towards services hosted in virtual host environments. >>>>>> >>>>>> [1] https://en.wikipedia.org/wiki/Server_Name_Indication >>>>>> [2] https://www.ietf.org/rfc/rfc3546.txt >>>>>> [3] https://hc.apache.org/news.html >>>>>> >>>>>> On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna < >>>>>> apa...@wso2.com> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I have encountered a weird "hostname in certificate didn't match:" >>>>>>> issue when accessing IS dashboard. My setup details are as follows. >>>>>>> >>>>>>> *Setup Details* >>>>>>> *IS cluster* >>>>>>> - 3 nodes cluster >>>>>>> - Hostname - mgt.is.wso2.com >>>>>>> - Certificate CN - mgt.is.wso2.com >>>>>>> >>>>>>> *BPS cluster* >>>>>>> - 2 nodes cluster (manager/worker) >>>>>>> - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com >>>>>>> - Certificate CN - *.bps.wso2.com >>>>>>> >>>>>>> * Both nodes are fronted by same Nginx plus load balancer. >>>>>>> >>>>>>> [1] >>>>>>> javax.net.ssl.SSLException: hostname in certificate didn't match: < >>>>>>> mgt.is.wso2.com> != <*.bps.wso2.com> >>>>>>> at >>>>>>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238) >>>>>>> at >>>>>>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54) >>>>>>> >>>>>>> &
[Dev] [IS] policies updating logs when deleting user
Hi Johann and IS team,
We have seen following logs when deleting users in IS 5.1.0, Are there any
specific reasons to enable those logs?
[*2015-11-06 18:17:44,394] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Initializing of policy store is started at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,399] INFO
{org.wso2.carbon.identity.entitlement.policy.store.DefaultPolicyDataStore}
- Using Global policy combining algorithm that is defined in configuration
file.*
*[2015-11-06 18:17:44,399] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Start retrieving policies from
org.wso2.carbon.identity.entitlement.policy.store.RegistryPolicyStoreManageModule@1545a815
at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,401] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Finish retrieving policies from
org.wso2.carbon.identity.entitlement.policy.store.RegistryPolicyStoreManageModule@1545a815
at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,402] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Initializing of policy store is finished at : Fri Nov 06 18:17:44 IST
2015*
*[2015-11-06 18:17:44,414] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Initializing of policy store is started at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,415] INFO
{org.wso2.carbon.identity.entitlement.policy.store.DefaultPolicyDataStore}
- Using Global policy combining algorithm that is defined in configuration
file.*
*[2015-11-06 18:17:44,415] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Start retrieving policies from
org.wso2.carbon.identity.entitlement.policy.store.RegistryPolicyStoreManageModule@1545a815
at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,416] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Finish retrieving policies from
org.wso2.carbon.identity.entitlement.policy.store.RegistryPolicyStoreManageModule@1545a815
at : Fri Nov 06 18:17:44 IST 2015*
*[2015-11-06 18:17:44,416] INFO
{org.wso2.carbon.identity.entitlement.policy.finder.CarbonPolicyFinder} -
Initializing of policy store is finished at : Fri Nov 06 18:17:44 IST
2015*
Please clarify.
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages
Hi Nandika/ Chathura/ Hasitha,
Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
that this was getting from extension that introduced in BPS/Dev Studio
which is not compliance with ODE.
*"Those errors can be seen in both standalone and cluster mode. These are
bpel compilation errors logged by ODE server due to the extensions we have
introduced in BPS/Dev Studio, which are not compliance with ODE (They are
not errors actually).*
*If the package get deployed successfully, please ignore those error logs."*
[1] https://wso2.org/jira/browse/BPS-915
Regards,
Aparna
On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda wrote:
> HI,
> Adding to above, some of those tags such as 'xml:space' are not required
> that are added by dev studio. They can be removed from the model without
> affecting any functionality.
>
> Regards,
> Vinod Kavinda
>
> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda wrote:
>
>> Hi all,
>> Those errors can be seen in standalone mode also, they can be seen in
>> carbon logs. These are bpel compilation errors logged by ODE server due to
>> the extensions we have introduced in BPS, which are not compliance with
>> ODE (They are not errors actually).
>> If the package get deployed successfully, please ignore those error logs.
>>
>> Regards,
>> Vinod
>>
>> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna
>> wrote:
>>
>>> Hi all,
>>>
>>> I have attached the bpel package to the jira[1]
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-3950
>>>
>>> Regards,
>>> Aparna
>>>
>>> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana
>>> wrote:
>>>
>>>> Hi,
>>>> Can you attach the actual bpel package generated. It looks like some
>>>> invalid content is generated into the bpel file.
>>>>
>>>> Regards
>>>> Nandika
>>>>
>>>> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna
>>>> wrote:
>>>>
>>>>> Is this intermittent ? Because I also reported this once earlier in
>>>>> dev mail. This was happened intermittently earlier in standalone pack as
>>>>> well.
>>>>> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna"
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Currently we are testing IS workflow feature with a BPS cluster. When
>>>>>> creating a new workflow, we have observed following error at BPS
>>>>>> terminal.
>>>>>>
>>>>>> ERROR
>>>>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>>>>
>>>>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>>>>>> Invalid content was found starting with element 'extensions'. One of '{"
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>>>>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>>>>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>&
Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages
; {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,233] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:138:52:cvc-complex-type.3.2.2:
>>> Attribute 'xml:space' is not allowed to appear in element 'bpel:literal'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,233] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:138:52:cvc-complex-type.3.2.2:
>>> Attribute 'xml:space' is not allowed to appear in element 'bpel:literal'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,235] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:224:56:cvc-complex-type.3.2.2:
>>> Attribute 'xml:space' is not allowed to appear in element 'bpel:literal'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,235] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:224:56:cvc-complex-type.3.2.2:
>>> Attribute 'xml:space' is not allowed to appear in element 'bpel:literal'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,237] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:303:84:cvc-elt.4.2:
>>> Cannot resolve 'p:tExpression' to a type definition for element
>>> 'p:searchBy'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,237] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:303:84:cvc-elt.4.2:
>>> Cannot resolve 'p:tExpression' to a type definition for element
>>> 'p:searchBy'.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,249] WARN
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory} - Validation errors
>>> during parsing, continuing due to
>>> -Dorg.apache.ode.compiler.failOnValidationErrors=false switch
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory}
>>> TID: [-1234] [] [2015-10-28 03:30:39,249] WARN
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory} - Validation errors
>>> during parsing, continuing due to
>>> -Dorg.apache.ode.compiler.failOnValidationErrors=false switch
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory}
>>>
>>>
>>> Any idea about what could be the reason for this? We are not observing
>>> this with standalone BPS or IS with BPS features included.
>>>
>>> Thanks
>>>
>>> --
>>> *Chamila Dilshan Wijayarathna,*
>>> Software Engineer
>>> Mobile:(+94)788193620
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>
--
*Regards,*
*Aparna Karunarathna.*
*Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard
Hi Isuru, I checked version from the ESB master branch pom[1]. 4.1.2 [1] https://github.com/wso2/product-esb/blob/master/pom.xml Regards, Aparna. On Tue, Oct 27, 2015 at 5:41 AM, Isuru Udana wrote: > Hi Aparna, > > We are using 4.3.1. > > > Thanks. > > On Mon, Oct 26, 2015 at 10:36 AM, Aparna Karunarathna > wrote: > >> Hi Kasun/Isuru, >> >> Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to newer >> version? >> >> @Deep, Thanks for the clarification. >> >> Regards, >> Aparna >> >> On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa >> wrote: >> >>> Hi Aparna, >>> >>> This can happen when the client does not send the SNI[1][2] to the >>> server side to select the proper HTTPS virtual host. In this case NGINX >>> reverse proxy created in the vhost. Most of the modern browsers send SNI to >>> server, therefore you will not observe this when you make the request via a >>> modern browser. >>> >>> Most of the new Java HTTP client libraries also support SNI. As an >>> example, Apache httpclient library support SNI from version 4.3.2 [3]. If >>> you use a library which does not support SNI, you will get this error for >>> HTTPS call going towards services hosted in virtual host environments. >>> >>> [1] https://en.wikipedia.org/wiki/Server_Name_Indication >>> [2] https://www.ietf.org/rfc/rfc3546.txt >>> [3] https://hc.apache.org/news.html >>> >>> On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna >>> wrote: >>> >>>> Hi all, >>>> >>>> I have encountered a weird "hostname in certificate didn't match:" >>>> issue when accessing IS dashboard. My setup details are as follows. >>>> >>>> *Setup Details* >>>> *IS cluster* >>>> - 3 nodes cluster >>>> - Hostname - mgt.is.wso2.com >>>> - Certificate CN - mgt.is.wso2.com >>>> >>>> *BPS cluster* >>>> - 2 nodes cluster (manager/worker) >>>> - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com >>>> - Certificate CN - *.bps.wso2.com >>>> >>>> * Both nodes are fronted by same Nginx plus load balancer. >>>> >>>> [1] >>>> javax.net.ssl.SSLException: hostname in certificate didn't match: < >>>> mgt.is.wso2.com> != <*.bps.wso2.com> >>>> at >>>> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238) >>>> at >>>> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54) >>>> >>>> >>>> >>>> When we check the browser cookie, it gave correct certificate. ( >>>> mgt.is.wso2.com), but when we check it from java client[2] it gives >>>> the bps certificate (*.bps.wso2.com) instead of IS. >>>> >>>> [2] >>>> https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/ >>>> >>>> What is the reason for this? Is it my config issue or Nginx issue or >>>> our product issue? >>>> >>>> -- >>>> *Regards,* >>>> >>>> *Aparna Karunarathna.* >>>> >>>> >>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >>>> >>> >>> >>> >>> -- >>> Deependra Ariyadewa >>> WSO2, Inc. http://wso2.com/ http://wso2.org >>> >>> email d...@wso2.com; cell +94 71 403 5996 ; >>> Blog http://risenfall.wordpress.com/ >>> PGP info: KeyID: 'DC627E6F' >>> >>> *WSO2 - Lean . Enterprise . Middleware* >>> >> >> >> >> -- >> *Regards,* >> >> *Aparna Karunarathna.* >> >> >> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >> > > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard
Hi Kasun/Isuru, Currently ESB uses Apache httpclient 4.1.2, shouldn't it upgrade to newer version? @Deep, Thanks for the clarification. Regards, Aparna On Sat, Oct 24, 2015 at 11:38 AM, Deependra Ariyadewa wrote: > Hi Aparna, > > This can happen when the client does not send the SNI[1][2] to the server > side to select the proper HTTPS virtual host. In this case NGINX reverse > proxy created in the vhost. Most of the modern browsers send SNI to server, > therefore you will not observe this when you make the request via a modern > browser. > > Most of the new Java HTTP client libraries also support SNI. As an > example, Apache httpclient library support SNI from version 4.3.2 [3]. If > you use a library which does not support SNI, you will get this error for > HTTPS call going towards services hosted in virtual host environments. > > [1] https://en.wikipedia.org/wiki/Server_Name_Indication > [2] https://www.ietf.org/rfc/rfc3546.txt > [3] https://hc.apache.org/news.html > > On Fri, Oct 23, 2015 at 11:07 AM, Aparna Karunarathna > wrote: > >> Hi all, >> >> I have encountered a weird "hostname in certificate didn't match:" issue >> when accessing IS dashboard. My setup details are as follows. >> >> *Setup Details* >> *IS cluster* >> - 3 nodes cluster >> - Hostname - mgt.is.wso2.com >> - Certificate CN - mgt.is.wso2.com >> >> *BPS cluster* >> - 2 nodes cluster (manager/worker) >> - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com >> - Certificate CN - *.bps.wso2.com >> >> * Both nodes are fronted by same Nginx plus load balancer. >> >> [1] >> javax.net.ssl.SSLException: hostname in certificate didn't match: < >> mgt.is.wso2.com> != <*.bps.wso2.com> >> at >> org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238) >> at >> org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54) >> >> >> >> When we check the browser cookie, it gave correct certificate. ( >> mgt.is.wso2.com), but when we check it from java client[2] it gives the >> bps certificate (*.bps.wso2.com) instead of IS. >> >> [2] >> https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/ >> >> What is the reason for this? Is it my config issue or Nginx issue or our >> product issue? >> >> -- >> *Regards,* >> >> *Aparna Karunarathna.* >> >> >> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >> > > > > -- > Deependra Ariyadewa > WSO2, Inc. http://wso2.com/ http://wso2.org > > email d...@wso2.com; cell +94 71 403 5996 ; > Blog http://risenfall.wordpress.com/ > PGP info: KeyID: 'DC627E6F' > > *WSO2 - Lean . Enterprise . Middleware* > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] "hostname in certificate didn't match:" issue when accessing IS dashboard
Hi all, I have encountered a weird "hostname in certificate didn't match:" issue when accessing IS dashboard. My setup details are as follows. *Setup Details* *IS cluster* - 3 nodes cluster - Hostname - mgt.is.wso2.com - Certificate CN - mgt.is.wso2.com *BPS cluster* - 2 nodes cluster (manager/worker) - Hostnames - Manager - mgt.bps.wso2.com / Worker - wrk.bps.wso2.com - Certificate CN - *.bps.wso2.com * Both nodes are fronted by same Nginx plus load balancer. [1] javax.net.ssl.SSLException: hostname in certificate didn't match: < mgt.is.wso2.com> != <*.bps.wso2.com> at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:238) at org.apache.http.conn.ssl.BrowserCompatHostnameVerifier.verify(BrowserCompatHostnameVerifier.java:54) When we check the browser cookie, it gave correct certificate. ( mgt.is.wso2.com), but when we check it from java client[2] it gives the bps certificate (*.bps.wso2.com) instead of IS. [2] https://darray.wordpress.com/2015/07/12/freak-vulnerability-and-disabling-weak-export-cipher-suites-in-wso2-carbon-4-2-0-based-products/ What is the reason for this? Is it my config issue or Nginx issue or our product issue? -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Table 'is510reg.REG_LOG' doesn't exist" error was thrown when starting the server
Sure, will have a quick look now.
Regards,
Aparna.
On Wed, Oct 7, 2015 at 3:14 PM, Isuruwan Herath wrote:
> Hi Aparna,
>
> Shall we have a quick look at this in the QA set up?
>
> Thanks!
>
> On Wed, Oct 7, 2015 at 3:04 PM, Isura Karunaratne wrote:
>
>> Registry team,
>>
>> Do you have any input on this issue ?
>>
>>
>> Thanks
>> Isura
>> On Wed, Oct 7, 2015 at 12:55 PM, Aparna Karunarathna
>> wrote:
>>
>>> Hi Isuru / Isuruwan,
>>>
>>> I was able to reproduce the issue now, that Table exists.
>>>
>>> ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO} - Failed to
>>> update log batch records . Table 'is510reg.REG_LOG' doesn't exist
>>> java.sql.BatchUpdateException: Table 'is510reg.REG_LOG' doesn't exist
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2056)
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:160)
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.saveLogBatch(JDBCLogsDAO.java:124)
>>> at
>>> org.wso2.carbon.registry.core.utils.LogWriter.logWrite(LogWriter.java:106)
>>> at org.wso2.carbon.registry.core.utils.LogWriter.run(LogWriter.java:91)
>>> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
>>> Table 'is510reg.REG_LOG' doesn't exist
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>>> at com.mysql.jdbc.Util.getInstance(Util.java:386)
>>> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190)
>>> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122)
>>> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
>>> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
>>> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818)
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157)
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460)
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2008)
>>> ... 5 more
>>> [2015-10-07 07:21:51,665] ERROR
>>> {org.wso2.carbon.registry.core.utils.LogWriter} - Unable to save log
>>> records
>>> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to
>>> update log batch records . Table 'is510reg.REG_LOG' doesn't exist
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:177)
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.saveLogBatch(JDBCLogsDAO.java:124)
>>> at
>>> org.wso2.carbon.registry.core.utils.LogWriter.logWrite(LogWriter.java:106)
>>> at org.wso2.carbon.registry.core.utils.LogWriter.run(LogWriter.java:91)
>>> Caused by: java.sql.BatchUpdateException: Table 'is510reg.REG_LOG'
>>> doesn't exist
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2056)
>>> at
>>> com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
>>> at
>>> org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:160)
>>> ... 3 more
>>> Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException:
>>> Table 'is510reg.REG_LOG' doesn't exist
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>>> at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>>> at com.mysql.jdbc.Util.getInstance(Util.java:386)
>>> at com.mysq
Re: [Dev] Table 'is510reg.REG_LOG' doesn't exist" error was thrown when starting the server
Hi Isuru / Isuruwan,
I was able to reproduce the issue now, that Table exists.
ERROR {org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO} - Failed to
update log batch records . Table 'is510reg.REG_LOG' doesn't exist
java.sql.BatchUpdateException: Table 'is510reg.REG_LOG' doesn't exist
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2056)
at
com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:160)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.saveLogBatch(JDBCLogsDAO.java:124)
at
org.wso2.carbon.registry.core.utils.LogWriter.logWrite(LogWriter.java:106)
at org.wso2.carbon.registry.core.utils.LogWriter.run(LogWriter.java:91)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'is510reg.REG_LOG' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818)
at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460)
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2008)
... 5 more
[2015-10-07 07:21:51,665] ERROR
{org.wso2.carbon.registry.core.utils.LogWriter} - Unable to save log
records
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to
update log batch records . Table 'is510reg.REG_LOG' doesn't exist
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:177)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.saveLogBatch(JDBCLogsDAO.java:124)
at
org.wso2.carbon.registry.core.utils.LogWriter.logWrite(LogWriter.java:106)
at org.wso2.carbon.registry.core.utils.LogWriter.run(LogWriter.java:91)
Caused by: java.sql.BatchUpdateException: Table 'is510reg.REG_LOG' doesn't
exist
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2056)
at
com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCLogsDAO.addLogRecords(JDBCLogsDAO.java:160)
... 3 more
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
'is510reg.REG_LOG' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1054)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4190)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4122)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2570)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2731)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2818)
at
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2157)
at
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2460)
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2008)
... 5 more
Regards,
Aparna.
On Wed, Oct 7, 2015 at 11:48 AM, Aparna Karunarathna
wrote:
> Hi Isuru,
>
> To troubleshoot the wso2.war deploying issue, I have dropped and created
> databases several times. Since this is intermittent issue didn't try to
> troubleshoot it much. We have reported this because we got the same issue
> on two different databases(mssql 2012 & mysql 5.6.25 and OSs(Linux,
> Windows).
>
> Regards,
> Aparna
>
> On Wed, Oct 7, 2015 at 11:32 AM, Isura Karunaratne wrote:
>
>> Adding Aparna
>>
>> On Tue, Oct 6, 2015 at 10:41 PM, Isuruwan Herath
>> wrote:
>>
>>> Hi Isura,
>>>
>>> Is it possible to verify that in QA DB, REG_LOG table has been created
>>> in *is510reg* database and access granted t
Re: [Dev] Table 'is510reg.REG_LOG' doesn't exist" error was thrown when starting the server
Hi Isuru, To troubleshoot the wso2.war deploying issue, I have dropped and created databases several times. Since this is intermittent issue didn't try to troubleshoot it much. We have reported this because we got the same issue on two different databases(mssql 2012 & mysql 5.6.25 and OSs(Linux, Windows). Regards, Aparna On Wed, Oct 7, 2015 at 11:32 AM, Isura Karunaratne wrote: > Adding Aparna > > On Tue, Oct 6, 2015 at 10:41 PM, Isuruwan Herath > wrote: > >> Hi Isura, >> >> Is it possible to verify that in QA DB, REG_LOG table has been created in >> *is510reg* database and access granted to the DB user which is >> configured in IS node, to the same database? >> > @Aparna, > Can you verify this? > > Thanks > Isura > >> >> Thanks, >> Isuruwan >> >> On Tue, Oct 6, 2015 at 8:26 PM, Isura Karunaratne wrote: >> >>> >>> Hi, >>>> >>>> QA reported [1] in IS5.1.0 alpha and we observed that the same error >>>> was occurred in ESB [2] and APIM[3] products as well. They resolved these >>>> issues as "Cannot Reproduce" >>>> >>>> @Greg team >>>> >>>> We are also unable to reproduce the issue and what would be the reason >>>> for occurring this issue in QA environment? >>>> >>>> >>>> Thanks >>>> Isura. >>>> >>>> >>>> >>>> [1] https://wso2.org/jira/browse/IDENTITY-3750 >>>> [2] https://wso2.org/jira/browse/ESBJAVA-2539 >>>> [3] https://wso2.org/jira/browse/APIMANAGER-2199 >>>> >>>> >>>> >>>> -- >>>> Isura Dilhara Karunaratne >>>> Senior Software Engineer >>>> >>>> Mob +94 772 254 810 >>>> >>>> >>> >>> >>> -- >>> Isura Dilhara Karunaratne >>> Senior Software Engineer >>> >>> Mob +94 772 254 810 >>> >>> >> >> >> -- >> Isuruwan Herath >> Technical Lead >> >> Contact: +94 776 273 296 >> > > > > -- > Isura Dilhara Karunaratne > Senior Software Engineer > > Mob +94 772 254 810 > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts
Hi Harsha/ Nandika, > > > As Nandika said, I think we don't need to worry about this bps feature in > cluster mode with embeded one. Better to test it with external. > > I'm not sure whether you understood my question or not. Enabling DepSync (SVN) in both nodes is not the problem. My question was when we enable the DepSync in both nodes as committing nodes and fronted by LB , both will try to commit artifacts,then will get svn conflicts. So how to configure the DepSync correctly in 2 nodes cluster fronted by LB ? So your suggestion is to embedded workflow feature cannot be used in cluster mode and need to configure a external BPS? > > In the cluster scenario, its better to point to an external BPS cluster. >> > If we use external BPS, what kind of BPS setup suitable for production setup? Single node or clustered setup? Regards, Aparna. > >> Regards >> Nandika >> >> On Tue, Oct 6, 2015 at 4:06 PM, Aparna Karunarathna >> wrote: >> >>> Hi Johann and IS team, >>> >>> How to enable the SVN in IS cluster to sync BPEL and HT artifacts among >>> nodes? >>> >>> In Worker/Manager cluster setup, manager node is used to commit >>> artifacts, but for IS cluster doesn't have manager node, both nodes are >>> behave as manager nodes. Basically this issue is getting when we >>> configuring workflows by pointing to the embedded BPS server from manager >>> node. >>> >>> Furthermore, with external BPS server we don't get this kind problem. >>> >>> Please clarify. >>> >>> -- >>> *Regards,* >>> >>> *Aparna Karunarathna.* >>> >>> >>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Nandika Jayawardana >> WSO2 Inc ; http://wso2.com >> lean.enterprise.middleware >> > > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [IS] How to enable the SVN in IS cluster to sync BPEL and HT artifacts
Hi Johann and IS team, How to enable the SVN in IS cluster to sync BPEL and HT artifacts among nodes? In Worker/Manager cluster setup, manager node is used to commit artifacts, but for IS cluster doesn't have manager node, both nodes are behave as manager nodes. Basically this issue is getting when we configuring workflows by pointing to the embedded BPS server from manager node. Furthermore, with external BPS server we don't get this kind problem. Please clarify. -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Greg5.0.0 Integration test execute with Cluster Deployment
Hi Deep, We installed a Oracle12c database in QA cloud and try to start the server by pointing to Oracle 12c db, but we couldn't. Oracle 12c is architectural(Multitenant Architecture) wise totally different to Oracle 11g. We need more time to understand Oracle 12c features and configurations. :( If you are familiar Oracle 12c please help on this or is there anyone who familiar Oracle 12c please help. Regards, Aparna. On Sat, Aug 22, 2015 at 9:00 PM, Deependra Ariyadewa wrote: > > > On Sat, Aug 22, 2015 at 1:36 PM, Thayalan wrote: > >> Please find the details below. >> >> nginx/1.7.9 & Oracle/11g >> > > I think it is time to test on 12c. 11g is not supported any more. > > https://blogs.oracle.com/UPGRADE/entry/premier_support_for_oracle_11 > > On Sat, Aug 22, 2015 at 12:18 AM, Deependra Ariyadewa >> wrote: >> >>> >>> >>> On Thu, Aug 20, 2015 at 6:50 PM, Chaminda Jayawardena >> > wrote: >>> >>>> Hi All, >>>> >>>> Is $Subject possible? AFAIK still this is possible only for some of >>>> wso2 products. Please advice and guide to do this(Share any document if >>>> exist). >>>> >>>> Please find the cluster details below, which we currently have. >>>> -2 Greg instances as manager nodes with external IDP(IS5.0.0) >>>> -External Apache Solr instance >>>> -All fronted by nginx >>>> >>> >>> What is the NGINX version in your cluster deployment >>> >>>> >>>> -with Oracle database >>>> >>> >>> What is the Oracle version in your cluster setup. >>> >>> >>> >>>> >>>> >>>> >>>> -- >>>> Thanks & Regards >>>> >>>> *Chaminda Jayawardena* >>>> Senior Software Engineer - QA >>>> WSO2 Inc. - http://wso2.com >>>> +94-77-7725234 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Deependra Ariyadewa >>> WSO2, Inc. http://wso2.com/ http://wso2.org >>> >>> email d...@wso2.com; cell +94 71 403 5996 ; >>> Blog http://risenfall.wordpress.com/ >>> PGP info: KeyID: 'DC627E6F' >>> >>> *WSO2 - Lean . Enterprise . Middleware* >>> >> >> >> >> -- >> Regards, >> Thayalan Sivapaleswararajah >> Associate Technical Lead - QA >> Mob: +94(0)777872485 >> Tel : +94(0)(11)2145345 >> Fax : +94(0)(11)2145300 >> Email: thaya...@wso2.com >> >> >> *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.* >> >> > > > -- > Deependra Ariyadewa > WSO2, Inc. http://wso2.com/ http://wso2.org > > email d...@wso2.com; cell +94 71 403 5996 ; > Blog http://risenfall.wordpress.com/ > PGP info: KeyID: 'DC627E6F' > > *WSO2 - Lean . Enterprise . Middleware* > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Clarification on GREG Clustering Setup for 5.0.0
Hi Sagara, That's not a dummy node, it used to do some sort of governance and that's the real registry node and other two nodes behave as Management nodes. This kind of deployment pattern propose by Greg team to avoid the subscription related issues. @Senaka and Ajith, please elaborate more details about this deployment pattern. Regards, Aparna. On Tue, Aug 4, 2015 at 5:29 PM, Sagara Gunathunga wrote: > > > On Tue, Aug 4, 2015 at 5:26 PM, Chandana Napagoda > wrote: > >> HI Evanthika/Chalitha, >> >> In most cases there is no dummy node to manage the subscriptions. There >> you have to define "mgtHost" and "remoteinstance" properly. But better to >> validate other scenarios as well. >> > > I'm curious to know what is 'dummy node" concept here, can someone > explain ? > > Thanks ! > >> >> Regards, >> Chandana >> >> On Tue, Aug 4, 2015 at 5:01 PM, Evanthika Amarasiri >> wrote: >> >>> Hi Shazni, >>> >>> On Tue, Aug 4, 2015 at 4:01 PM, Shazni Nazeer wrote: >>> >>>> Hi Pubudu, >>>> >>>> There are few ways you can do the testing. In addition to the two >>>> methods you have mentioned >>>> >>> >>> As per the offline discussion I had with Chandana, we were under the >>> impression that a dummy node is not required and we don't recommend this >>> topology anymore. Can you please confirm? >>> >>> >>> >>>> following basic clustering topologies can be used as well. >>>> >>>> Two G-Reg nodes in cluster without fronting with a load balancer >>>> Two G-Reg nodes in cluster without fronting with load balancer >>>> One G-Reg instance with just a jdbc mount (This is not a clustered >>>> scenario) >>>> >>>> For your second question, from G-Reg 5.0.0 inwards, API-M related >>>> scripts won't be packed in the G-Reg server by default. It'll only be >>>> available if you install API-M features on top of G-Reg. Nevertheless, for >>>> clustering to work, you do not necessarily need to have a datasource >>>> configuration for API-M db. So that part can be omitted in the default >>>> pack. >>>> >>>> This would need to be reflected in the doc as well [1] >>>> >>>> [1] https://wso2.org/jira/browse/DOCUMENTATION-2109 >>>> >>>> Shazni Nazeer >>>> Mob : +94 37331 >>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer >>>> Blog : http://shazninazeer.blogspot.com >>>> >>>> On Tue, Aug 4, 2015 at 1:13 PM, Pubudu Priyashan >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> We are currently testing the GREG clustering setup for 5.0.0. >>>>> >>>>> 1. Previously in 4.6 GREG version the recommended setup was with three >>>>> GREG instances with one dummy node and the registry mount. >>>>> But in 5.0.0 we've been told to test the clustering set up with two >>>>> GREG manager nodes using one IS instance as the external IDP with user >>>>> store and registry mount. >>>>> >>>>> Can you please confirm what is the recommended set up for GREG 5.0.0 >>>>> and the document link? >>>>> >>>>> >>>>> 2. Also in GREG clustering tutorial with nginx[1], it requires user to >>>>> access '$GREG_HOME/dbscripts/apimgt/mysql.sql' location. But apimgt >>>>> directory is not available in GREG 5.0.0 version by default. Do we need to >>>>> update the document [1] to reflect most recent clustering setup? >>>>> >>>>> Appreciate your advise on above two questions. Thanks. >>>>> >>>>> [1] >>>>> https://docs.wso2.com/display/CLUSTER420/Clustering+Governance+Registry+with+Nginx#ClusteringGovernanceRegistrywithNginx-Environment >>>>> >>>>> >>>>> Best Regards, >>>>> Pubudu D.P >>>>> Senior Software Engineer - QA Team | WSO2 inc. >>>>> Mobile : +94775464547 >>>>> >>>> >>>> >>> >> >> >> -- >> *Chandana Napagoda* >> Senior Software Engineer >> WSO2 Inc. - http://wso2.org >> >> *Email : chand...@wso2.com **Mobile : +94718169299 >> <%2B94718169299>* >> >> *Blog :http://cnapagoda.blogspot.com <http://cnapagoda.blogspot.com>* >> >> > > > -- > Sagara Gunathunga > > Architect; 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 > > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack
Thanks Prasad. Regards, Aparna. On Tue, Jul 14, 2015 at 3:54 PM, Prasad Tissera wrote: > Hi Aparna, > > For carbon 4.4.0 it should directly inside conf directory. [1]. Default > file location as per the p2.inf is under multitenancy folder. But in the > product build can copy the file to the correct location in the bin.xml. > From next release this should be properly fixed in either user core [1] or > tenant.common feature p2.inf [2]. > > [1]. > https://github.com/wso2/carbon4-kernel/blob/v4.4.0/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/config/TenantMgtXMLProcessor.java#L48 > [2]. > https://github.com/wso2/carbon-multitenancy/blob/master/features/tenant-mgt/org.wso2.carbon.tenant.common.server.feature/src/main/resources/p2.inf#L4 > > Regards, > Prasad. > > On Tue, Jul 14, 2015 at 3:11 PM, Aparna Karunarathna > wrote: > >> Hi Johann/Prasad, >> >> What is the correct location of the 'tenant-mgt.xml' file? >> >> Regards, >> Aparna. >> >> >> On Tue, Jul 14, 2015 at 2:57 PM, Godwin Amila Shrimal >> wrote: >> >>> Hi Sandapa, >>> >>> AFAK 'tenant-mgt.xml' is located in *repository/conf *not in >>> *repository/conf/**multitenancy *in earlier versions.I am not sure is >>> there is a decision to move *repository/conf/**multitenancy *in current >>> versions >>> *.* >>> Thanks >>> Godwin >>> >>> On Tue, Jul 14, 2015 at 2:50 PM, Sandapa Handakumbura >>> wrote: >>> >>>> Hi, >>>> >>>> In ESB 4.9.0, 'tenant-mgt.xml' is located in *repository/conf *(the >>>> usual location). Is that the correct location or should it be >>>> *repository/conf/**multitenancy *? >>>> >>>> Please confirm. >>>> >>>> Thanks, >>>> Sandapa >>>> >>>> On Mon, Jul 13, 2015 at 12:48 PM, Aparna Karunarathna >>>> wrote: >>>> >>>>> >>>>> "tenant-mgt.xml" file is included under repository/conf/multitenancy >>>>> directory in the ES200 pack. >>>>> >>>>> @Johann/ SameeraJ / SameeraM, Have we changed the location of tenant- >>>>> mgt.xml file or is this an error? >>>>> >>>>> Regards, >>>>> Aparna. >>>>> >>>>> On Mon, Jul 13, 2015 at 12:36 PM, Aparna Karunarathna >>>> > wrote: >>>>> >>>>>> Even IS 510 M3 pack doesn't have the tenant-mgt.xml file. >>>>>> >>>>>> Regards, >>>>>> Aparna >>>>>> >>>>>> >>>>>> On Mon, Jul 13, 2015 at 11:35 AM, Thayalan wrote: >>>>>> >>>>>>> Hi Team, >>>>>>> >>>>>>> As per the mail discussion in [1] & [2] what I understood was >>>>>>> tenant-mgt.xml file has to be included with all the products. But, I'm >>>>>>> not >>>>>>> clear on the final verdict whether to include $Subject with all the >>>>>>> products that we ship including GREG. Please confirm. >>>>>>> >>>>>>> The same issue persist with the latest GREG pack as well. >>>>>>> >>>>>>> 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon >>>>>>> packs? >>>>>>> 2. Is it possible to re-factor current 'product distribution process' >>>>>>> -- >>>>>>> Regards, >>>>>>> Thayalan Sivapaleswararajah >>>>>>> Associate Technical Lead - QA >>>>>>> Mob: +94(0)777872485 >>>>>>> Tel : +94(0)(11)2145345 >>>>>>> Fax : +94(0)(11)2145300 >>>>>>> Email: thaya...@wso2.com >>>>>>> >>>>>>> >>>>>>> *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 >>>>>>&
Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack
Hi Johann/Prasad, What is the correct location of the 'tenant-mgt.xml' file? Regards, Aparna. On Tue, Jul 14, 2015 at 2:57 PM, Godwin Amila Shrimal wrote: > Hi Sandapa, > > AFAK 'tenant-mgt.xml' is located in *repository/conf *not in > *repository/conf/**multitenancy *in earlier versions.I am not sure is > there is a decision to move *repository/conf/**multitenancy *in current > versions > *.* > Thanks > Godwin > > On Tue, Jul 14, 2015 at 2:50 PM, Sandapa Handakumbura > wrote: > >> Hi, >> >> In ESB 4.9.0, 'tenant-mgt.xml' is located in *repository/conf *(the >> usual location). Is that the correct location or should it be >> *repository/conf/**multitenancy *? >> >> Please confirm. >> >> Thanks, >> Sandapa >> >> On Mon, Jul 13, 2015 at 12:48 PM, Aparna Karunarathna >> wrote: >> >>> >>> "tenant-mgt.xml" file is included under repository/conf/multitenancy >>> directory in the ES200 pack. >>> >>> @Johann/ SameeraJ / SameeraM, Have we changed the location of tenant- >>> mgt.xml file or is this an error? >>> >>> Regards, >>> Aparna. >>> >>> On Mon, Jul 13, 2015 at 12:36 PM, Aparna Karunarathna >>> wrote: >>> >>>> Even IS 510 M3 pack doesn't have the tenant-mgt.xml file. >>>> >>>> Regards, >>>> Aparna >>>> >>>> >>>> On Mon, Jul 13, 2015 at 11:35 AM, Thayalan wrote: >>>> >>>>> Hi Team, >>>>> >>>>> As per the mail discussion in [1] & [2] what I understood was >>>>> tenant-mgt.xml file has to be included with all the products. But, I'm not >>>>> clear on the final verdict whether to include $Subject with all the >>>>> products that we ship including GREG. Please confirm. >>>>> >>>>> The same issue persist with the latest GREG pack as well. >>>>> >>>>> 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon >>>>> packs? >>>>> 2. Is it possible to re-factor current 'product distribution process' >>>>> -- >>>>> Regards, >>>>> Thayalan Sivapaleswararajah >>>>> Associate Technical Lead - QA >>>>> Mob: +94(0)777872485 >>>>> Tel : +94(0)(11)2145345 >>>>> Fax : +94(0)(11)2145300 >>>>> Email: thaya...@wso2.com >>>>> >>>>> >>>>> *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.* >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Regards,* >>>> >>>> *Aparna Karunarathna.* >>>> >>>> >>>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >>>> >>> >>> >>> >>> -- >>> *Regards,* >>> >>> *Aparna Karunarathna.* >>> >>> >>> *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Sandapa Handakumbura >> Associate Technical Lead >> WSO2.Inc. ; http://wso2.com/ >> M : +94777115866 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Godwin Amila Shrimal* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: *+94772264165* > linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>* > twitter: https://twitter.com/godwinamila > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack
"tenant-mgt.xml" file is included under repository/conf/multitenancy directory in the ES200 pack. @Johann/ SameeraJ / SameeraM, Have we changed the location of tenant-mgt.xml file or is this an error? Regards, Aparna. On Mon, Jul 13, 2015 at 12:36 PM, Aparna Karunarathna wrote: > Even IS 510 M3 pack doesn't have the tenant-mgt.xml file. > > Regards, > Aparna > > > On Mon, Jul 13, 2015 at 11:35 AM, Thayalan wrote: > >> Hi Team, >> >> As per the mail discussion in [1] & [2] what I understood was >> tenant-mgt.xml file has to be included with all the products. But, I'm not >> clear on the final verdict whether to include $Subject with all the >> products that we ship including GREG. Please confirm. >> >> The same issue persist with the latest GREG pack as well. >> >> 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon >> packs? >> 2. Is it possible to re-factor current 'product distribution process' >> -- >> Regards, >> Thayalan Sivapaleswararajah >> Associate Technical Lead - QA >> Mob: +94(0)777872485 >> Tel : +94(0)(11)2145345 >> Fax : +94(0)(11)2145300 >> Email: thaya...@wso2.com >> >> >> *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.* >> >> > > > -- > *Regards,* > > *Aparna Karunarathna.* > > > *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533 <0714002533>* > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG 5.00 Alpha] tenant-mgt.xml file not included with the pack
Even IS 510 M3 pack doesn't have the tenant-mgt.xml file. Regards, Aparna On Mon, Jul 13, 2015 at 11:35 AM, Thayalan wrote: > Hi Team, > > As per the mail discussion in [1] & [2] what I understood was > tenant-mgt.xml file has to be included with all the products. But, I'm not > clear on the final verdict whether to include $Subject with all the > products that we ship including GREG. Please confirm. > > The same issue persist with the latest GREG pack as well. > > 1. [Dev] Why are we not shipping the tenant-mgt.xml file with Carbon packs > ? > 2. Is it possible to re-factor current 'product distribution process' > -- > Regards, > Thayalan Sivapaleswararajah > Associate Technical Lead - QA > Mob: +94(0)777872485 > Tel : +94(0)(11)2145345 > Fax : +94(0)(11)2145300 > Email: thaya...@wso2.com > > > *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.* > > -- *Regards,* *Aparna Karunarathna.* *Associate Technical Lead - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] App Manager Release 1.0.0 - QA Plan changes
Hi Sumedha and Dinusha, Could you please mention non tested features and areas so far? If we can get it now, Nuwan & Asanthi can focus on those areas. Regards, Aparna. On Wed, May 6, 2015 at 2:12 PM, Nuwan Silva wrote: > We are setting up the cluster and will be doing a long running test. > further more plan to do a stress test by creating 100+ web applications. > > Regards, > NuwanS. > > On Wed, May 6, 2015 at 2:04 PM, Dinusha Senanayaka > wrote: > >> Hi Asanthi, >> >> Feature list looks ok. Additionally we need to give priority for, >> - Cluster setup >> - Testing with IS Service pack >> - Long running test >> >> Regards, >> Dinusha. >> >> On Wed, May 6, 2015 at 1:51 PM, Asanthi Kulasinghe >> wrote: >> >>> Hi Dinusha, >>> >>> As discussed during the meeting , can you please confirm whether the >>> list given below covers all the required features. >>> >>> - App life cycle and docs >>> - App Visibility >>> - Integration with BAM >>> - BPS integration - Workflows >>> - XACML >>> - JWT >>> - OAuth >>> - Samples >>> - Throttling >>> - App Discovery >>> - Deploy Sample feature >>> - Session replication >>> - Single log out >>> - User roles >>> - Cluster scenarios >>> - Enterprise subscription >>> - Skip Creating proxy Services >>> - Integrating with EMM (iOS) >>> - Long running and stress tests >>> - Testing with Oracle >>> - Testing in Windows >>> >>> >>> >> >> >> -- >> Dinusha Dilrukshi >> Associate Technical Lead >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94725255071 >> Blog: http://dinushasblog.blogspot.com/ >> >> _______ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > > *Nuwan Silva* > *Senior Software Engineer - QA* > Mobile: +9477 980 4543 > > WSO2 Inc. > lean . enterprise . middlewear. > http://www.wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Regards,* *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON][SS] Incorrect Behavior - Carbon Login by Changing Default User
[adding carbon team] On Mon, Feb 16, 2015 at 6:19 PM, Chaminda Jayawardena wrote: > Hi All, > > Noticed an incorrect behavior in carbon login when it changed the default > carbon user's username and password by below steps. > > 1. Changed the username and password in repository/conf/user-mgt.xml [in a > Storage Server fresh pack] > ** > * ssadmin* > * Ss@dmin123* > ** > > 2. Remove all in repository/database/ > 3. Remove all in repository/data/org.wso2.carbon.directory/ > 4. Start the server with -Dsetup > 5. Try to log in to new user name and password which we set in above[1] - > this is ok > 6. and then try to log in with admin/admin - this is also working but > should not be worked. > > Please correct if I missed anything here. > > Please find the jira : https://wso2.org/jira/browse/SS-528 > > -- > Thanks & Regards > > *Chaminda Jayawardena* > Senior Software Engineer - QA > WSO2 Inc. - http://wso2.com > +94-77-7725234 > -- *Regards,* *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] SS 1.5.0 Release Testing Status
Hi All, SS is scheduled to released on this Friday(13th Feb), but QA team has observed secondary user creation issue in SS and reported under carbon jira[1]. This might be a kernel patch to fix this issue. As per the discussion had with Sameera & carbon team, first they has to test the carbon 4.3 patching process and then to fix it. [1] https://wso2.org/jira/browse/CARBON-15142 Regards, Aparna On Tue, Feb 10, 2015 at 11:55 PM, Chaminda Jayawardena wrote: > Hi All, > > Please find the update on SS 1.5.0 release testing. > > We have covered the following high-level areas so far. > > 1. RSS Manager >-Postgresql >-MySql >-MSSQL >-H2 > 2. Cassandra Keyspaces > 3. Hadoop File System - Pending > > Test case document, find here [1] > > Below types and count of issues on [2] are in open status; > Highest - 2 > High -10 > > [1]. > https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Aj1RxSLVRSX3dER3ckRJblM0WlRlT3FkTWZBVDFJRkE&usp=sharing > [2]. https://wso2.org/jira/issues/?jql=project%20%3D%20SS > > -- > Thanks & Regards > > *Chaminda Jayawardena* > Senior Software Engineer - QA > WSO2 Inc. - http://wso2.com > +94-77-7725234 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Regards,* *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 13 Release
Hi Chanika/ Anjana, We did a smoke test on latest DSS 3.2.2 pack and no blocking issues were observed. Regards, Aparna. On Mon, Dec 1, 2014 at 6:35 PM, Chanika Geeganage wrote: > Hi Aparna, > > The new pack and the p2-repo can be found from > https://svn.wso2.org/repos/wso2/scratch/chunk13-release/01-12-2014 > > Thanks > > On Mon, Dec 1, 2014 at 12:10 PM, Anjana Fernando wrote: > >> Hi Aparna, >> >> I hope other aspects of DSS has been tested, so yeah, we can wait for the >> HZ fixes to test this specific scenario. >> >> Cheers, >> Anjana. >> >> On Mon, Dec 1, 2014 at 10:27 AM, Aparna Karunarathna >> wrote: >> >>> Hi Anjana & Chanika, >>> >>> Due to the hazelcast issues [1] & [2], Is it OK to stop testing and will >>> wait for new pack? So far we have verified the fixes that has been >>> identified in the last build(15/11/2014). >>> >>> [1] https://wso2.org/jira/browse/CARBON-15096 >>> [2] https://wso2.org/jira/browse/CARBON-15097 >>> >>> >>> Regards, >>> Aparna. >>> >>> >>> On Fri, Nov 28, 2014 at 5:51 PM, Chanika Geeganage >>> wrote: >>> >>>> The new pack can be found from >>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/28-11-2014/ >>>> >>>> On Fri, Nov 28, 2014 at 5:28 AM, Chanika Geeganage >>>> wrote: >>>> >>>>> p2-repo is available at >>>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/27-11-2014/p2-repo/ >>>>> >>>>> On Thu, Nov 27, 2014 at 10:39 PM, Chanika Geeganage >>>>> wrote: >>>>> >>>>>> The latest pack can be downloaded from >>>>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/27-11-2014/wso2dss-3.2.2.zip >>>>>> >>>>>> Thanks >>>>>> >>>>>> On Sat, Nov 15, 2014 at 1:08 PM, Chanika Geeganage >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> The new DSS 3.2.2 pack is available at >>>>>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/15-11-2014-DSS/wso2dss-3.2.2.zip >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On Fri, Nov 14, 2014 at 3:25 PM, Chanika Geeganage >>>>>> > wrote: >>>>>>> >>>>>>>> Hi Aparna, >>>>>>>> >>>>>>>> Building the p2-repo is halted as some of the released artifacts >>>>>>>> are not deployed to nexus. See "Nested categories released in chunk-11 >>>>>>>> are >>>>>>>> not deployed in nexus". Once this issue is sorted out, I will build the >>>>>>>> p2-repo and update the thread. >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> On Fri, Nov 14, 2014 at 8:40 AM, Aparna Karunarathna < >>>>>>>> apa...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi Chanika, >>>>>>>>> >>>>>>>>> Can you please share the p2 repo as well? >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Aparna. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Nov 13, 2014 at 9:19 PM, Chanika Geeganage < >>>>>>>>> chan...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Please find the latest DSS 3.2.2 pack from >>>>>>>>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/13-11-2014-DSS/wso2dss-3.2.2.zip >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> On Tue, Nov 11, 2014 at 8:14 PM, Maninda Edirisooriya < >>>>>>>>>> mani...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Fixed the build and latest DSS and BAM packs are available at >>>>>>>>>>> https://svn.wso2.org/repos/wso2/people/maninda/BAM_packs/2014-11-11/ >>>>>&
[Dev] ESB log4j file gets replaced with DSS log4j file when installing features using p2 repo
Hi Sameera, In the DSS 3.2.2 testing cycle I have installed the DSS 3.2.2 all features to the ESB 4.8.1 from latest p2 repo, when I installed, ESB log4j (original ESB) file gets replaced with DSS log4j file instead of appending the log4j file. What is the correct behavior of replacing or appending file of the original pack when installing features from p2 repo? Regards, -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Chunk 13 Release
Hi Anjana & Chanika, Due to the hazelcast issues [1] & [2], Is it OK to stop testing and will wait for new pack? So far we have verified the fixes that has been identified in the last build(15/11/2014). [1] https://wso2.org/jira/browse/CARBON-15096 [2] https://wso2.org/jira/browse/CARBON-15097 Regards, Aparna. On Fri, Nov 28, 2014 at 5:51 PM, Chanika Geeganage wrote: > The new pack can be found from > https://svn.wso2.org/repos/wso2/scratch/chunk13-release/28-11-2014/ > > On Fri, Nov 28, 2014 at 5:28 AM, Chanika Geeganage > wrote: > >> p2-repo is available at >> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/27-11-2014/p2-repo/ >> >> On Thu, Nov 27, 2014 at 10:39 PM, Chanika Geeganage >> wrote: >> >>> The latest pack can be downloaded from >>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/27-11-2014/wso2dss-3.2.2.zip >>> >>> Thanks >>> >>> On Sat, Nov 15, 2014 at 1:08 PM, Chanika Geeganage >>> wrote: >>> >>>> Hi, >>>> >>>> The new DSS 3.2.2 pack is available at >>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/15-11-2014-DSS/wso2dss-3.2.2.zip >>>> >>>> Thanks >>>> >>>> On Fri, Nov 14, 2014 at 3:25 PM, Chanika Geeganage >>>> wrote: >>>> >>>>> Hi Aparna, >>>>> >>>>> Building the p2-repo is halted as some of the released artifacts are >>>>> not deployed to nexus. See "Nested categories released in chunk-11 are not >>>>> deployed in nexus". Once this issue is sorted out, I will build the >>>>> p2-repo >>>>> and update the thread. >>>>> >>>>> Thanks >>>>> >>>>> On Fri, Nov 14, 2014 at 8:40 AM, Aparna Karunarathna >>>>> wrote: >>>>> >>>>>> Hi Chanika, >>>>>> >>>>>> Can you please share the p2 repo as well? >>>>>> >>>>>> Regards, >>>>>> Aparna. >>>>>> >>>>>> >>>>>> On Thu, Nov 13, 2014 at 9:19 PM, Chanika Geeganage >>>>>> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Please find the latest DSS 3.2.2 pack from >>>>>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/13-11-2014-DSS/wso2dss-3.2.2.zip >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On Tue, Nov 11, 2014 at 8:14 PM, Maninda Edirisooriya < >>>>>>> mani...@wso2.com> wrote: >>>>>>> >>>>>>>> Fixed the build and latest DSS and BAM packs are available at >>>>>>>> https://svn.wso2.org/repos/wso2/people/maninda/BAM_packs/2014-11-11/ >>>>>>>> >>>>>>>> >>>>>>>> *Maninda Edirisooriya* >>>>>>>> Senior Software Engineer >>>>>>>> >>>>>>>> *WSO2, Inc.*lean.enterprise.middleware. >>>>>>>> >>>>>>>> *Blog* : http://maninda.blogspot.com/ >>>>>>>> *E-mail* : mani...@wso2.com >>>>>>>> *Skype* : @manindae >>>>>>>> *Twitter* : @maninda >>>>>>>> >>>>>>>> On Tue, Nov 11, 2014 at 2:13 PM, Maninda Edirisooriya < >>>>>>>> mani...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Yes. Yesterday night I built both DSS and BAM and there was a >>>>>>>>> build break and a BAM internal defect. Therefore was not able to >>>>>>>>> release >>>>>>>>> it. At the moment we are in the process of fixing these issues. >>>>>>>>> >>>>>>>>> >>>>>>>>> *Maninda Edirisooriya* >>>>>>>>> Senior Software Engineer >>>>>>>>> >>>>>>>>> *WSO2, Inc.*lean.enterprise.middleware. >>>>>>>>> >>>>>>>>> *Blog* : http://maninda.blogspot.com/ >>>>>>>>> *E-mail* : mani...@wso2.com >>>>>>>>> *Skype* : @manindae >>>>>>>>> *Twitter* : @maninda >>>>>>>>>
Re: [Dev] Chunk 13 Release
Hi Chanika, Can you please share the p2 repo as well? Regards, Aparna. On Thu, Nov 13, 2014 at 9:19 PM, Chanika Geeganage wrote: > Hi, > > Please find the latest DSS 3.2.2 pack from > https://svn.wso2.org/repos/wso2/scratch/chunk13-release/13-11-2014-DSS/wso2dss-3.2.2.zip > > Thanks > > On Tue, Nov 11, 2014 at 8:14 PM, Maninda Edirisooriya > wrote: > >> Fixed the build and latest DSS and BAM packs are available at >> https://svn.wso2.org/repos/wso2/people/maninda/BAM_packs/2014-11-11/ >> >> >> *Maninda Edirisooriya* >> Senior Software Engineer >> >> *WSO2, Inc.*lean.enterprise.middleware. >> >> *Blog* : http://maninda.blogspot.com/ >> *E-mail* : mani...@wso2.com >> *Skype* : @manindae >> *Twitter* : @maninda >> >> On Tue, Nov 11, 2014 at 2:13 PM, Maninda Edirisooriya >> wrote: >> >>> Yes. Yesterday night I built both DSS and BAM and there was a build >>> break and a BAM internal defect. Therefore was not able to release it. At >>> the moment we are in the process of fixing these issues. >>> >>> >>> *Maninda Edirisooriya* >>> Senior Software Engineer >>> >>> *WSO2, Inc.*lean.enterprise.middleware. >>> >>> *Blog* : http://maninda.blogspot.com/ >>> *E-mail* : mani...@wso2.com >>> *Skype* : @manindae >>> *Twitter* : @maninda >>> >>> On Tue, Nov 11, 2014 at 1:17 PM, Chanika Geeganage >>> wrote: >>> >>>> Hi, >>>> >>>> Both BAM and DSS are added to chunk-13. Yesterday there was some issues >>>> found in the built BAM pack during smoke test. Maninda will be able to give >>>> more details about the issues. We will try to resolve those issues and >>>> provide RC packs today. >>>> >>>> Thanks >>>> >>>> >>>> On Tue, Nov 11, 2014 at 11:56 AM, Nuwan Dias wrote: >>>> >>>>> AFAIK only DSS is going on chunk-13. @Chanika, can you confirm please? >>>>> >>>>> BAM/APIM have moved to chunk-14. Ratha is building packs now and we >>>>> should be able to provide packs within the day. >>>>> >>>>> Thanks, >>>>> NuwanD. >>>>> >>>>> On Tue, Nov 11, 2014 at 11:52 AM, Aparna Karunarathna >>>> > wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Since the Chunk 13 release date scheduled on 3rd week of November, >>>>>> can you build all chunk 13 packs in the builder machine and share the >>>>>> latest packs and p2 repo with us. >>>>>> >>>>>> >>>>>> Regards, >>>>>> -- >>>>>> *Aparna Karunarathna.* >>>>>> >>>>>> >>>>>> *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533 >>>>>> <0714002533>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Nuwan Dias >>>>> >>>>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>>>> email : nuw...@wso2.com >>>>> Phone : +94 777 775 729 >>>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards.. >>>> >>>> Chanika Geeganage >>>> Software Engineer >>>> WSO2, Inc.; http://wso2.com >>>> >>>> >>> >> > > > -- > Best Regards.. > > Chanika Geeganage > Software Engineer > Mobile : +94773522586 > WSO2, Inc.; http://wso2.com > > -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Chunk 13 Release
Hi, Since the Chunk 13 release date scheduled on 3rd week of November, can you build all chunk 13 packs in the builder machine and share the latest packs and p2 repo with us. Regards, -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM 2.5.0 Release testing
st:9160 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> hive.incremental.processing.intermediate.results.cassandra.userName >>>>>> admin >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> hive.incremental.processing.intermediate.results.cassandra.password >>>>>> admin >>>>>> >>>>>> >>>>>> >>>>>> Shavantha Weerasinghe >>>>>> Senior Software Engineer QA >>>>>> WSO2, Inc. >>>>>> lean.enterprise.middleware. >>>>>> http://wso2.com >>>>>> http://wso2.org >>>>>> Tel : 94 11 214 5345 >>>>>> Fax :94 11 2145300 >>>>>> >>>>>> >>>>>> On Mon, Nov 3, 2014 at 6:12 PM, Dunith Dhanushka >>>>>> wrote: >>>>>> >>>>>>> Hi , >>>>>>> >>>>>>> Please note that when setting this up in the research cloud, turn >>>>>>> off the iptables by '*sudo service iptables stop*'. Otherwise it'll >>>>>>> block internode communications. >>>>>>> >>>>>>> Regards, >>>>>>> Dunith >>>>>>> >>>>>>> On Mon, Nov 3, 2014 at 11:53 AM, Dunith Dhanushka >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Aparna, >>>>>>>> >>>>>>>> I have completed the puppet script upgrade for puppet version 3.7 >>>>>>>> and tested them on a Centos cluster. Please find the attached guide for >>>>>>>> setup instructions. >>>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> Dunith >>>>>>>> >>>>>>>> BAM 2.5.0 Distributed Setup with Puppet 3.7 >>>>>>>> <https://docs.google.com/a/wso2.com/document/d/1-BfLkgk6xDD-sd11xBbW5I0ZQodwUE1WuUUEl1nwAK4/edit?usp=drive_web> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Oct 29, 2014 at 11:58 AM, Dunith Dhanushka >>>>>>> > wrote: >>>>>>>> >>>>>>>>> Hi Aparna, >>>>>>>>> >>>>>>>>> I have completed the scripts for BAM and Cassandra nodes. But >>>>>>>>> still need to work on Hadoop scripts. I have started testing them on >>>>>>>>> the >>>>>>>>> centos cluster created in the research cloud. >>>>>>>>> >>>>>>>>> Hopefully by today EOD I'll be able to finish testing with full >>>>>>>>> BAM cluster. >>>>>>>>> >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Dunith >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 29, 2014 at 11:40 AM, Aparna Karunarathna < >>>>>>>>> apa...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi Dunith, >>>>>>>>>> >>>>>>>>>> Any update on puppet scripts? >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Aparna. >>>>>>>>>> >>>>>>>>>> On Mon, Oct 27, 2014 at 10:42 AM, Sewmini Jayaweera < >>>>>>>>>> sewm...@wso2.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Aparna, >>>>>>>>>>> >>>>>>>>>>> I tested following issues, >>>>>>>>>>> >>>>>>>>>>> [1] https://wso2.org/jira/browse/BAM-1611 >>>>>>>>>>> [2] https://wso2.org/jira/browse/BAM-1515 >>>>>>>>>>> [3] https://redmine.wso2.com/issues/3186 >>>>>>>>>>> >>>>>>>>>>> Issue [1] and [2] were fixed. >>>>>>>>>>> >>>>>>>>>>> in order to test issu
Re: [Dev] BAM 2.5.0 Release testing
7;t like to create unnecessary user).
Regards,
Aparna.
On Mon, Nov 3, 2014 at 6:16 PM, Rasanjaya Subasinghe
wrote:
> Hi all,
>
> Set '*sudo chkconfig iptables off ' *to disable the iptable service.
>
> thanks
>
> On Mon, Nov 3, 2014 at 6:12 PM, Dunith Dhanushka wrote:
>
>> Hi ,
>>
>> Please note that when setting this up in the research cloud, turn off the
>> iptables by '*sudo service iptables stop*'. Otherwise it'll block
>> internode communications.
>>
>> Regards,
>> Dunith
>>
>> On Mon, Nov 3, 2014 at 11:53 AM, Dunith Dhanushka
>> wrote:
>>
>>> Hi Aparna,
>>>
>>> I have completed the puppet script upgrade for puppet version 3.7 and
>>> tested them on a Centos cluster. Please find the attached guide for setup
>>> instructions.
>>>
>>>
>>> Regards,
>>> Dunith
>>>
>>> BAM 2.5.0 Distributed Setup with Puppet 3.7
>>> <https://docs.google.com/a/wso2.com/document/d/1-BfLkgk6xDD-sd11xBbW5I0ZQodwUE1WuUUEl1nwAK4/edit?usp=drive_web>
>>>
>>>
>>> On Wed, Oct 29, 2014 at 11:58 AM, Dunith Dhanushka
>>> wrote:
>>>
>>>> Hi Aparna,
>>>>
>>>> I have completed the scripts for BAM and Cassandra nodes. But still
>>>> need to work on Hadoop scripts. I have started testing them on the centos
>>>> cluster created in the research cloud.
>>>>
>>>> Hopefully by today EOD I'll be able to finish testing with full BAM
>>>> cluster.
>>>>
>>>>
>>>> Regards,
>>>> Dunith
>>>>
>>>>
>>>> On Wed, Oct 29, 2014 at 11:40 AM, Aparna Karunarathna
>>>> wrote:
>>>>
>>>>> Hi Dunith,
>>>>>
>>>>> Any update on puppet scripts?
>>>>>
>>>>> Regards,
>>>>> Aparna.
>>>>>
>>>>> On Mon, Oct 27, 2014 at 10:42 AM, Sewmini Jayaweera
>>>>> wrote:
>>>>>
>>>>>> Hi Aparna,
>>>>>>
>>>>>> I tested following issues,
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/BAM-1611
>>>>>> [2] https://wso2.org/jira/browse/BAM-1515
>>>>>> [3] https://redmine.wso2.com/issues/3186
>>>>>>
>>>>>> Issue [1] and [2] were fixed.
>>>>>>
>>>>>> in order to test issue [3] I created an email adaptor and when
>>>>>> sending a email contains text as e-mail body got following error
>>>>>>
>>>>>> [2014-10-27 10:23:36,317] INFO
>>>>>> {org.apache.axis2.builder.BuilderUtil} - OMException in getSOAPBuilder
>>>>>> org.apache.axiom.om.OMException:
>>>>>> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'm'
>>>>>> (code 109) in prolog; expected '<'
>>>>>> at [row,col {unknown-source}]: [1,1]
>>>>>> at
>>>>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>>>>>> at
>>>>>> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
>>>>>> at java.lang.Thread.run(Thread.java:745)
>>>>>>
>>>>>> Similar issue is being reported by Shavantha -
>>>>>> https://wso2.org/jira/browse/BAM-1830
>>>>>>
>>>>>> Thank You.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Sewmini Jayaweera
>>>>>> *Software Engineer - QA Team*
>>>>>> Mobile: +94 (0) 773 381 250
>>>>>> sewm...@wso2.com
>>>>>>
>>>>>> On Fri, Oct 24, 2014 at 5:52 PM, Shavantha Weerasinghe <
>>>>>> shavan...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Inosh
>>>>>>>
>>>>>>> When we create a stream the payload is generated in xml format as
>>>>>>> below[1] however, when the email is sent with this in the body the BAM
>>>>>>> throws an exception "INFO {org.apache.axis2.builder.BuilderUtil} -
>>>>>>> OMException in getSOAPBuilder
>>>>>>> org.apache.axiom.soap.SOAPProcessingException: First Element must
>>>>>>> contain the l
[Dev] Dep Sync in Analyzer and Receiver nodes
Hi Anjana/KasunG/suho, According to the new BAM 2.5.0 deployment pattern [1] we have configured the BAM cluster with 11 nodes(4 cassandra, 3 hadoop, 2 analyzer and 2 receiver). Since BAM 2.5.0 is releasing with CEP features, we have to enable the dep sync for receiver nodes as well. Therefore one of the Analyzer/Receiver nodes were configured as RW nodes and other analyzer/receiver nodes were configured as RO nodes and pointed to a single svn repo. Toolboxes can be deployed to the Analyzer RW node and CEP input adapters to the Receiver RW node. We have seen svn conflicts when both RW nodes were trying to commit to svn repo. Therefore, how to configure the Dep Sync for Analyzer/Receiver nodes in BAM 2.5.0 clustered setup? Please advice. [1] https://docs.wso2.com/display/CLUSTER420/Deploying+BAM+with+Puppet Regards, -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] BAM 2.5.0 Release testing
Hi Dunith,
Any update on puppet scripts?
Regards,
Aparna.
On Mon, Oct 27, 2014 at 10:42 AM, Sewmini Jayaweera
wrote:
> Hi Aparna,
>
> I tested following issues,
>
> [1] https://wso2.org/jira/browse/BAM-1611
> [2] https://wso2.org/jira/browse/BAM-1515
> [3] https://redmine.wso2.com/issues/3186
>
> Issue [1] and [2] were fixed.
>
> in order to test issue [3] I created an email adaptor and when sending a
> email contains text as e-mail body got following error
>
> [2014-10-27 10:23:36,317] INFO {org.apache.axis2.builder.BuilderUtil} -
> OMException in getSOAPBuilder
> org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'm'
> (code 109) in prolog; expected '<'
> at [row,col {unknown-source}]: [1,1]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
> at
> org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:204)
> at java.lang.Thread.run(Thread.java:745)
>
> Similar issue is being reported by Shavantha -
> https://wso2.org/jira/browse/BAM-1830
>
> Thank You.
>
>
>
> Sewmini Jayaweera
> *Software Engineer - QA Team*
> Mobile: +94 (0) 773 381 250
> sewm...@wso2.com
>
> On Fri, Oct 24, 2014 at 5:52 PM, Shavantha Weerasinghe > wrote:
>
>> Hi Inosh
>>
>> When we create a stream the payload is generated in xml format as
>> below[1] however, when the email is sent with this in the body the BAM
>> throws an exception "INFO {org.apache.axis2.builder.BuilderUtil} -
>> OMException in getSOAPBuilder
>> org.apache.axiom.soap.SOAPProcessingException: First Element must contain
>> the local name, Envelope , but found events". If we send the payload on
>> email as [2] the exception is not thrown. Is this the expected behaviour
>>
>> [1] system generated payload
>>
>>
>>
>> 45
>> data1
>> data4
>> data4
>> data2
>> data3
>> data1
>> data3
>> data2
>>
>>
>> data5
>>
>>
>> data5
>> data3
>> data4
>> data1
>> 645565
>>
>>
>>
>>
>> [2] with soap envelope
>> http://www.w3.org/2003/05/soap-envelope";
>> xmlns:ser="http://services.samples";
>> xmlns:xsd="http://services.samples/xsd";>
>>
>>
>>
>>
>>
>> 100
>> data3> method>
>> data5<
>> /character_set_encoding>
>> data5> address>
>> data3
>> data1
>> data2
>> data4
>> data1
>>
>>
>> data2
>>
>>
>> data3
>> data1
>> data1
>> data4
>> 323232
>>
>>
>>
>>
>>
>>
>>
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Thu, Oct 23, 2014 at 2:10 PM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> Hi Aparna/Asanthi
>>>
>>> Hi Guys
>>>
>>> The attachment on google drive has all that is needed to try MQTT flow
>>>
>>> regards,
>>> mqttex.zip
>>> <https://docs.google.com/a/wso2.com/file/d/0B3pVKBDCKX9lYTgxcXM2QlFDMEE/edit?usp=drive_web>
>>>
>>>
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>> On Wed, Oct 22, 2014 at 3:12 PM, Anjana Fernando
>>> wrote:
>>>
>>>> Hi Aparna,
>>>>
>>>> First, use the versions by default mentioned in the puppet setup. Then
>>>> after that, you can move into Apache Cassandra 2.0.x and DSE Cassandra 2.0
>>>> based one. Hadoop use the same mentioned in the puppet setup, that is the
>>>> stable v1 version.
>>>>
>>
Re: [Dev] BAM 2.5.0 Release testing
Hi Anjana, As we discussed(Anjana, Evanthika & myself), due to the limited time frame we have to prioritize the testing scope. BAM Cluster should be configured using puppet scripts. Therefore can you please specify the exact Cassandra & hadoop versions to test. Regards, Aparna. On Wed, Oct 22, 2014 at 11:26 AM, Asanthi Kulasinghe wrote: > Hi, > > Can we please have a p2 repo to be used for this? > > Regards > Asanthi > > On Tue, Oct 21, 2014 at 8:39 PM, Shavantha Weerasinghe > wrote: > >> Hi Aparna >> >> I have started work on the test scenarios for feature ID#3186 related to >> Multiple Transport/Data Format Support in BAM >> >> regards, >> >> Shavantha Weerasinghe >> Senior Software Engineer QA >> WSO2, Inc. >> lean.enterprise.middleware. >> http://wso2.com >> http://wso2.org >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> >> >> On Tue, Oct 21, 2014 at 2:24 PM, Yasith Tharindu wrote: >> >>> Given access to the nominated people. >>> >>> On Mon, Oct 20, 2014 at 5:19 PM, Evanthika Amarasiri >> > wrote: >>> >>>> Hi Yasith, >>>> >>>> It would be great if we you can grant us access to the QA cloud asap >>>> since we need to start setting up the environments and start testing the >>>> products. The release is on the 24th (Oct). >>>> >>>> Regards, >>>> Evanthika >>>> >>>> On Mon, Oct 20, 2014 at 5:15 PM, Rasanjaya Subasinghe < >>>> rasanj...@wso2.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> The new setup is almost configured and linux bases images are already >>>>> uploaded and tested.And newly system can be accessible by OT credentials. >>>>> But before gain access to the private cloud you need to ask yasith to >>>>> enable the user credentials. >>>>> >>>>> Thank you. >>>>> >>>> >>>> >>> >>> >>> -- >>> ~Thanks >>> Yasith Tharindu,*WSO2 Inc,* >>> Blog : http://www.yasith.info >>> Twitter : http://twitter.com/yasithnd >>> LinkedIn : http://www.linkedin.com/in/yasithnd >>> GPG ID : *57CEE66E* >>> >>> *US : +1 (408) 754-7388 <%28408%29%20754-7388> - 51926* >>> *LK : +94 (011) 214 5345 - 1005739* >>> "' lean "' enterprise '" middleware '" http://wso2.com >>> >> >> > > > -- > *Asanthi Kulasinghe* > WSO2 Inc; http://www.wso2.com/. > Mobile: +94777355522 > > > -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] BAM 2.5.0 Release testing
Hi, This is just an update about BAM 2.5.0 Release testing. Last Friday we have started $subject and currently we are testing on local setup's, due to the unavailability of the QA cloud. @Rasanjaya, What is the status of the QA cloud and when will be available the QA cloud ? As per the QA test plane[1], we are testing Integration test Scenarios, Support jira's, etc [1] https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0Ak_8WRenbwnhdE8yY0RmakZMbDZ5amMxZEdUVzgwbEE#gid=0 Regards, -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CARBON] Reproducing CARBON-14572
Hi Gayashan, Seems like I haven't attached the carbon log, very sorry for that. This was happened when we were doing basic bpel testing in BPS clustered setup(might be a milestones pack). These issues were not reproducible very easily and also cannot give the exact steps to reproduce the issue. Regards, Aparna On Thu, Oct 16, 2014 at 7:48 PM, Gayashan Amarasinghe wrote: > Hi Aparna, > > Regarding $subject at [1], Can you provide more information to reproduce > this error? While performing which task, did you get these errors? What > sort of errors was it throwing? Since the description in the JIRA is too > generic, the errors could be thrown either due to issues in carbon server > or in BPS features. Would be really helpful if you can provide more > information. > > [1] https://wso2.org/jira/browse/CARBON-14572 > > Thanks. > /Gayashan > > -- > *Gayashan Amarasinghe* > Software Engineer | Platform TG > WSO2, Inc. | http://wso2.com > lean. enterprise. middleware > > Mobile : +94718314517 > Blog : gayashan-a.blogspot.com > -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] AM tables creating issues in API-M 1.7.0 (Oracle & mssql)
Hi All, We have observed $subject. Server started using -Dsetup and no start-up errors were thrown, server started successfully. When check databases we have seen tables are getting created partially in Oracle [1] database, then I have executed the oracle script manually and some tables were created with errors. In mssql [2] script should be updated. Please have a look. [1] https://wso2.org/jira/browse/APIMANAGER-2163 [2] https://wso2.org/jira/browse/APIMANAGER-2159 Regards, -- *Aparna Karunarathna.* *Senior Software Engineer - QAWSO2 Inc.Mobile: 0714002533* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Warnings when doing deployment synchronization of Carbon 4.2 based products (ESB 4.8)
Hi Sagara, We didn't observe any OOM issues after adding the svnkit(dropins dir). Regards, Aparna. On Sun, Apr 6, 2014 at 5:45 PM, Sagara Gunathunga wrote: > > > > On Sun, Apr 6, 2014 at 1:59 PM, Sagara Gunathunga wrote: > >> >> >> Any idea ? >> > > Applied the suggested workarounds on issues[1], [2] then ran into > following heap space issue. > > java.lang.OutOfMemoryError: Java heap space > > Dumping heap to > /Users/sagara/dev/clients/dev-services/BPFrance/setups/bpi/esb-active/repository/logs/heap-dump.hprof > ... > > Unable to create > /Users/sagara/dev/clients/dev-services/BPFrance/setups/bpi/esb-active/repository/logs/heap-dump.hprof: > File exists > > [2014-04-06 14:14:02,745] ERROR - CarbonDeploymentSchedulerTask Error > while running deployment scheduler.. > > java.lang.OutOfMemoryError: Java heap space > > at java.util.Arrays.copyOf(Arrays.java:2882) > > at > java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) > > at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390) > > at java.lang.StringBuffer.append(StringBuffer.java:224) > > at > org.tmatesoft.svn.core.SVNErrorMessage.getFullMessage(SVNErrorMessage.java:257) > > at > org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:58) > > at > org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:163) > > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:364) > > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:272) > > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:265) > > at > org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:261) > > at > org.tmatesoft.svn.core.wc.SVNStatusClient.doStatus(SVNStatusClient.java:316) > > at > org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:296) > > at > org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:278) > > at > org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:542) > > at > org.tigris.subversion.svnclientadapter.svnkit.SvnKitClientAdapter.getStatus(SvnKitClientAdapter.java:144) > > at > org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:528) > > at > org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:521) > > at > org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.cleanupDeletedFiles(SVNBasedArtifactRepository.java:533) > > at > org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.checkout(SVNBasedArtifactRepository.java:399) > > at > org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer.checkout(DeploymentSynchronizer.java:181) > > at > org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:87) > > at > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:165) > > at > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:123) > > > > FYI I'm running local svn 1.7.10 based repo on my mac 10.9.1 machine. > > > [1] - https://wso2.org/jira/browse/BPS-346 > [2] - https://wso2.org/jira/browse/BPS-346 > > >> >> Thanks ! >> >> >> On Wed, Jan 29, 2014 at 5:08 AM, Nirmal Fernando wrote: >> >>> Hi, >>> >>> Noticed $subject. What could be the reason? >>> >>> [2014-01-29 03:04:39,918] WARN - SvnOutputParser Can't find a svn >>> action for svn output line : A (bin) >>> repository/deployment/server/axis2services/Version.aar >>> [2014-01-29 03:04:39,943] WARN - SvnOutputParser Can't find a svn >>> action for svn output line : A (bin) >>> repository/deployment/server/axis2services/Echo.aar >>> [2014-01-29 03:04:41,042] WARN - SvnOutputParser Can't find a svn >>> action for svn output line : A (bin) >>> repository/deployment/server/webapps/STRATOS_ROOT/images/logo.gif >>> >>> >>> -- >>> >>> Thanks & regards, >>> Nirmal >>> >>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >>> Mobile: +94715779733 >>> Blog: http://nirmalfdo.blogspot.com/ >>> >>> >>> >>> ___
[Dev] WSO2 Developer Studio 3.2.0 to create BPEL samples
Hi, Is it possible to use the WSO2 Developer Studio 3.2.0 to create BPEL samples for BPS release testing ? If so, please share sample guides and doc links. -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Admin user is getting blocked to accessing the API store when create a tenant in Greg, hence cannot use the REST API
I was able to login to the API store using admin user from following link, but the admin user cannot subscribe a API. https://localhost:9443/productapistore/?tenant=carbon.super On Tue, Oct 15, 2013 at 9:48 PM, Aparna Karunarathna wrote: > admin user doesn't get a link to login to API store and it's only showing > the tenant link. > > > On Tue, Oct 15, 2013 at 9:34 PM, Sumedha Rubasinghe wrote: > >> Aparna, >> Could you explain the issue again? >> >> >> On Tue, Oct 15, 2013 at 9:23 PM, Aparna Karunarathna wrote: >> >>> Hi, >>> >>> The admin user is getting blocked to accessing the API store, when >>> creates a tenant in Greg, hence admin user cannot use the REST APIs. Its >>> new feature that has been added to API-M 1.5, anyhow it's not a valid >>> scenario for Greg point of view. This should be an issue with any >>> product that use the API store. Please clarify. >>> >>> -- >>> *Regards, >>> Aparna Karunarathna.* >>> *Senior Software Engineer - QA >>> WSO2 Inc. >>> Mobile: 0714002533*** >>> *Tel : 94 11 214 5345* >>> *Fax : 94 11 2145300* >>> >> >> >> >> -- >> /sumedha >> m: +94 773017743 >> b : bit.ly/sumedha >> > > > > -- > *Regards, > Aparna Karunarathna.* > *Senior Software Engineer - QA > WSO2 Inc. > Mobile: 0714002533*** > *Tel : 94 11 214 5345* > *Fax : 94 11 2145300* > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Admin user is getting blocked to accessing the API store when create a tenant in Greg, hence cannot use the REST API
admin user doesn't get a link to login to API store and it's only showing the tenant link. On Tue, Oct 15, 2013 at 9:34 PM, Sumedha Rubasinghe wrote: > Aparna, > Could you explain the issue again? > > > On Tue, Oct 15, 2013 at 9:23 PM, Aparna Karunarathna wrote: > >> Hi, >> >> The admin user is getting blocked to accessing the API store, when >> creates a tenant in Greg, hence admin user cannot use the REST APIs. Its >> new feature that has been added to API-M 1.5, anyhow it's not a valid >> scenario for Greg point of view. This should be an issue with any >> product that use the API store. Please clarify. >> >> -- >> *Regards, >> Aparna Karunarathna.* >> *Senior Software Engineer - QA >> WSO2 Inc. >> Mobile: 0714002533*** >> *Tel : 94 11 214 5345* >> *Fax : 94 11 2145300* >> > > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Admin user is getting blocked to accessing the API store when create a tenant in Greg, hence cannot use the REST API
Hi, The admin user is getting blocked to accessing the API store, when creates a tenant in Greg, hence admin user cannot use the REST APIs. Its new feature that has been added to API-M 1.5, anyhow it's not a valid scenario for Greg point of view. This should be an issue with any product that use the API store. Please clarify. -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] "A tenant with same domain already exist" returned when creating tenants on a clustered setup
Still we are getting this on clustered setup.
TID: [0] [ELB] [2013-10-11 15:21:47,364] WARN {org.apache.synapse.transport
.passthru.TargetHandler} - http-outgoing-344: Connection time out while in
state: REQUEST_DONE {org.apache.synapse.transport.passthru.TargetHandler}
TID: [0] [ELB] [2013-10-11 15:21:47,721] WARN {org.apache.synapse.transport
.passthru.SourceHandler} - Connection time out after request is read:
http-incoming-5370 {org.apache.synapse.transport.passthru.SourceHandler}
TID: [0] [ELB] [2013-10-11 15:21:48,367] INFO {org.wso2.carbon.lb.endpoint.
endpoint.TenantAwareLoadBalanceEndpoint} - Failed over to
Host:192.168.18.1, Remote Host:null, Port: 4200, HTTP:10763, HTTPS:10443,
Domain: greg.qa.460.domain, Sub-domain:mgt, Active:true {org.wso2.carbon.lb.
endpoint.endpoint.TenantAwareLoadBalanceEndpoint}
Regards,
Aparna.
On Wed, Oct 9, 2013 at 2:53 PM, Evanthika Amarasiri wrote:
> When creating a tenant in a ESB worker/manager separated setup, fronted by
> an ELB, I see the same behavior (A dead page is returned once the tenant is
> created and we see the INFO message - CommonUtil A tenant with same
> domain already exist. Please use a different domain name. tenant domain:
> evan.com.)
>
> [1] - https://wso2.org/jira/browse/CARBON-14240
>
> Regards,
> Evanthika
>
> On Wed, Jul 31, 2013 at 8:31 PM, Afkham Azeez wrote:
>
>>
>>
>>
>> On Tue, Jul 30, 2013 at 9:24 AM, Nirodha Pramod wrote:
>>
>>>
>>>
>>>
>>> On Tue, Jul 30, 2013 at 9:20 AM, Nirmal Fernando wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jul 30, 2013 at 9:11 AM, Nirodha Pramod wrote:
>>>>
>>>>> Hi Nirmal,
>>>>>
>>>>> On Tue, Jul 30, 2013 at 8:49 AM, Nirmal Fernando wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 30, 2013 at 8:20 AM, Evanthika Amarasiri <
>>>>>> evanth...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We noticed the error mentioned in $subject when creating tenants on
>>>>>>> our App-server worker manager separated setup, fronted by an ELB.
>>>>>>> However,
>>>>>>> the tenants do get created but they are not activated.
>>>>>>>
>>>>>>> We see the below exception at ELB console.
>>>>>>>
>>>>>>> TID: [0] [ELB] [2013-07-30 08:18:17,377] WARN
>>>>>>> {org.apache.synapse.transport.passthru.SourceHandler} - Connection time
>>>>>>> out after request is read: http-incoming-22
>>>>>>> {org.apache.synapse.transport.passthru.SourceHandler}
>>>>>>> TID: [0] [ELB] [2013-07-30 08:18:17,471] WARN
>>>>>>> {org.apache.synapse.transport.passthru.TargetHandler} -
>>>>>>> http-outgoing-20:
>>>>>>> Connection time out while in state: REQUEST_DONE
>>>>>>> {org.apache.synapse.transport.passthru.TargetHandler}
>>>>>>> TID: [0] [ELB] [2013-07-30 08:18:18,472] INFO
>>>>>>> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -
>>>>>>> Failed over to Host:192.168.4.52, Remote Host:null, Port: 4250,
>>>>>>> HTTP:10763, HTTPS:10443, Domain: as.qa.420.domain, Sub-domain:mgt,
>>>>>>> Active:true
>>>>>>> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}
>>>>>>>
>>>>>>
>>>>>> FYI this doesn't mean that the tenant is not activated, but for some
>>>>>> reason connection to a member of the cluster got timed out and ELB failed
>>>>>> over to another member of the cluster.
>>>>>>
>>>>>
>>>>> Here the Tenant does not get activated, and we cannot login with the
>>>>> created tenant. You have to activate the tenant manually to log in. A
>>>>>
>>>>
>>>> Yes, this is a separate issue AFAIU.
>>>>
>>>>
>>>>> lso as we observed due to the time out it (probably ELB) tries to
>>>>> send another tenant creation submit request which results in logging
>>>>> "A tenant with same domain already exist" in AS side.
>>>>>
>>>>
>>>> Well, ELB doesn't send any such tenant creation requests AFAIK.
>>>>
>>> Well what I meant was a retry or something in that sort.(just guessed :)
>>> )
>>>
>>>
>> Yes you are correct. On certain error codes, ELB fails over, and in this
>> case, it is a timeout, and failover has happened. This timeout will go away
>> once we fix the tenant creation time issue. We narrowed it down to the time
>> it takes to copy the tenant's theme in its registry space. Senaka has
>> committed a fix, which improves the tenant creation time.
>>
>> ___
>> 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
>
>
--
*Regards,
Aparna Karunarathna.*
*Senior Software Engineer - QA
WSO2 Inc.
Mobile: 0714002533***
*Tel : 94 11 214 5345*
*Fax : 94 11 2145300*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] P2 repo issues
Hi, Seems like P2 repo is not compatible with chunk2 builds, we have observed following issues when testing the P2 repo and Greg. - Cannot install AppServer features to the Greg [1] from P2 repo. - Startup errors when installed the Greg features to Carbon server[2]. - Created Greg pack is unusable and cannot add wsdl and list the metadata. [1] https://wso2.org/jira/browse/CARBON-14514 [2] https://wso2.org/jira/browse/CARBON-14512 [3] https://wso2.org/jira/browse/CARBON-14513 -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Build] Packs built on 5th Oct - with revision 187322
Hi Sanjeewa, Please share the P2 repo as well. Regards, Aparna. On Mon, Oct 7, 2013 at 10:46 AM, Nuwan Silva wrote: > Hi All, > > Are these packs testable? Can we proceed with testing with these packs? > > Thanks, > NuwanS. > > > On Mon, Oct 7, 2013 at 10:30 AM, Mohanadarshan Vivekanandalingam < > mo...@wso2.com> wrote: > >> Hi Shavantha, >> >> CEP packs does not contains the changes that discussed.. >> >> Regards, >> Mohan >> >> >> On Mon, Oct 7, 2013 at 9:23 AM, Shavantha Weerasinghe > > wrote: >> >>> hi All >>> is the CEP pack with the changes discussed ? >>> regards, >>> >>> Shavantha Weerasinghe >>> Senior Software Engineer QA >>> WSO2, Inc. >>> lean.enterprise.middleware. >>> http://wso2.com >>> http://wso2.org >>> Tel : 94 11 214 5345 >>> Fax :94 11 2145300 >>> >>> >>> >>> On Sat, Oct 5, 2013 at 10:26 AM, Sanjeewa Malalgoda >>> wrote: >>> >>>> Hi Team, >>>> Please download latest packs from following url[1]. >>>> Last updated revision was 187322 >>>> There were integration test failures in BAM/APIM/CEP and ESB. All of >>>> them are similar and sent separate notes to dev mail list. >>>> >>>> >>>> [1] >>>> http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/ >>>> wso2am-1.5.0.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2am-1.5.0.zip> >>>> >>>> >>>> wso2bam-2.4.0.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2bam-2.4.0.zip> >>>> >>>> >>>> wso2cep-3.0.0.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2cep-3.0.0.zip> >>>> >>>> >>>> wso2esb-4.8.0.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2esb-4.8.0.zip> >>>> >>>> wso2greg-4.6.0.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2greg-4.6.0.zip> >>>> >>>> >>>> wso2ues-1.0.1.zip<http://ec2-54-224-94-128.compute-1.amazonaws.com/chunk-02/N_05-10-13/wso2ues-1.0.1.zip> >>>> >>>> >>>> >>>> >>>> Thanks, >>>> sanjeewa. >>>> -- >>>> * >>>> * >>>> *Sanjeewa Malalgoda* >>>> Senior Software Engineer >>>> WSO2 Inc. >>>> Mobile : +94713068779 >>>> >>>> <http://sanjeewamalalgoda.blogspot.com/>blog >>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.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 >>> >>> >> >> >> -- >> *V. Mohanadarshan* >> *Software Engineer,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com * >> *lean.enterprise.middleware.* >> * >> * >> email: mo...@wso2.com >> phone:(+94) 771117673 >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > * > * > *Nuwan Silva > * > *Senior Software Engineer - QA* > Mobile: +94779804543 > > WSO2 Inc. > lean . enterprise . middlewear. > http://www.wso2.com > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Two carbonapps directories are available in the Carbon 4.2.0 packs
Hi, Two carbonapps directories are available in the Carbon 4.2.0 packs, Which carbonapps directory is the correct one? -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Warning - We don't support method overloading. Ignoring [getAttributeName] was observed when starting the Greg
Yes, same warning.
Regards,
Aparna
On Wed, Sep 25, 2013 at 12:59 PM, Senaka Fernando wrote:
> Hi Aparna,
>
> Is this https://wso2.org/jira/browse/IDENTITY-1849?
>
> Thanks,
> Senaka.
>
>
> On Wed, Sep 25, 2013 at 12:34 PM, Aparna Karunarathna wrote:
>
>> Hi,
>>
>> Following warning message was observed when starting the Greg (24th Sep)
>> pack.
>>
>> TID: [0] [Greg] [2013-09-25 10:56:58,282] WARN
>> {org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator} - We don't
>> support method overloading. Ignoring [getAttributeName]
>> {org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator}
>>
>>
>> --
>> *Regards,
>> Aparna Karunarathna.*
>> *Senior Software Engineer - QA
>> WSO2 Inc.
>> Mobile: 0714002533***
>> *Tel : 94 11 214 5345*
>> *Fax : 94 11 2145300*
>>
>
>
>
> --
> * <http://us13.wso2con.com/>
> *
> *
> *
> *Senaka Fernando*
> Senior 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
>
--
*Regards,
Aparna Karunarathna.*
*Senior Software Engineer - QA
WSO2 Inc.
Mobile: 0714002533***
*Tel : 94 11 214 5345*
*Fax : 94 11 2145300*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Warning - We don't support method overloading. Ignoring [getAttributeName] was observed when starting the Greg
Hi,
Following warning message was observed when starting the Greg (24th Sep)
pack.
TID: [0] [Greg] [2013-09-25 10:56:58,282] WARN
{org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator} - We don't
support method overloading. Ignoring [getAttributeName]
{org.apache.axis2.description.java2wsdl.DefaultSchemaGenerator}
--
*Regards,
Aparna Karunarathna.*
*Senior Software Engineer - QA
WSO2 Inc.
Mobile: 0714002533***
*Tel : 94 11 214 5345*
*Fax : 94 11 2145300*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] unique constraint (GOV46USER.SYS_C0097056) violated - REGISTRY-1941
Hi all, Still we are getting this issue [1] on Greg clustered setup. [1] https://wso2.org/jira/browse/REGISTRY-1941 Please have a look. -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ELB 2.1.0 with GREG 4.6.0 clustered setup
Hi Nirmal, Shall we try to reproduce this error on our QA setup? Regards, Aparna On Sun, Sep 15, 2013 at 5:39 PM, Nirmal Fernando wrote: > Hi Aparna, > > I'm having hard time on reproducing these issues, unfortunately. I'm > testing on an EC2 machine and using latest packs. > > > On Sun, Sep 15, 2013 at 5:04 PM, Nirmal Fernando wrote: > >> Hi Aparna, >> >> I've replied to thread [1]. Please have a look. And now I'm trying with >> the latest Greg pack too. >> >> >> >> On Fri, Sep 13, 2013 at 2:56 PM, Aparna Karunarathna wrote: >> >>> Hi, >>> >>> We are unable to test on ELB fronted Greg clustered setup due to timeout >>> issue, because of this issue we are testing the Greg without the ELB. We >>> have reported this issue with chunk01 release as well (Refer mail thread >>> [1]). >>> >>> Therefore we won't be able to release the ELB 2.1.0 with chunk02 release >>> as well. This will be a really big issue customer point of view, because >>> there's no way of using our product with our ELB. Please provide us a >>> testable ELB 2.1.0 pack. >>> >>> [1] [Dev] - Accessing the Management Console after page times out >>> returns a "Connection reset" error without redirecting to the Login page >>> >>> -- >>> *Regards, >>> Aparna Karunarathna.* >>> *Senior Software Engineer - QA >>> WSO2 Inc. >>> Mobile: 0714002533*** >>> *Tel : 94 11 214 5345* >>> *Fax : 94 11 2145300* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Thanks & regards, >> Nirmal >> >> Senior Software Engineer- Platform Technologies Team, WSO2 Inc. >> Mobile: +94715779733 >> Blog: http://nirmalfdo.blogspot.com/ >> >> > > > -- > > Thanks & regards, > Nirmal > > Senior Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] ELB 2.1.0 with GREG 4.6.0 clustered setup
Hi, We are unable to test on ELB fronted Greg clustered setup due to timeout issue, because of this issue we are testing the Greg without the ELB. We have reported this issue with chunk01 release as well (Refer mail thread [1]). Therefore we won't be able to release the ELB 2.1.0 with chunk02 release as well. This will be a really big issue customer point of view, because there's no way of using our product with our ELB. Please provide us a testable ELB 2.1.0 pack. [1] [Dev] - Accessing the Management Console after page times out returns a "Connection reset" error without redirecting to the Login page -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Packs built on Sep 10
Publisher and Store webapps are not working on 10th Sept Greg pack, therefore unable to test the REST API. Regards, Aparna. On Wed, Sep 11, 2013 at 7:29 PM, Aparna Karunarathna wrote: > We are continuing our Greg testing with RC8 ELB pack. > > > On Wed, Sep 11, 2013 at 7:17 PM, Aparna Karunarathna wrote: > >> >> Still we are getting timeout issue frequently and not able to connect >> with Greg console from 1 user. Seems like spinning issue is fixed in the >> ELB. We have set *http. connection. timeout=12* in the >> passthru-http.properties file as suggested by Nirmal, but no difference was >> seen. >> >> Regards, >> Aparna. >> >> >> On Tue, Sep 10, 2013 at 3:43 PM, Isuru Perera wrote: >> >>> Thanks Shelan! >>> >>> >>> On Tue, Sep 10, 2013 at 3:27 PM, Shelan Perera wrote: >>> >>>> Hi, >>>> >>>> Please find the packs built on revision 184928 (Until we get the packs >>>> from builder machine). >>>> This was built on a clean repo. >>>> >>>> http://10.100.1.185/packs/sep-10/ >>>> >>>> Thanks >>>> >>>> -- >>>> *Shelan Perera* >>>> >>>> Senior Software Engineer >>>> ** >>>> Integration Technology Group >>>> *WSO2, Inc. : wso2.com* >>>> lean.enterprise.middleware. >>>> >>>> *Blog* : blog.shelan.org >>>> *Linked-i*n : >>>> http://www.linkedin.com/pub/shelan-perera/a/194/465 >>>> *Twitter* :https://twitter.com/#!/shelan >>>> >>>> *Mobile* : +94 772 604 402 >>>> >>>> >>> >>> >>> -- >>> Isuru Perera >>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >>> Lean . Enterprise . Middleware >>> >>> about.me/chrishantha >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Regards, >> Aparna Karunarathna.* >> *Senior Software Engineer - QA >> WSO2 Inc. >> Mobile: 0714002533*** >> *Tel : 94 11 214 5345* >> *Fax : 94 11 2145300* >> > > > > -- > *Regards, > Aparna Karunarathna.* > *Senior Software Engineer - QA > WSO2 Inc. > Mobile: 0714002533*** > *Tel : 94 11 214 5345* > *Fax : 94 11 2145300* > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Packs built on Sep 10
We are continuing our Greg testing with RC8 ELB pack. On Wed, Sep 11, 2013 at 7:17 PM, Aparna Karunarathna wrote: > > Still we are getting timeout issue frequently and not able to connect with > Greg console from 1 user. Seems like spinning issue is fixed in the ELB. We > have set *http. connection. timeout=12* in the > passthru-http.properties file as suggested by Nirmal, but no difference was > seen. > > Regards, > Aparna. > > > On Tue, Sep 10, 2013 at 3:43 PM, Isuru Perera wrote: > >> Thanks Shelan! >> >> >> On Tue, Sep 10, 2013 at 3:27 PM, Shelan Perera wrote: >> >>> Hi, >>> >>> Please find the packs built on revision 184928 (Until we get the packs >>> from builder machine). >>> This was built on a clean repo. >>> >>> http://10.100.1.185/packs/sep-10/ >>> >>> Thanks >>> >>> -- >>> *Shelan Perera* >>> >>> Senior Software Engineer >>> ** >>> Integration Technology Group >>> *WSO2, Inc. : wso2.com* >>> lean.enterprise.middleware. >>> >>> *Blog* : blog.shelan.org >>> *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 >>> *Twitter* :https://twitter.com/#!/shelan >>> >>> *Mobile* : +94 772 604 402 >>> >>> >> >> >> -- >> Isuru Perera >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Regards, > Aparna Karunarathna.* > *Senior Software Engineer - QA > WSO2 Inc. > Mobile: 0714002533*** > *Tel : 94 11 214 5345* > *Fax : 94 11 2145300* > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Packs built on Sep 10
Still we are getting timeout issue frequently and not able to connect with Greg console from 1 user. Seems like spinning issue is fixed in the ELB. We have set *http. connection. timeout=12* in the passthru-http.properties file as suggested by Nirmal, but no difference was seen. Regards, Aparna. On Tue, Sep 10, 2013 at 3:43 PM, Isuru Perera wrote: > Thanks Shelan! > > > On Tue, Sep 10, 2013 at 3:27 PM, Shelan Perera wrote: > >> Hi, >> >> Please find the packs built on revision 184928 (Until we get the packs >> from builder machine). >> This was built on a clean repo. >> >> http://10.100.1.185/packs/sep-10/ >> >> Thanks >> >> -- >> *Shelan Perera* >> >> Senior Software Engineer >> ** >> Integration Technology Group >> *WSO2, Inc. : wso2.com* >> lean.enterprise.middleware. >> >> *Blog* : blog.shelan.org >> *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 >> *Twitter* :https://twitter.com/#!/shelan >> >> *Mobile* : +94 772 604 402 >> >> > > > -- > Isuru Perera > Senior Software Engineer | WSO2, Inc. | http://wso2.com/ > Lean . Enterprise . Middleware > > about.me/chrishantha > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ConcurrentModificationException in CarbonDeploymentSchedulerTask
Still we are getting this error.
TID: [0] [Greg] [2013-09-10 10:24:50,088] ERROR
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} - Error
while running deployment scheduler..
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask}
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
at java.util.HashMap$EntryIterator.next(HashMap.java:934)
at java.util.HashMap$EntryIterator.next(HashMap.java:932)
at
org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
at
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
at
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:65)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:110)
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:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Regards,
Aparna.
On Fri, Sep 28, 2012 at 12:46 PM, Rajika Kumarasiri wrote:
>
> [2012-09-28 12:41:27,297] ERROR - CarbonDeploymentSchedulerTask Error
> while running deployment synchronizer
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
> at java.util.HashMap$EntryIterator.next(HashMap.java:834)
> at java.util.HashMap$EntryIterator.next(HashMap.java:832)
> at
> org.apache.axis2.deployment.RepositoryListener.loadOtherDirectories(RepositoryListener.java:270)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:253)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:63)
> at
> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:100)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
*Regards,
Aparna Karunarathna.*
*Senior Software Engineer - QA
WSO2 Inc.
Mobile: 0714002533***
*Tel : 94 11 214 5345*
*Fax : 94 11 2145300*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Additional features in the Greg 4.6.0
Hi Ajith, Shall we remove Senaka mentioned features (UI level) from Greg Mgt UI ? Regards, Aparna. On Tue, Sep 10, 2013 at 9:41 AM, Aparna Karunarathna wrote: > Thanks Senaka. > > Regards, > Aparna > > > On Mon, Sep 9, 2013 at 10:32 PM, Senaka Fernando wrote: > >> Hi Aparna, >> >> Apart from the Asset Store (will figure what to do with that tomorrow) >> the rest is not required by G-Reg. These are side effects of having OAuth >> capabilities, and its better if we can get rid of these. >> >> Thanks, >> Senaka. >> >> >> On Mon, Sep 9, 2013 at 5:51 PM, Aparna Karunarathna wrote: >> >>> Hi, >>> >>> Please confirm whether we need to have following features in the Greg >>> 4.6.0? >>> >>> - asset-store - jaggery webapp >>> - My Authorized Applications under - Home> My Identity> My Authorized >>> Apps >>> - OAuth Management under - Home> Manage> OAuth >>> >>> -- >>> *Regards, >>> Aparna Karunarathna.* >>> *Senior Software Engineer - QA >>> WSO2 Inc. >>> Mobile: 0714002533*** >>> *Tel : 94 11 214 5345* >>> *Fax : 94 11 2145300* >>> >> >> >> >> -- >> * <http://us13.wso2con.com/> >> * >> * >> * >> *Senaka Fernando* >> Senior 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 >> > > > > -- > *Regards, > Aparna Karunarathna.* > *Senior Software Engineer - QA > WSO2 Inc. > Mobile: 0714002533*** > *Tel : 94 11 214 5345* > *Fax : 94 11 2145300* > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Additional features in the Greg 4.6.0
Thanks Senaka. Regards, Aparna On Mon, Sep 9, 2013 at 10:32 PM, Senaka Fernando wrote: > Hi Aparna, > > Apart from the Asset Store (will figure what to do with that tomorrow) the > rest is not required by G-Reg. These are side effects of having OAuth > capabilities, and its better if we can get rid of these. > > Thanks, > Senaka. > > > On Mon, Sep 9, 2013 at 5:51 PM, Aparna Karunarathna wrote: > >> Hi, >> >> Please confirm whether we need to have following features in the Greg >> 4.6.0? >> >> - asset-store - jaggery webapp >> - My Authorized Applications under - Home> My Identity> My Authorized Apps >> - OAuth Management under - Home> Manage> OAuth >> >> -- >> *Regards, >> Aparna Karunarathna.* >> *Senior Software Engineer - QA >> WSO2 Inc. >> Mobile: 0714002533*** >> *Tel : 94 11 214 5345* >> *Fax : 94 11 2145300* >> > > > > -- > * <http://us13.wso2con.com/> > * > * > * > *Senaka Fernando* > Senior 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 > -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Additional features in the Greg 4.6.0
Hi, Please confirm whether we need to have following features in the Greg 4.6.0? - asset-store - jaggery webapp - My Authorized Applications under - Home> My Identity> My Authorized Apps - OAuth Management under - Home> Manage> OAuth -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: Are we releasing the Assets Store with Greg 4.6.0?
Forwarding to dev. -- Forwarded message -- From: Aparna Karunarathna Date: Mon, Sep 9, 2013 at 3:25 PM Subject: Are we releasing the Assets Store with Greg 4.6.0? To: Senaka Fernando , Nuwan Dias , support-dev-group Cc: Evanthika Amarasiri , Iranga Muthuthanthri < ira...@wso2.com> Hi, Are we releasing the Assets Store with Greg 4.6.0? Please clarify. -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* -- *Regards, Aparna Karunarathna.* *Senior Software Engineer - QA WSO2 Inc. Mobile: 0714002533*** *Tel : 94 11 214 5345* *Fax : 94 11 2145300* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Urgent] Manager Roles page is getting crashed
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:172)
at
org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927)
at
org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
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: java.lang.Exception: org.apache.axis2.databinding.ADBException:
Unexpected subelement {http://common.mgt.user.carbon.wso2.org/xsd}domainName
at
org.wso2.carbon.user.mgt.stub.types.carbon.FlaggedName$Factory.parse(FlaggedName.java:716)
at
org.wso2.carbon.user.mgt.stub.types.carbon.GetAllRolesNamesResponse$Factory.parse(GetAllRolesNamesResponse.java:489)
at
org.wso2.carbon.user.mgt.stub.UserAdminStub.fromOM(UserAdminStub.java:5611)
... 114 more
Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement
{http://common.mgt.user.carbon.wso2.org/xsd}domainName
at
org.wso2.carbon.user.mgt.stub.types.carbon.FlaggedName$Factory.parse(FlaggedName.java:710)
... 116 more
Please have a look.
--
*Regards,
Aparna Karunarathna.
WSO2 Inc.
Mobile:0714002533***
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fatal error was thrown when login as a tenant in Windows environment
extValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:179) at org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) at org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:49) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:579) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) [2012-09-18 19:25:22,586] INFO - PermissionUpdater Permission cache updated for tenant 1 -- *Regards, Aparna Karunarathna. WSO2 Inc. Mobile:0714002533*** ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] NPE is observed when server is idle
Hi,
Following NPE was throwing continuously when server is logged and idle for
30min or more. This was observed with the GReg pack(3rd Sept). JIRA [1] was
created for this issue.
[2012-09-03 19:37:40,035] ERROR
{org.wso2.carbon.core.multitenancy.MultitenantServerManager} - Error
occurred while executing tenant cleanup
java.lang.NullPointerException
at
org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:395)
at
org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
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)
[1] https://wso2.org/jira/browse/CARBON-13857
Environment:
Server: wso2greg-4.5.0
OS: Win 7
Java: 1.7.3
--
*Regards,
Aparna Karunarathna.
WSO2 Inc.
Mobile:0714002533***
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Greg testing cycle 2 - Cyrillic character testing
Hi, In Greg testing cycle 2, we have tested the Greg build with the Russian locale(windows-1251) on windows platform. When create a matadata using early Cyrillic characters, it displayed as "? ? ? ?" and it works fine for modern characters. *The early Cyrillic alphabet* А Б В Г Д Е Ж Ѕ Z З И І К Л М Н О П Р С Т Ȣ Ѹ Ф Х Ѿ Ц Ч Ш Щ Ъ Ꙑ Ь Ѣ Ꙗ Ѥ Ю Ѧ Ѫ Ѩ Ѭ Ѡ Ѻ Ѯ Ѱ Ѳ Ѵ Source: http://en.wikipedia.org/wiki/Cyrillic_script *The modern Cyrillic alphabet(*The Russian alphabet is known as the Cyrillic alphabet) А, Б, В, Г, Д, Е, Ё, Ж, З, И, Й, К, Л, М, Н, О, П, Р, С, Т, У, Ф, Х, Ц, Ч, Ш, Щ, Ъ, Ы, Ь, Э, Ю, Я Source: http://www.russianlessons.net/lessons/lesson1_main.php Currently we are testing with modern characters (windows-1251). Do we have to test the early Cyrillic characters as well? -- Regards, Aparna Karunarathna. WSO2 Inc. Mobile:0714002533 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] C4 G-reg pack for functional testing
Hi Dimuthu,
As per an offline discussion with Senaka most of the new features are
available on this build. Therefore we are continuing testing on this
build.
Regards,
Aparna
On Fri, May 25, 2012 at 11:20 AM, Dimuthu Leelarathne wrote:
> Hi Aparna,
>
> We - the AppFactory team also experienced that. According to Supun this is
> fixed in revision r128159.
>
> So you can use a pack built before 24th May or wait for the next build
> coming after a platform build.
>
> thanks,
> dimuthu
>
>
> On Fri, May 25, 2012 at 11:13 AM, Aparna Karunarathna
> wrote:
>>
>> Hi,
>>
>> Following exception was thrown continuously when start the GReg and we
>> are able to login to the management console. Currently we are doing a
>> smoke test and will report the other issues.
>>
>>
>> org.wso2.carbon.registry.core.exceptions.RegistryException: The path
>>
>> '/_system/local/repository/components/org.wso2.carbon.system.statistics/services/WorkListService/{http://wso2.org/worklist/}addTask'
>> contains one or more illegal characters (~!@#;%^*()+={}|\<>"',)
>> at
>> org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:287)
>> at
>> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
>> at
>> org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:415)
>> at
>> org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:649)
>> at
>> org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.persistOperationStatistics(StatisticsPersistenceScheduler.java:208)
>> at
>> org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.invoke(StatisticsPersistenceScheduler.java:37)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.invokeCarbonDeploymentSchedulerExtenders(CarbonDeploymentSchedulerTask.java:101)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:71)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>>
>> Regards,
>> Aparna
>>
>> On Fri, May 25, 2012 at 10:54 AM, Evanthika Amarasiri
>> wrote:
>> > Noticed the following minor issue while extracting the G-Reg pack.
>> >
>> > inflating:
>> >
>> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/handler-def/handlers.xml
>> > inflating:
>> >
>> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/registry-extensions/application.rxt
>> > replace
>> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml?
>> > [y]es, [n]o, [A]ll, [N]one, [r]ename: y
>> > inflating:
>> > wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml
>> >
>> > Regards,
>> > Evanthika
>> >
>> >
>> > On Fri, May 25, 2012 at 9:45 AM, Dimuthu Leelarathne
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> Please find the Greg pack at
>> >>
>> >>
>> >> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-141/artifact/JOB1/GREG
>> >>
>> >> thanks,
>> >> dimuthu
>> >>
>> >>
>> >> On Fri, May 25, 2012 at 9:33 AM, Charitha Kankanamge
>> >>
>> >> wrote:
>> >>>
>> >>> Hi Dimuthu,
>> >>> Please give us a G-reg pack, we will look into other packs only after
>> >>> completing a functional test round of G-Reg.
>> >>>
>> >>>
>> >>> On Friday, May 25, 2012, Dimu
Re: [Dev] C4 G-reg pack for functional testing
Hi,
Following exception was thrown continuously when start the GReg and we
are able to login to the management console. Currently we are doing a
smoke test and will report the other issues.
org.wso2.carbon.registry.core.exceptions.RegistryException: The path
'/_system/local/repository/components/org.wso2.carbon.system.statistics/services/WorkListService/{http://wso2.org/worklist/}addTask'
contains one or more illegal characters (~!@#;%^*()+={}|\<>"',)
at
org.wso2.carbon.registry.core.jdbc.Repository.put(Repository.java:287)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.put(EmbeddedRegistry.java:709)
at
org.wso2.carbon.registry.core.caching.CacheBackedRegistry.put(CacheBackedRegistry.java:415)
at
org.wso2.carbon.registry.core.session.UserRegistry.put(UserRegistry.java:649)
at
org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.persistOperationStatistics(StatisticsPersistenceScheduler.java:208)
at
org.wso2.carbon.statistics.persistance.StatisticsPersistenceScheduler.invoke(StatisticsPersistenceScheduler.java:37)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.invokeCarbonDeploymentSchedulerExtenders(CarbonDeploymentSchedulerTask.java:101)
at
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:71)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Regards,
Aparna
On Fri, May 25, 2012 at 10:54 AM, Evanthika Amarasiri
wrote:
> Noticed the following minor issue while extracting the G-Reg pack.
>
> inflating:
> wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/handler-def/handlers.xml
> inflating:
> wso2greg-4.0.0-SNAPSHOT/samples/asset-models/ApplicationModel/registry-extensions/application.rxt
> replace wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml?
> [y]es, [n]o, [A]ll, [N]one, [r]ename: y
> inflating:
> wso2greg-4.0.0-SNAPSHOT/samples/asset-models/Populator/build.xml
>
> Regards,
> Evanthika
>
>
> On Fri, May 25, 2012 at 9:45 AM, Dimuthu Leelarathne
> wrote:
>>
>> Hi,
>>
>> Please find the Greg pack at
>>
>> http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-141/artifact/JOB1/GREG
>>
>> thanks,
>> dimuthu
>>
>>
>> On Fri, May 25, 2012 at 9:33 AM, Charitha Kankanamge
>> wrote:
>>>
>>> Hi Dimuthu,
>>> Please give us a G-reg pack, we will look into other packs only after
>>> completing a functional test round of G-Reg.
>>>
>>>
>>> On Friday, May 25, 2012, Dimuthu Leelarathne wrote:
>>>>
>>>> Hi Charitha,
>>>>
>>>> Next packs are going to be merged. Greg merging is done. We can give you
>>>> a pack from Bamboo only for Greg if it is blocking.
>>>>
>>>> Others are not ready yet.
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>> On Thu, May 24, 2012 at 5:44 PM, Charitha Kankanamge
>>>> wrote:
>>>>>
>>>>> Hi Senaka/Dimuthu,
>>>>> Will it be possible for us to get a C4 based testable G-reg pack for
>>>>> testing by tomorrow? We are supposed to start executing the test scenarios
>>>>> which we drafted in G-reg QA plan [1]
>>>>>
>>>>>
>>>>> [1]https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AvhVRxNoCg0KdHRVMm1pM2xLUDREajdHRVlQekJRcUE&pli=1#gid=0
>>>>>
>>>>> Thanks!
>>>>> Charitha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Dimuthu Leelarathne
>>>> Technical Lead
>>>>
>>>> WSO2, Inc. (http://wso2.com)
>>>> email: dimut...@wso2.com
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>> --
>>> Charitha Kankanamge
>>> cell: +94 718 359 265
>>> blog: http://charithaka.blogspot.com
>>>
>>
>>
>>
>> --
>> 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
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
Regards,
Aparna Karunarathna.
WSO2 Inc.
Mobile:0714002533
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] smoke testing - alpha packs
hread in support-dev). >>>>>>> Because of that, we will carry out end- end system testing locally >>>>>>> with these packs. >>>>>>> >>>>>>> Thanks >>>>>>> Charitha >>>>>>> >>>>>>> >>>>>>> On Monday, April 2, 2012, Pradeep Fernando wrote: >>>>>>> >>>>>>>> Hi Charitha/QA team, >>>>>>>> >>>>>>>> Looks like we have a testable set of product packs. please get the >>>>>>>> packs from this location [1]. >>>>>>>> >>>>>>>> we expect you/team to test Carbon-kernel functionalities. Please >>>>>>>> use, >>>>>>>> >>>>>>>> IS, >>>>>>>> GREG, >>>>>>>> AS, >>>>>>>> ESB, >>>>>>>> Manager >>>>>>>> >>>>>>>> + any other required product >>>>>>>> >>>>>>>> as testing materials. >>>>>>>> >>>>>>>> [1] http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-24/artifact >>>>>>>> >>>>>>>> thanks, >>>>>>>> --Pradeep >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Charitha Kankanamge >>>>>>> cell: +94 718 359 265 >>>>>>> blog: http://charithaka.blogspot.com <http://wso2.com> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Nirodha Gallage* >>>>> Software Engineer, QA. >>>>> WSO2 Inc.: http://wso2.com/ >>>>> Email: niro...@wso2.com Mobile: +94716429078 >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Chamara Ariyarathne* >>>> Software Engineer - QA; >>>> WSO2 Inc; http://www.wso2.com/. >>>> Mobile; *0772786766* >>>> >>>> >>> >>> >>> -- >>> *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 >>> >>> >> >> >> -- >> Prabath Abeysekara >> Software Engineer >> WSO2 Inc. >> Email: praba...@wso2.com >> Mobile: +94774171471 >> >> <http://harshana05.blogspot.com/> >> >> > > > -- > *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 > > -- *Regards, Aparna Karunarathna. WSO2 Inc. Mobile:0714002533*** ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
