Re: [Dev] WSO2 Committers += Pandula Kariyawasam

[Nirodha Pramod]

Congratulations Pandula!

On Mon, Oct 5, 2015 at 2:12 PM, Yasassri Ratnayake 
wrote:

> Congrats Pandula :)
>
> On Mon, Oct 5, 2015 at 11:57 AM, Malintha Adikari 
> wrote:
>
>> Congratz Pandula
>>
>>
>> On Mon, Oct 5, 2015 at 11:54 AM, Chanaka Fernando 
>> wrote:
>>
>>> Congratulations Pandula !!!
>>>
>>> On Mon, Oct 5, 2015 at 11:13 AM, Pavithra Madurangi 
>>> wrote:
>>>
 Hi All,

 It's my pleasure to announce Pandula Kariyawasam as a WSO2 Committer.
 Pandula is an active member of QA team and has given a great contribution
 to Application Server, API Manager, G-Reg, ESB, EMM, BAM, App Factory and
 IS product releases. So in recognition of his contribution, dedication and
 ownership shown towards the tasks given to him, he has been voted as a WSO2
 Committer.

 Pandula, congratulations and keep up the good work...!

 Regards,
 Pavithra
 --
 *Pavithra Madurangi*
 Associate Technical Lead - QA.
 WSO2 Inc.: http://wso2.com/
 Mobile: 0777207357 / 0112747089

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


>>>
>>>
>>> --
>>> --
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Malintha Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> Mobile: +94 71 2312958
>> Blog:http://malinthas.blogspot.com
>> Page:   http://about.me/malintha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Yasassri Ratnayake
> Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <%2B94715933168>*
> *Blogs : http://yasassriratnayake.blogspot.com
> *
> *http://wso2logs.blogspot.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

[Dev] ML Predict Mediator feature for ESB is broken

[Nirodha Pramod]

Hi Nirmal,

We have tried to test the Predict Mediator feature with ESB 4.9.0 alpha
packs and got the below two blocking issues[1] [2]. Please have a look. We
followed the doc [3]

[1] https://wso2.org/jira/browse/ML-193

[2] https://wso2.org/jira/browse/ML-188

[3] https://docs.wso2.com/display/ML100/Predict+Mediator+for+ESB


Regards,
Nirodha

-- 

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

Re: [Dev] mongoDB integration with wso2ml

[Nirodha Pramod]

Hi Zajith,

WSO2 ML 1.0.0 does not support Mongo DB database as of now. We currently
support H2 and MySQL only.

Regards,
Nirodha

On Thu, Jul 30, 2015 at 4:04 PM, Mohamed ZAJITH 
wrote:

> my system configuration
> OS ubuntu 14.04
> JAVA 1.7.65
> MongoDB 2.6.10
> wso2ml
> https://docs.wso2.com/display/ML100/Installation+Prerequisites
>
> I want to integrate mongodb in wso2ml help me
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] [ML] Do we need Carbon Application adding feature?

[Nirodha Pramod]

Done.

Thanks.


[1] https://wso2.org/jira/browse/ML-148

On Fri, Jul 17, 2015 at 10:46 AM, Nirmal Fernando  wrote:

> Thanks Nirodha. We'll check on how to remove it. Please create a Jira.
>
> On Fri, Jul 17, 2015 at 9:59 AM, Nirodha Pramod  wrote:
>
>> Hi All,
>>
>> Do we need CApp adding feature in ML? Since we don't have any CApp
>> deploying model for ML I think it is better to remove it.
>>
>> Thanks,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Associate Technical Lead, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 

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

[Dev] [ML] Do we need Carbon Application adding feature?

[Nirodha Pramod]

Hi All,

Do we need CApp adding feature in ML? Since we don't have any CApp
deploying model for ML I think it is better to remove it.

Thanks,
Nirodha

-- 

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

[Dev] [ML] Cannot add new users

[Nirodha Pramod]

Hi,

There we get a JSP exception when adding new users from carbon console, in
ML beta1 pack. Please have a look.

[1] https://wso2.org/jira/browse/ML-130


Regards,
Nirodha

-- 

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

[Dev] [ML] Removing tenant creation wizard

[Nirodha Pramod]

Hi Nirmal,

Since AFAIK we are not supporting multi-tenancy in ML, I think we should
remove the tanant wizards in carbon console. Any concerns to keep it?

- Nirodha
-- 

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

Re: [Dev] The table 'UM_USER_ROLE' is full

[Nirodha Pramod]

Thanks for the information Tharindu, but this issue occurs when you just
run the registry database script separately on the database for the first
time. It does not involve server startup.

I have tried some solutions mentioned in the links provided by Uvindra they
don't seems to work though.

On Sat, Jul 4, 2015 at 12:59 AM, Tharindu Edirisinghe 
wrote:

> Hi Nirodha,
>
> Before starting the server and after starting the server, if you query the
> UM_ROLE_PERMISSION table, you should be able to see that some of the
> records are getting inserted again as new records without getting deleted
> the previous records. This can be the reason for the issue where with time,
> when you restart the server the UM_ROLE_PERMISSION table can grow and
> exceed some allocated space. However this issue is fixed such that at
> server startup it does not insert new records if already existing. You can
> find the JIRA for that in [1]. If you get the latest
> org.wso2.carbon.user.core-4.2.0 and apply as a patch, you should be able to
> avoid growing of the table upon startup of the server. I hope this helps.
> If you need more information, I can help.
>
> [1] https://wso2.org/jira/browse/CARBON-15265
>
> Thanks,
> TharinduE
>
> On Fri, Jul 3, 2015 at 12:50 PM, Uvindra Dias Jayasinha 
> wrote:
>
>> Doesn't look like an issue with the script itself, this could happen
>> because you have run out of disk space on the DB cluster or the table has
>> reached its max allocated size, see following links,
>>
>>
>> http://stackoverflow.com/questions/730579/error-1114-hy000-the-table-is-full
>>
>> http://stackoverflow.com/questions/21850287/error-1114-hy000-the-table-xxx-is-full
>>
>> http://stackoverflow.com/questions/19639343/error-while-executing-sql-file-error-1114-mysql-table-is-full
>>
>> On 3 July 2015 at 12:06, Nirodha Pramod  wrote:
>>
>>> Hi,
>>>
>>> The script was taken from the AM 1.9.0 registry database script.
>>>
>>> -Nirodha
>>>
>>> On Fri, Jul 3, 2015 at 12:05 PM, Nirodha Pramod 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I get the below set of errors when running the registry database script
>>>> on a mysql NDB cluster. Could this be a script issue or Mysql config issue?
>>>>
>>>> Any thought on this would be appreciated.
>>>>
>>>>
>>>>
>>>>
>>>> Query OK, 0 rows affected (0.24 sec)
>>>>
>>>> Query OK, 0 rows affected (0.20 sec)
>>>>
>>>> ERROR 1114 (HY000): The table 'UM_ROLE_PERMISSION' is full
>>>> Query OK, 0 rows affected (0.21 sec)
>>>>
>>>> ERROR 1114 (HY000): The table 'UM_USER_ROLE' is full
>>>> ERROR 1114 (HY000): The table 'UM_SHARED_USER_ROLE' is full
>>>> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
>>>> (increase MaxNoOfAttributes)' from NDBCLUSTER
>>>> ERROR 1114 (HY000): The table 'UM_USER_ATTRIBUTE' is full
>>>> ERROR 1114 (HY000): The table 'UM_DIALECT' is full
>>>> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
>>>> (increase MaxNoOfAttributes)' from NDBCLUSTER
>>>> ERROR 1114 (HY000): The table 'UM_PROFILE_CONFIG' is full
>>>> ERROR 1114 (HY000): The table 'UM_HYBRID_ROLE' is full
>>>> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
>>>> (increase MaxNoOfAttributes)' from NDBCLUSTER
>>>> ERROR 1114 (HY000): The table 'UM_SYSTEM_ROLE' is full
>>>> ERROR 1114 (HY000): The table 'UM_SYSTEM_USER_ROLE' is full
>>>> ERROR 1114 (HY000): The table 'UM_HYBRID_REMEMBER_ME' is full
>>>> ERROR 1114 (HY000): The table 'UM_CUSTOM_USERSTORE' is full
>>>>
>>>> ​Thanks,
>>>> Nirodha​
>>>>
>>>> --
>>>>
>>>> *Nirodha Gallage*
>>>> Associate Technical Lead, QA.
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94716429078
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Nirodha Gallage*
>>> Associate Technical Lead, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Uvindra
>>
>> Mobile: 33962
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Tharindu Edirisinghe
> Software Engineer | WSO2 Inc
> Identity Server Team
> Blog : tharindue.blogspot.com
> mobile : +94 775 181586
>
>
>


-- 

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

Re: [Dev] The table 'UM_USER_ROLE' is full

[Nirodha Pramod]

Hi,

The script was taken from the AM 1.9.0 registry database script.

-Nirodha

On Fri, Jul 3, 2015 at 12:05 PM, Nirodha Pramod  wrote:

> Hi,
>
> I get the below set of errors when running the registry database script on
> a mysql NDB cluster. Could this be a script issue or Mysql config issue?
>
> Any thought on this would be appreciated.
>
>
>
>
> Query OK, 0 rows affected (0.24 sec)
>
> Query OK, 0 rows affected (0.20 sec)
>
> ERROR 1114 (HY000): The table 'UM_ROLE_PERMISSION' is full
> Query OK, 0 rows affected (0.21 sec)
>
> ERROR 1114 (HY000): The table 'UM_USER_ROLE' is full
> ERROR 1114 (HY000): The table 'UM_SHARED_USER_ROLE' is full
> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
> (increase MaxNoOfAttributes)' from NDBCLUSTER
> ERROR 1114 (HY000): The table 'UM_USER_ATTRIBUTE' is full
> ERROR 1114 (HY000): The table 'UM_DIALECT' is full
> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
> (increase MaxNoOfAttributes)' from NDBCLUSTER
> ERROR 1114 (HY000): The table 'UM_PROFILE_CONFIG' is full
> ERROR 1114 (HY000): The table 'UM_HYBRID_ROLE' is full
> ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
> (increase MaxNoOfAttributes)' from NDBCLUSTER
> ERROR 1114 (HY000): The table 'UM_SYSTEM_ROLE' is full
> ERROR 1114 (HY000): The table 'UM_SYSTEM_USER_ROLE' is full
> ERROR 1114 (HY000): The table 'UM_HYBRID_REMEMBER_ME' is full
> ERROR 1114 (HY000): The table 'UM_CUSTOM_USERSTORE' is full
>
> ​Thanks,
> Nirodha​
>
> --
>
> *Nirodha Gallage*
> Associate Technical Lead, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>



-- 

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

[Dev] The table 'UM_USER_ROLE' is full

[Nirodha Pramod]

Hi,

I get the below set of errors when running the registry database script on
a mysql NDB cluster. Could this be a script issue or Mysql config issue?

Any thought on this would be appreciated.




Query OK, 0 rows affected (0.24 sec)

Query OK, 0 rows affected (0.20 sec)

ERROR 1114 (HY000): The table 'UM_ROLE_PERMISSION' is full
Query OK, 0 rows affected (0.21 sec)

ERROR 1114 (HY000): The table 'UM_USER_ROLE' is full
ERROR 1114 (HY000): The table 'UM_SHARED_USER_ROLE' is full
ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
(increase MaxNoOfAttributes)' from NDBCLUSTER
ERROR 1114 (HY000): The table 'UM_USER_ATTRIBUTE' is full
ERROR 1114 (HY000): The table 'UM_DIALECT' is full
ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
(increase MaxNoOfAttributes)' from NDBCLUSTER
ERROR 1114 (HY000): The table 'UM_PROFILE_CONFIG' is full
ERROR 1114 (HY000): The table 'UM_HYBRID_ROLE' is full
ERROR 1296 (HY000): Got error 708 'No more attribute metadata records
(increase MaxNoOfAttributes)' from NDBCLUSTER
ERROR 1114 (HY000): The table 'UM_SYSTEM_ROLE' is full
ERROR 1114 (HY000): The table 'UM_SYSTEM_USER_ROLE' is full
ERROR 1114 (HY000): The table 'UM_HYBRID_REMEMBER_ME' is full
ERROR 1114 (HY000): The table 'UM_CUSTOM_USERSTORE' is full

​Thanks,
Nirodha​

-- 

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

Re: [Dev] APIM-1.9.0 latest build pack - 09-05-2015

[Nirodha Pramod]

Hi Lakmali,

When can we have the migration scripts for 1.8.0 to 1.9.0. Those are not
included in the pack.

Thanks,
Nirodha

On Sun, May 10, 2015 at 8:59 AM, Lakmali Baminiwatta 
wrote:

> Hi,
>
> Please find $subject from [1].
>
> [1]http://builder1.us1.wso2.org/~apim/09-05-2015/wso2am-1.9.0-SNAPSHOT.zip
>
> Thanks,
> Lakmali
>
> --
> Lakmali Baminiwatta
>  Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] App-Manager 1.0 Release Testing Update

[Nirodha Pramod]

Also we have started testing earlier enough I guess. Pavithra started
testing the previous packs in last August/Spetember. And this round of
testing started in January. The problem was some features were not ready
and features changed through out last couple of months, which invalidates
the tests we did and have to do it again.

On Tue, Apr 7, 2015 at 1:49 PM, Nirodha Pramod  wrote:

> Hi,
>
> Our concerns were that we had the above mentioned L1s and L2s and added
> new features in the latest packs, which makes it not ready to be released
> in two more days. And we have been getting packs like every other day(some
> with config changes too) so it is a bit hard to manage testing on all the
> given packs. So to do a decent release we would need more time to test.
> Since we were running low on headcount we could not allocate more than one
> in past few weeks. However we have allocated another person to help with
> AppM testing.
>
> Thanks,
> Nirodha
>
> On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe 
> wrote:
>
>> Shakar,
>> All these are available on packs.
>>
>> Problems
>> - we now have 8 L1s, 26 L2s
>> - QA was running low on resources, so only one engineer was available for
>> last 2+ weeks
>> - So QA wants to test more
>>
>>
>> On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar <
>> shan...@wso2.com> wrote:
>>
>>> Hi Sumedha,
>>>
>>> Yes, thats all fine. I am asking when we will get the pack with all
>>> these features/ changes done. Meaning the proper alpha with features
>>> frozen. If we still don't know that date, it is also fine, but we can plan
>>> the QA based on that.
>>>
>>> On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe 
>>> wrote:
>>>
>>>> On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar <
>>>> shan...@wso2.com> wrote:
>>>>
>>>>> Hi Sumedha, Dinusha,
>>>>>
>>>>> When do we have the alpha release with feature frozen?
>>>>>
>>>>
>>>> Hi Shankar,
>>>> We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/
>>>> lists out all public packs we have hosted).
>>>>
>>>> Then Isabelle & Chris used this alpha pack to do a series of partner
>>>> briefings.
>>>>
>>>> After these briefings we got feedback to improve following areas:
>>>> 1. App Publishing flow is too lengthy for a newbie
>>>> 2. App Policy Mgt should be separated out from App Publishing (thread:
>>>> [APPM] [IS] Change of XACML based authorization)
>>>> 3. Make graphs more aesthetic
>>>> 4. Improve first timers experience better by adding a sample app
>>>> deployer (thread: dev: App Manager sample deployer)
>>>>
>>>> We also discovered following:
>>>> - We only support EMM 1.0. So need to add support for both EMM 1.0.0 &
>>>> MDM 2.0.0  ("thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App
>>>> Management feature to App Manager)
>>>>
>>>> - ES only supports permission check for login only. So we had to
>>>> implement permission model on top of ES (thread : Life Cycles
>>>> transition for Apps in APPM)
>>>>
>>>> Apart from this RuwanA finished his project on App Discovery (thread:
>>>> [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS)
>>>>
>>>>
>>>> So after the alpha on 23rd of December, above are the changes we
>>>> introduced apart from fixing issues reported.
>>>>
>>>>
>>>>
>>>>
>>>>> On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake >>>> > wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> This is to update the Latest progress on App Manager Release testing.
>>>>>> Currently there are following blockers and critical issues. IMHO these 
>>>>>> need
>>>>>> to be fixed before the release.
>>>>>>
>>>>>>- Oracle DB script related issues.
>>>>>>- BAM toolbox issues/ Stats related issues
>>>>>>- Single Logout
>>>>>>- BPS integration issues. (Was Fixed with the latest pack (5th
>>>>>>April Pack), yet to verify the fix)
>>>>>>- Session Related issues. etc.
>>>>>>
>>>>>> Some of these issues are list

Re: [Dev] App-Manager 1.0 Release Testing Update

[Nirodha Pramod]

Hi,

Our concerns were that we had the above mentioned L1s and L2s and added new
features in the latest packs, which makes it not ready to be released in
two more days. And we have been getting packs like every other day(some
with config changes too) so it is a bit hard to manage testing on all the
given packs. So to do a decent release we would need more time to test.
Since we were running low on headcount we could not allocate more than one
in past few weeks. However we have allocated another person to help with
AppM testing.

Thanks,
Nirodha

On Tue, Apr 7, 2015 at 1:35 PM, Sumedha Rubasinghe  wrote:

> Shakar,
> All these are available on packs.
>
> Problems
> - we now have 8 L1s, 26 L2s
> - QA was running low on resources, so only one engineer was available for
> last 2+ weeks
> - So QA wants to test more
>
>
> On Tue, Apr 7, 2015 at 1:18 PM, Selvaratnam Uthaiyashankar <
> shan...@wso2.com> wrote:
>
>> Hi Sumedha,
>>
>> Yes, thats all fine. I am asking when we will get the pack with all these
>> features/ changes done. Meaning the proper alpha with features frozen. If
>> we still don't know that date, it is also fine, but we can plan the QA
>> based on that.
>>
>> On Tue, Apr 7, 2015 at 12:28 PM, Sumedha Rubasinghe 
>> wrote:
>>
>>> On Tue, Apr 7, 2015 at 11:13 AM, Selvaratnam Uthaiyashankar <
>>> shan...@wso2.com> wrote:
>>>
 Hi Sumedha, Dinusha,

 When do we have the alpha release with feature frozen?

>>>
>>> Hi Shankar,
>>> We did alpha on 23rd Dec 2014. (http://builder1.us1.wso2.org/~appm/
>>> lists out all public packs we have hosted).
>>>
>>> Then Isabelle & Chris used this alpha pack to do a series of partner
>>> briefings.
>>>
>>> After these briefings we got feedback to improve following areas:
>>> 1. App Publishing flow is too lengthy for a newbie
>>> 2. App Policy Mgt should be separated out from App Publishing (thread:
>>> [APPM] [IS] Change of XACML based authorization)
>>> 3. Make graphs more aesthetic
>>> 4. Improve first timers experience better by adding a sample app
>>> deployer (thread: dev: App Manager sample deployer)
>>>
>>> We also discovered following:
>>> - We only support EMM 1.0. So need to add support for both EMM 1.0.0 &
>>> MDM 2.0.0  ("thread: [Architecture] [CDM] [AppM] Moving CDM (EMM) App
>>> Management feature to App Manager)
>>>
>>> - ES only supports permission check for login only. So we had to
>>> implement permission model on top of ES (thread : Life Cycles
>>> transition for Apps in APPM)
>>>
>>> Apart from this RuwanA finished his project on App Discovery (thread:
>>> [Architecture] [AppM][AppFactory][AS] AppM Discovery of WebApps from AS)
>>>
>>>
>>> So after the alpha on 23rd of December, above are the changes we
>>> introduced apart from fixing issues reported.
>>>
>>>
>>>
>>>
 On Tue, Apr 7, 2015 at 10:35 AM, Yasassri Ratnayake 
 wrote:

> Hi All,
>
> This is to update the Latest progress on App Manager Release testing.
> Currently there are following blockers and critical issues. IMHO these 
> need
> to be fixed before the release.
>
>- Oracle DB script related issues.
>- BAM toolbox issues/ Stats related issues
>- Single Logout
>- BPS integration issues. (Was Fixed with the latest pack (5th
>April Pack), yet to verify the fix)
>- Session Related issues. etc.
>
> Some of these issues are listed from [1] - [9]. In total(Open,
> Reopened, In Progress issues) there are 38 L1 and L2 isuues, 95 L3 issues
> and 15 L4 & L5 issues.
>
> Along the way we faced several challenges when testing APP-M apart
> from the blocking issues we faced, following new features were added
>
>- App Discovery
>- New Stats pages
>- Sample Deploying feature
>
> Some features also got changed
>
>- EMM integration
>- XACML policy UI etc.
>
> There were some configuration level changes in web-apps as well as in
> app-manager.xml/ user-mgt.xml which affected the Automation process. Lack
> of documentation was another issue we faced.
>
> Currently we are in the process of testing untested areas and bug
> fixed scenarios. Due to above mentioned issues IMHO I highly doubt whether
> we can do a proper round of testing before the planned release date.
>
> [1] - https://wso2.org/jira/browse/APPM-718
> [2] - https://wso2.org/jira/browse/APPM-715
> [3] - https://wso2.org/jira/browse/APPM-686
> [4] - https://wso2.org/jira/browse/APPM-651
> [5] - https://wso2.org/jira/browse/APPM-481
> [6] - https://wso2.org/jira/browse/APPM-324
> [7] - https://wso2.org/jira/browse/APPM-511
> [8] - https://wso2.org/jira/browse/APPM-544
> [9] - https://wso2.org/jira/browse/APPM-639
>
> With Regards,
>
>
> On Thu, Mar 19, 2015 at 2:18 PM, Dinusha Senanayaka 
> wrote:
>
>> Hi Yasassri,
>>
>> Please find the latest pack in 

Re: [Dev] App-Manager 1.0 Release Testing Update

[Nirodha Pramod]

Hi Yasassri,

The tentative scheduled released date is 25th March, can we cover the rest
of the scenarios (not tested) mentioned above by that time?

-Nirodha

On Tue, Mar 17, 2015 at 2:50 PM, Yasassri Ratnayake 
wrote:

> Hi All,
>
> This is to update the current status of the App Manger release cycle.
>
> We had issues initially when testing due to following reasons
>
>- There was no decided permission model embedded to AM.
>- UI got changed along the way
>- Features were not finalized.
>
> We got the following critical fixes with the 06-03-2015 pack.
>
> => Finalized permission model
> => Fix for blockers under tenant scenarios.
>
> Got the following fixes with the 16-03-2015 pack.
>
> => Oracle Script fix
> => Fixed Mobile App scenarios for tenant
>
> *What has being done*
>
> 1. Setting-up cluster setup. (Deployment is Automated)
> 2. Jmeter scripts to mimic basic functionality of AM (Currently not
> working due to recent changes in AM)
> 3. Covered webapp creation/ Mobile app creation flow.
> 4. Smoke test with EMM integration.
> 5. Tested clustered caching scenarios.
> 6. Tested throttling.
> 7. Smoke tests on windows.
>
> *Current Status*
>
> ATM the latest pack is unstable so we are not testing the pack in the
> clustered setup, hence we are doing our tests in a standalone setup. And
> still the workflow process is not finalized.
>
> *Issue Status*
>
> From 6th March, 68 issues reported and a total of 220 issues reported by
> the QA team up-to now and from that there are 102 open issues.
>
> *What needs to be covered*
>
> With  the new Changes we have to cover the following areas.
>
> 1. Test with Oracle
> 2. Run a long running test.
> 3. Run Integration scenarios with BAM / EMM / IS (The cluster setup
> already has a IS cluster).
> 4. Smoke tests on already tested features/areas after bug fixes and
> improvements.
>
> With Regards,
> --
> Yasassri Ratnayake
> Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <%2B94715933168>*
> *Blog : http://yasassriratnayake.blogspot.com/
> *
>



-- 

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

Re: [Dev] How to start wso2sever with "wso2server.sh start" after ciphertoo is executed

[Nirodha Pramod]

Hi Nuwan,

You have to create a text file called "password-tmp" (no extenstion) and
set the keystore password in it, and save the file in the carbon_home
folder. When the server is started it reads the password from that file and
deletes the file. So if you are restarting again you will have to create
the file again.

-Nirodha

On Sun, Mar 1, 2015 at 8:04 AM, Nuwan Wimalasekara  wrote:

> Hi
> Once ciphertool is executed, server start  ask to provide the keystore
> password "Enter KeyStore and Private Key Password :" from command line. So
> if the server is start "./wso2server.sh start", the password can not be
> provided. Is there any command lime parameter to pass the password when
> server start up?
>
> Thanks,
> Nuwanw
>
> --
> Nuwan Wimalasekara
> Senior Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> phone: +94 71 668 4620
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

[Dev] [Secondary userstore] [UI] "Disabled" parameter is marked as mandatory with a checkbox to tick

[Nirodha Pramod]

Hi,

Please see the jira [1]. In the secondary userstore UI , the user is sort
of asked to mark the newly created userstore as disabled, by making it
mandatory with a checkbox. Usually in UI forms a single checkbox field is
not marked as mandatory which makes no sense. So this disabled parameter
should go as an optional.

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

Thanks,
Nirodha

-- 

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

[Dev] not working in carbon 4.3.0

[Nirodha Pramod]

Hi,

Please note the $subject which have reported with [1]

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


Thanks.
Nirodha

-- 

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

Re: [Dev] [SS] Enable Secure Vault with carbon4.3.0?

[Nirodha Pramod]

Hi Manoj,

I found a wrong XPath in cipher-tool.properties file. Please see [1]
reported.

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

-Nirodha

On Wed, Feb 11, 2015 at 10:53 AM, Chaminda Jayawardena 
wrote:

> Thank you Manoj & Kishanthan.
>
> On Wed, Feb 11, 2015 at 10:34 AM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> Please find the instructions on below document.
>>
>> ​
>>  How to use Cipher Tool in your product
>> 
>> ​
>>
>> Thanks,
>> Manoj
>>
>>
>> *Manoj Kumara*
>> Software Engineer
>> WSO2 Inc. http://wso2.com/
>> *lean.enterprise.middleware*
>> Mobile: +94713448188
>>
>> On Wed, Feb 11, 2015 at 10:28 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> There is a guide (currently being developed by Manoj) on how to use
>>> ciphertool as a separate tool (not as a p2 feature). You can refer that.
>>>
>>> On Mon, Feb 9, 2015 at 10:56 PM, Chaminda Jayawardena >> > wrote:
>>>
 Any help on this please.

 On Mon, Feb 9, 2015 at 12:25 PM, Chaminda Jayawardena <
 chami...@wso2.com> wrote:

> Hi All,
>
> I am working on *SS150 **[The future release of WSO2SS is based on
> carbon 4.3.0]* *release **testing* and trying to *enable secure
> vault.*
> *ciphertool.sh* is missing in the bin folder and realized that it was
> changed in *carbon4.3.0* as needed to add it as a feature (refer
> [2]).
> No relevant feature found in [2] since SS150 is not there yet.
>
>
> Please guide to get this done as per current conditions.
>
> [1]
> https://docs.wso2.com/display/Carbon430/Carbon+Secure+Vault+Implementation
> [2] http://product-dist.wso2.com/p2/carbon/releases/turing
>
> --
> Thanks & Regards
>
> *Chaminda Jayawardena*
> Senior Software Engineer - QA
> WSO2 Inc. - http://wso2.com
> +94-77-7725234
>



 --
 Thanks & Regards

 *Chaminda Jayawardena*
 Senior Software Engineer - QA
 WSO2 Inc. - http://wso2.com
 +94-77-7725234

>>>
>>>
>>>
>>> --
>>> *Kishanthan Thangarajah*
>>> Senior Software Engineer,
>>> Platform Technologies Team,
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - +94773426635
>>> Blog - *http://kishanthan.wordpress.com
>>> *
>>> Twitter - *http://twitter.com/kishanthan
>>> *
>>>
>>
>>
>
>
> --
> 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
>
>


-- 

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

Re: [Dev] Can we use ELB 2.1.1 to cluster Carbon 4.3.0 products?

[Nirodha Pramod]

Yes we had a problem with the nodes not joining to ELB (WK member). We will
continue with nginx.

On Thu, Feb 12, 2015 at 1:34 PM, Sameera Jayasoma  wrote:

> Hi Nirodha,
>
> I don't this is possible, but we could patch few components in ELB and get
> it done. Btw, we no longer recommend to use ELB.
>
> Thanks,
> Sameera.
>
> On Thu, Feb 12, 2015 at 12:29 PM, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> Is it possible to use ELB 2.1.1 for cluster Carbon 4.3.0 products.
>> Hazelcast versions in those two differ.
>>
>> Carbon 4.3.0 - hazelcast_3.2.6.wso2v3.jar
>> ESB 2.1.1 - hazelcast_3.0.1.wso2v1.jar
>>
>>
>> Thanks,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 

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

[Dev] Can we use ELB 2.1.1 to cluster Carbon 4.3.0 products?

[Nirodha Pramod]

Hi,

Is it possible to use ELB 2.1.1 for cluster Carbon 4.3.0 products.
Hazelcast versions in those two differ.

Carbon 4.3.0 - hazelcast_3.2.6.wso2v3.jar
ESB 2.1.1 - hazelcast_3.0.1.wso2v1.jar


Thanks,
Nirodha

-- 

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

Re: [Dev] Tenant creation issue with Active Directory

[Nirodha Pramod]

Can we get a temporary patch to carry on testing with AD for [2] . We are
blocked with AD testing and have moved on back to JDBC because of the above
issue.

[2] https://wso2.org/jira/browse/IDENTITY-2915


Thanks,
Nirodha

On Tue, Feb 10, 2015 at 5:40 PM, Pushpalanka Jayawardhana 
wrote:

> Hi Asanthi,
>
> This has been detected previously as well.
> Please refer the thread "[Dev] Multi Tenant support with Active Directory"
> and public jira [1].
>
> [1] - https://wso2.org/jira/browse/IDENTITY-2791
>
> Thanks,
> Pushpalanka.
> --
> Pushpalanka Jayawardhana, B.Sc.Eng.(Hons).
> Software Engineer, WSO2 Lanka (pvt) Ltd;  wso2.com/
> Mobile: +94779716248
> Blog: pushpalankajaya.blogspot.com/ | LinkedIn:
> lk.linkedin.com/in/pushpalanka/ | Twitter: @pushpalanka
>
>
> On Tue, Feb 10, 2015 at 5:15 PM, Asanthi Kulasinghe 
> wrote:
>
>> Hi,
>>
>> We have setup  ESB 4.9.0 with Active Directory as the user store.
>>
>> The following have been updated accordingly.
>> 1. user-mgt.xml
>> 2. 'RootPartition' property in tenant-mgt.xml
>>
>> Error [1] is logged when creating a tenant. The tenant is created in the
>> inactive mode. Certain tenant details are not saved ( tenant password /
>> first name/ last name )
>>
>> Error [2] occurs in the attempt to update  tenant details. Therefore it
>> is not possible even to update and login to the tenant.
>>
>> Does anyone have an idea of what could be causing this issue?  Are there
>> any configuration changes we need to make apart from the above?
>>
>>
>> *[1]
>> *
>>
>> TID: [-1234] [] [2015-02-10 11:16:55,048] ERROR
>> {org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil} -  Failed to add tenant
>> config. tenant-domain: testtenant.com, tenant-admin: testtenant.
>> {org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil}
>> org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceExceptionException:
>> TenantMgtAdminServiceExceptionException
>> at java.lang.J9VMInternals.newInstanceImpl(Native Method)
>> at java.lang.Class.newInstance(Class.java:1774)
>> at
>> org.wso2.carbon.tenant.mgt.stub.TenantMgtAdminServiceStub.addTenant(TenantMgtAdminServiceStub.java:2743)
>> at
>> org.wso2.carbon.tenant.mgt.ui.clients.TenantServiceClient.addTenant(TenantServiceClient.java:90)
>> at
>> org.wso2.carbon.tenant.mgt.ui.utils.TenantMgtUtil.addTenantConfigBean(TenantMgtUtil.java:67)
>> at
>> org.apache.jsp.tenant_002dmgt.submit_005ftenant_005fajaxprocessor_jsp._jspService(submit_005ftenant_005fajaxprocessor_jsp.java:136)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>> at
>> org.apache.catalina.valves.

Re: [Dev] Mysql connection issue

[Nirodha Pramod]

Hi Ratha,

This is either the user does not have enough privileges or you haven't
given remote access permission for clients to connect remotely. If you can
connect from a client from within the server machine then the root cause is
the latter one. To overcome that you have to set the bind-address value to
the ip instead of 127.0.0.1 to give remote access, which is in my.cnf file.
In linux systems it is usually there in /etc/mysql/my.cnf.  Please refer
[2] and [3] for more info.

[2]
http://stackoverflow.com/questions/2482234/how-to-know-mysql-my-cnf-location
[3]
http://www.cyberciti.biz/faq/unix-linux-mysqld-server-bind-to-more-than-one-ip-address/


-Nirodha

On Wed, Feb 11, 2015 at 9:57 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Vijayaratha,
>
> Have you checked this answer[1] at stackoverflow.
> You could try adding a new administrator account:
>
> [1]
> http://stackoverflow.com/questions/1559955/host-xxx-xx-xxx-xxx-is-not-allowed-to-connect-to-this-mysql-server
>
>
> On Wed, Feb 11, 2015 at 9:47 AM, Vijayaratha Vijayasingam  > wrote:
>
>> I checked that option too. My setting is right..Attached screenshot
>>
>> On 11 February 2015 at 12:11, Bhathiya Jayasekara 
>> wrote:
>>
>>> Hi Ratha,
>>>
>>> In MySQL server, *skip-networking* setting must have been enabled. You
>>> have to disable it to allow remote connections. More infor here [1].
>>>
>>> [1]
>>> http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html
>>>
>>> Thanks,
>>> Bhathiya
>>>
>>> On Wed, Feb 11, 2015 at 9:35 AM, Vijayaratha Vijayasingam <
>>> rat...@wso2.com> wrote:
>>>
 Hi all;
 Trying to connect remote mysql server which in windows box. But
 getting[1];

 I can ping to that machine and firewall is off. Root user has all
 privileges.

 Anyone knows the cause, what type of security settings i need to do in
 mysql?

 [1]Caused by:
 com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Could
 not create connection to database server. Attempted reconnect 3 times.
 Giving up.

 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

 at
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

 at
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

 at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

 at com.mysql.jdbc.Util.handleNewInstance(Util.java:377)

 at com.mysql.jdbc.Util.getInstance(Util.java:360)

 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)

 at com.mysql.jdbc.

 Caused by: java.sql.SQLException: null,  message from server: "Host
 '192.168.50.62' is not allowed to connect to this MySQL server"

 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:996)

 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:935)

 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:924)

  at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1037)


 thanks
 --
 -Ratha

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


>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Software Engineer,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <%2B94715478185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> -Ratha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] P2 repo for ESB 4.9.0

[Nirodha Pramod]

Hi,

Can we have the $subject please. We need to test our setups with secure
vault enabled and from Carbon 4.3.0 release it comes as a feature to be
installed from p2-repo.

Thanks,
Nirodha

On Mon, Feb 2, 2015 at 4:05 PM, Asanthi Kulasinghe  wrote:

> Hi,
>
> Can we have $Subject?
>
>
>
> Regards
> *Asanthi Kulasinghe*
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94777355522
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] Server hangs with mssql

[Nirodha Pramod]

Hi Ratha,

We have test APIM 1.8.0 with MSSQL at the early stages and below[1] are the
issues we found. Other than that we didn't experienced any server getting
hanged issue.

[1]
https://wso2.org/jira/browse/APIMANAGER-2823?jql=project%20%3D%20APIMANAGER%20AND%20affectedVersion%20%3D%20%221.8.0%22%20AND%20text%20~%20%22mssql%22

-Nirodha

On Fri, Feb 6, 2015 at 2:17 PM, Isuru Perera  wrote:

> I have used MSSQL datasources with no issues. Did you check OSGi console?
> Perhaps some bundles are not getting activated.
>
> On Wed, Feb 4, 2015 at 2:53 PM, Vijayaratha Vijayasingam 
> wrote:
>
>> Hi all;
>> I configured mssql as DB. When starting the server (AM 1.8.0)it hangs at
>> some point. There is no any error logs or other log infos.[1]
>>
>> Anyone faced such issue before?
>>
>> [1]
>>
>> [2015-02-05 08:12:08,679]  INFO - CarbonCoreActivator User :
>> Administrator, en-US, Asia/Singapore
>> [2015-02-05 08:12:10,056]  WARN - ValidationResultPrinter The running OS
>> : Windows Server 2012 is not a tested Operating System for running WSO2
>> Carbo
>> n
>> [2015-02-05 08:12:10,056]  WARN - ValidationResultPrinter The default
>> keystore (wso2carbon.jks) is currently being used. To maximize security
>> when dep
>> loying to a production environment, configure a new keystore with a
>> unique password in the production server profile.
>> [2015-02-05 08:12:10,181]  INFO - AgentHolder Agent created !
>> [2015-02-05 08:12:10,197]  INFO - AgentDS Successfully deployed Agent
>> Client
>> [2015-02-05 08:12:10,244]  INFO - AgentHolder Agent created !
>> [2015-02-05 08:12:10,275]  INFO - AgentDS Successfully deployed Agent
>> Client
>> [2015-02-05 08:12:23,884]  INFO - TaglibUriRule TLD skipped. URI:
>> http://tiles.apache.org/tags-tiles is already defined
>> [2015-02-05 08:12:28,883]  INFO - EmbeddedRegistryService Configured
>> Registry in 68ms
>> [2015-02-05 08:12:28,976]  INFO - EmbeddedRegistryService Connected to
>> mount at govregistry in 66ms
>> [2015-02-05 08:13:42,880]  INFO - EmbeddedRegistryService Connected to
>> mount at govregistry in 399ms
>> [2015-02-05 08:13:59,519]  INFO - RegistryCoreServiceComponent Registry
>> Mode: READ-WRITE
>>
>>
>> --
>> -Ratha
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> 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
>
>


-- 

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

[Dev] [AM 1.8.0] [Blocker] Cannot save API in Manage state for users with create permission

[Nirodha Pramod]

Hi,

Users in 'API Provider' role (login and create permissions only) cannot
save APIs in the Manage state. Hence the API providers cannot give tier
level, subscription availability setting etc when creating the API.

[1] https://wso2.org/jira/browse/APIMANAGER-3158

Thanks,
Nirodha




-- 

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

Re: [Dev] Does AS (or Carbon Server) make sure to properly start it self, before join with the cluster ?

[Nirodha Pramod]

Hi Asanka,

I too have observed this behavior before. So the AS clustering ports get
opened early and joins with the ELB and the rest of the cluster before the
server is fully initialized.

-Nirodha

On Wed, Sep 17, 2014 at 7:16 AM, Asanka Vithanage  wrote:

>
> Hi All,
>
> I am currently testing on a ELB 211 fronted 1 manager/2 worker AS 521
> cluster. Here when i am following below steps, i am getting below noted
> errors on ELB stack traces.
>
>
> *Steps:*
>
> Setup a 1 manager/2 worker node ELB fronted setup
>
> Invoke SimpleStockQuate service deployed on AS 521(http path) continuously
> using jmeter script(with 1000 jmeter threads and 10 seconds ramp-up period)
>
> Down the worker node using ./wso2server.sh stop command
>
> Startup the downed worker node and check the ELB logs
>
> *Issue:*
>
> Intermittently observed following issue on ELB stack trace, but AS stack
> traces does not show any thing except member left/member join messages
>
>
> Note: I have tried above steps nearly 10 times and out of them 3 times
> observed below error.[Attached ELB log for further reference]
>
> TID: [0] [ELB] [2014-09-17 11:13:55,107]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent} -
>  Member left [aa7c330e-eb71-488c-a905-79c3a07ba671]: /10.0.0.85:4300
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent}
>
> TID: [0] [ELB] [2014-09-17 11:13:55,122]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent} -
>  Member left [aa7c330e-eb71-488c-a905-79c3a07ba671]: /10.0.0.85:4300
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent}
>
> TID: [0] [ELB] [2014-09-17 11:16:12,293]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent} -
>  Member joined [cd2f1123-f734-456f-bc3f-7ae03ec0142a]: /10.0.0.85:4300
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent}
>
> TID: [0] [ELB] [2014-09-17 11:16:12,297]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent} -
>  Member joined [cd2f1123-f734-456f-bc3f-7ae03ec0142a]: /10.0.0.85:4300
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent}
>
> TID: [0] [ELB] [2014-09-17 11:16:15,423]  INFO
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent} -
>  Application member Host:10.0.0.85, Remote Host:null, Port: 4300,
> HTTP:9765, HTTPS:9445, Domain: wso2.as.domain, Sub-domain:worker,
> Active:true joined application cluster
> {org.wso2.carbon.core.clustering.hazelcast.HazelcastGroupManagementAgent}
>
> TID: [0] [ELB] [2014-09-17 11:16:16,139]  WARN
> {org.apache.synapse.transport.passthru.TargetHandler} -  Connection closed
> by target host before receiving the request
> {org.apache.synapse.transport.passthru.TargetHandler}
>
> TID: [0] [ELB] [2014-09-17 11:16:16,169]  INFO
> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -
>  Failed to send message to Member Host:10.0.0.85, Remote Host:null, Port:
> 4300, HTTP:9765, HTTPS:9445, Domain: wso2.as.domain, Sub-domain:worker,
> Active:true . Error Code: 101508
> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}
>
> TID: [0] [ELB] [2014-09-17 11:16:16,170] ERROR
> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint} -
>  Error sending request! Connection timeout after request is read by the
> host as.wso2.com . Error code: 101508 Protocol State: RESPONSE HEAD
> {org.wso2.carbon.lb.endpoint.endpoint.TenantAwareLoadBalanceEndpoint}
>
>
>
> After analyzing AS and ELB stack-traces, i felt that AS worker nodes join
> the cluster before it properly initialized. So when ELB handover the job to
> AS worker nodes, It fails to do the job.
>
>
> Does my observation make sense here or is there any other reason for this
> behavior?
>
>
> WDYT?
>
>
>
> --
> Asanka Vithanage
> Senior Software Engineer -QA
> Mobile: +94 0716286708
> Email: asan...@wso2.com
> WSO2 Inc. www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] API-Manager Token Validity period in a clustered setup

[Nirodha Pramod]

Hi Dinusha,

Let me clarify my question. If the token is generated by the keymanager
node why does not that node itself set the validity period read from KM
node's identity.xml, at the time of token generation.  Why does KM node
generate the token and store node sets the validity period. Why not KM node
does both tasks?

regards,
Nirodha



On Mon, Jul 28, 2014 at 12:42 PM, Sanjeewa Malalgoda 
wrote:

>
>
>
> On Sun, Jul 27, 2014 at 11:56 PM, Dinusha Senanayaka 
> wrote:
>
>>
>>
>>
>> On Mon, Jul 28, 2014 at 11:44 AM, Nirodha Pramod 
>> wrote:
>>
>>> ​Hi Sanjeewa,
>>>
>>> Ain't it a wrong design? ​IMO if the APPLICATION TOKEN is generated in
>>> the KeyManager node (which you configure the server url in the store), then
>>> it should read the validity period from the key manager node itself at the
>>> time of token generation. I dont understand why it reads the validity
>>> period from store node's configuration and then generate the token in
>>> keymanager node. Configuring all the nodes in the same way is not a good
>>> solution.
>>>
>>
>> Once the store/key-maanger nodes are separated, we could not read the
>> identity.xml of key-manager from the store using file system. To do that,
>> we need to expose a service that could read the identity.xml properties.
>> But this complicate the implementation and introduce additional service
>> call in the store load. So defining it in store is ok IMO.
>>
> +1.
>
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> thanks,
>>> Nirodha
>>>
>>>
>>> On Mon, Jul 28, 2014 at 11:35 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
>>>> The reason for this issue is, in API store when we generate token
>>>> default validity time will pick from store nodes config file. Then you will
>>>> see store nodes validity period(configured in identity.xml) in token
>>>> validity period box. But if you send token generation request(user access
>>>> token) to key manager through gateway then it will eventually hit key
>>>> manager. Then validity period in key manager will effect. There is no
>>>> logical reason for this. We need to add this configuration to all nodes in
>>>> same way.
>>>>
>>>> Thanks,
>>>> sanjeewa.
>>>>
>>>>
>>>> On Sun, Jul 27, 2014 at 10:56 PM, Asanthi Kulasinghe 
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We have observed that the token expiration times in a API-Manager
>>>>> Clustered set up for token types Application access token and User access
>>>>> token, are taken from the values set in 2 different nodes.
>>>>>
>>>>> ie:
>>>>>   value of the Store
>>>>> node's identity.xml  is considered for Application access token expiration
>>>>> time.
>>>>>   value of the Key Manager
>>>>> node's identity.xml is considered for the User access token expiration 
>>>>> time.
>>>>>
>>>>> Is there a logical reason behind this or should the values set in Key
>>>>> Manager node be considered for both token types?
>>>>>
>>>>> Regards
>>>>> *Asanthi Kulasinghe*
>>>>> WSO2 Inc; http://www.wso2.com/.
>>>>> Mobile: +94777355522
>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Sanjeewa Malalgoda*
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Nirodha Gallage*
>>> Senior Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Dinusha Dilrukshi
>> Senior Software Engineer
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  <http://sanjeewamalalgoda.blogspot.com/>blog
> :http://sanjeewamalalgoda.blogspot.com/
> <http://sanjeewamalalgoda.blogspot.com/>
>
>
>


-- 

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

Re: [Dev] API-Manager Token Validity period in a clustered setup

[Nirodha Pramod]

​Hi Sanjeewa,

Ain't it a wrong design? ​IMO if the APPLICATION TOKEN is generated in the
KeyManager node (which you configure the server url in the store), then it
should read the validity period from the key manager node itself at the
time of token generation. I dont understand why it reads the validity
period from store node's configuration and then generate the token in
keymanager node. Configuring all the nodes in the same way is not a good
solution.

thanks,
Nirodha


On Mon, Jul 28, 2014 at 11:35 AM, Sanjeewa Malalgoda 
wrote:

> The reason for this issue is, in API store when we generate token default
> validity time will pick from store nodes config file. Then you will see
> store nodes validity period(configured in identity.xml) in token validity
> period box. But if you send token generation request(user access token) to
> key manager through gateway then it will eventually hit key manager. Then
> validity period in key manager will effect. There is no logical reason for
> this. We need to add this configuration to all nodes in same way.
>
> Thanks,
> sanjeewa.
>
>
> On Sun, Jul 27, 2014 at 10:56 PM, Asanthi Kulasinghe 
> wrote:
>
>> Hi,
>>
>> We have observed that the token expiration times in a API-Manager
>> Clustered set up for token types Application access token and User access
>> token, are taken from the values set in 2 different nodes.
>>
>> ie:
>>   value of the Store node's
>> identity.xml  is considered for Application access token expiration time.
>>   value of the Key Manager node's
>> identity.xml is considered for the User access token expiration time.
>>
>> Is there a logical reason behind this or should the values set in Key
>> Manager node be considered for both token types?
>>
>> Regards
>> *Asanthi Kulasinghe*
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94777355522
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

[Dev] [API-M] Token expiration time is set 300s less than the given value when generating tokens using the UI

[Nirodha Pramod]

Hi,

Noticed this API cloud. I have mentioned the steps in JIRA [1]. Can this be
due to the default value of 300 in
identity.xml ??


regards,
Nirodha

[1] https://wso2.org/jira/browse/CLOUD-166

-- 

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

Re: [Dev] Identity Server 5.0.0 nightly build - 16-05-2014

[Nirodha Pramod]

Hi All,

Any update on new packs?

regards,
Nirodha




On Fri, May 16, 2014 at 5:25 PM, Prabath Abeysekera wrote:

> Thanks for the prompt response guys!
>
>
> On Fri, May 16, 2014 at 5:12 PM, Johann Nallathamby wrote:
>
>> Hi Prabath,
>>
>> Will be able to finish it by EOD.
>>
>>
>> On Fri, May 16, 2014 at 5:03 PM, Prabath Abeysekera wrote:
>>
>>> Hi Dulanja, Johann,
>>>
>>> Any update on the P2 repo? Would you guys be able to give us a rough
>>> time estimation as to when this will be available?
>>>
>>>
>>> Cheers,
>>> Prabath
>>>
>>>
>>> On Fri, May 16, 2014 at 10:13 AM, Asanthi Kulasinghe 
>>> wrote:
>>>
 Hi ,

 Can we have a p2 repo for this? Would be great if we could have one
 today itself.
 API-M 1.7.0 verification with IS as a Key Manager will be on hold until
 then.

 Regards
 Asanthi


 On Fri, May 16, 2014 at 1:24 AM, Dulanja Liyanage wrote:

> Hi All,
>
> Please find the subject at [1]
>
> Built from: SVN r202841
>
> [1]
> https://svn.wso2.org/repos/wso2/scratch/IS-5.0.0/15-05-2014/nightly-build/wso2is-5.0.0.zip
>
> Thanks & Regards
>
> Dulanja
>
> --
> Dulanja Liyanage
> WSO2 Inc.
> M: +94776764717
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Asanthi Kulasinghe*
 WSO2 Inc; http://www.wso2.com/.
 Mobile: +94777355522



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


>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Associate Technical Lead, Data TG.
>>> WSO2 Inc.
>>> Email: praba...@wso2.com
>>> Mobile: +94774171471
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Associate Technical Lead
>> Integration Technologies Team
>>  WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com *
>>
>
>
>
> --
> Prabath Abeysekara
> Associate Technical Lead, Data TG.
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] API Manager 1.7.0 & ELB-2.1.1 nightly build packs 06-05-2014

[Nirodha Pramod]

Hi,

Cannot browse registry in above API-M pack.

JIRA - https://wso2.org/jira/browse/APIMANAGER-2310


regards,
Nirodha


On Wed, May 7, 2014 at 1:34 PM, Anjana Fernando  wrote:

> Hi,
>
> Yeah, +1, lets anyway fix it in patch0007.
>
> Cheers,
> Anjana.
>
>
> On Wed, May 7, 2014 at 1:20 PM, Isuru Udana  wrote:
>
>> Hi Anjana,
>>
>>
>> On Wed, May 7, 2014 at 1:12 PM, Anjana Fernando  wrote:
>>
>>> Hi Manoj,
>>>
>>> So this is a bug that can affect DSS too? .. if so, we have to patch in
>>> 0007 itself.
>>>
>> This is only affecting for non blocking transports (ptt/nio). So DSS will
>> not get affected by this.
>> However IMO we need to revert this in Patch0007 as it is not good to
>> release a kernel patch with a serious bug.
>>
>>
>>>
>>> Cheers,
>>> Anjana.
>>>
>>>
>>>  On Wed, May 7, 2014 at 12:44 PM, Manoj Kumara  wrote:
>>>
 Hi Nuwan,

 currently patch0007 is breezed due to due to DSS release. I'll revert
 this after talking to DSS team.

 Thanks,
 Manoj


 *Manoj Kumara*
 Software Engineer
 WSO2 Inc. http://wso2.com/
 *lean.enterprise.middleware*
 Mobile: +94713448188


 On Wed, May 7, 2014 at 12:27 PM, Nuwan Dias  wrote:

> Hi Charitha,
>
> We figured out that this had been a regression due to a kernel patch -
> patch0007. Commit revision is r200946. Thanks IsuruU for the
> assistance.
>
> @Manoj, please revert this patch urgently since it causes a 202
> Accepted to be sent for all tenant requests and drops the response body.
>
> Thanks,
> NuwanD.
>
>
> On Wed, May 7, 2014 at 3:53 AM, Charitha Kankanamge  > wrote:
>
>> ​Thanks Sanjeewa. MSSQL related blockers are fixed in this pack.
>> Verified the jiras.
>>  However, there is a critical MT failure which can be reproduced in a
>> fresh pack as well.
>>
>> When you invoke an API in a tenant, the response is not returned.
>> Given below is the wire log. As you can see, the response is not sent 
>> back.
>> Client always gets http 202 acknowledgement instead of the actual 
>> response.
>> Basically MT is broken.
>>
>> Note that the same API works with the same backend in super tenant
>> mode. So this must be a MT regression.
>>
>> [2014-05-07 03:25:31,891] DEBUG - wire >> "POST /t/
>> superqa.com/axis2API/v1 HTTP/1.1[\r][\n]"
>> [2014-05-07 03:25:31,892] DEBUG - wire >> "Connection: close[\r][\n]"
>> [2014-05-07 03:25:31,893] DEBUG - wire >> "Accept-Encoding:
>> gzip,deflate[\r][\n]"
>> [2014-05-07 03:25:31,894] DEBUG - wire >> "Content-Type:
>> text/xml;charset=UTF-8[\r][\n]"
>> [2014-05-07 03:25:31,894] DEBUG - wire >> "SOAPAction:
>> "urn:echoString"[\r][\n]"
>> [2014-05-07 03:25:31,895] DEBUG - wire >> "Authorization: Bearer
>> 4636d529ea62b726e312a53794dccf36[\r
>> ][\n]"
>> [2014-05-07 03:25:31,896] DEBUG - wire >> "Content-Length:
>> 307[\r][\n]"
>> [2014-05-07 03:25:31,896] DEBUG - wire >> "Host: 10.0.0.2:8280
>> [\r][\n]"
>> [2014-05-07 03:25:31,897] DEBUG - wire >> "User-Agent:
>> Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]"
>> [2014-05-07 03:25:31,897] DEBUG - wire >> "[\r][\n]"
>> [2014-05-07 03:25:31,898] DEBUG - wire >> "> xmlns:soapenv="http://schemas.xmlsoap.o
>> rg/soap/envelope/" xmlns:ser="http://service.carbon.wso2.org
>> ">[\r][\n]"
>>  [2014-05-07 03:25:31,898] DEBUG - wire >> "
>> [\r][\n]"
>> [2014-05-07 03:25:31,899] DEBUG - wire >> "   [\r][\n]"
>> [2014-05-07 03:25:31,899] DEBUG - wire >> "
>>  [\r][\n]"
>> [2014-05-07 03:25:31,899] DEBUG - wire >> "
>> [\r][\n]"
>> [2014-05-07 03:25:31,900] DEBUG - wire >> "
>> test[\r][\n]"
>> [2014-05-07 03:25:31,900] DEBUG - wire >> "
>>  [\r][\n]"
>> [2014-05-07 03:25:31,901] DEBUG - wire >> "   [\r][\n]"
>> [2014-05-07 03:25:31,901] DEBUG - wire >> ""
>> [2014-05-07 03:25:31,917]  INFO - LogMediator To:
>> local://axis2services/axis2API/v1, WSAction: urn:e
>> choString, SOAPAction: urn:echoString, MessageID:
>> urn:uuid:AE969D38832DDA67D11399413331911, Directio
>> n: request, Envelope: > encoding="utf-8"?>http://service.carbon.wso2.org";>
>>   
>>  
>>  test
>>   
>>
>> [2014-05-07 03:25:31,929] DEBUG - wire << "POST
>> /services/Axis2Service HTTP/1.1[\r][\n]"
>> [2014-05-07 03:25:31,930] DEBUG - wire << "Accept-Encoding:
>> gzip,deflate[\r][\n]"
>> [2014-05-07 03:25:31,930] DEBUG - wire << "Content-Type:
>> text/xml;charset=UTF-8[\r][\n]"
>> [2014-05-07 03:25:31,930] DEBUG - wire << "SOAPAction:
>> "urn:echoString"[\r][\n]"
>> [2014-05-07 03:25:31,931] DEBUG - wire << "Transfer-Encoding:
>> chunked[\r][\n]"
>> [2014-05-07 03:25:31,931] DEBUG - wire << "Host:
>> localhost:9764[\r][\n]"
>> [2014-05-07 03:25:31,931] DEBUG - wire << "C

Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle

[Nirodha Pramod]

Hi Lakmali,

There is another blocking issue[6] with Oracle when generating Keys in
store. Please have a look.

regards,
Nirodha

[6] https://wso2.org/jira/browse/APIMANAGER-2302



On Mon, May 5, 2014 at 9:38 PM, Lakmali Baminiwatta wrote:

> Hi,
>
> Please find the fixed oracle script attached.
>
> Thanks,
> Lakmali
>
>
> On 5 May 2014 21:11, Nirodha Pramod  wrote:
>
>> Hi Lakmali,
>>
>> Can we have a patch for this issue [3] this is an absolute blocker for
>> testing on Oracle.
>>
>> regards,
>> Nirodha
>>
>>
>> On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta wrote:
>>
>>> Hi,
>>>
>>> On 3 May 2014 00:26, Nirodha Pramod  wrote:
>>>
>>>> Hi,
>>>>
>>>> Following two blocking issues were found with the oracle script for
>>>> AM_DB on 29th April pack. Please have a look.
>>>>
>>>
>>>> [1] https://wso2.org/jira/browse/APIMANAGER-2266
>>>>
>>>
>>> Had been Fixed now.
>>>
>>> [2] https://wso2.org/jira/browse/APIMANAGER-2268
>>>>
>>>
>>>  It seems this issue has occurred due to user not having permissions to
>>> create triggers.
>>>
>>>  Fixed the issue[3] in r201794.
>>>
>>> [3] https://wso2.org/jira/browse/APIMANAGER-2264
>>>
>>>  Thanks,
>>> Lakmali
>>>
>>>>
>>>> regards,
>>>> Nirodha
>>>>
>>>> --
>>>>
>>>> *Nirodha Gallage*
>>>> Senior Software Engineer, QA.
>>>> WSO2 Inc.: http://wso2.com/
>>>> Mobile: +94716429078
>>>>
>>>
>>>
>>>
>>> --
>>> Lakmali Baminiwatta
>>>  Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> lean.enterprise.middleware
>>> mobile:  +94 71 2335936
>>> blog : lakmali.com
>>>
>>>
>>
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Lakmali Baminiwatta
>  Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>


-- 

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

[Dev] APIM 1.7.0 User management features are not up to date with IS 5.0.0

[Nirodha Pramod]

Hi,

Please note the subject as both releases are going on the same chunk. There
are user core issues like [1] which are there in APIM but not in IS. Also
observed that the 'org.wso2.carbon.user.mgt.ui_' version is old in APIM.
Please have a look.

[1] https://wso2.org/jira/browse/APIMANAGER-2293

jira created [2]  - https://wso2.org/jira/browse/APIMANAGER-2294

regards,
Nirodha
-- 

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

Re: [Dev] Migration scripts for API-M 1.6.0 to 1.7.0

[Nirodha Pramod]

Hi,

Can we have this as soon as possible. Created a jira for this.

[1] https://wso2.org/jira/browse/APIMANAGER-2292

regards,
Nirodha


On Thu, Apr 17, 2014 at 7:54 PM, Nuwan Dias  wrote:

> Hi Nirodha,
>
> This is still not done. We have a list maintained to identify what needs
> to be migrated, quite a long list actually :). But work has not been
> initiated on the migration script. Will let you know once done.
>
> Thanks,
> NuwanD.
>
>
> On Thu, Apr 17, 2014 at 11:41 AM, Nirodha Pramod  wrote:
>
>> Ping!! On the $subject.
>>
>>
>> On Thu, Apr 10, 2014 at 11:37 AM, Nirodha Pramod wrote:
>>
>>> Hi,
>>>
>>> Do we have the $subject ready?
>>>
>>> regards,
>>> Nirodha
>>>
>>> --
>>>
>>> *Nirodha Gallage*
>>> Senior Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>
>>
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

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

Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle

[Nirodha Pramod]

Hi Lakmali,

Can we have a patch for this issue [3] this is an absolute blocker for
testing on Oracle.

regards,
Nirodha


On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta wrote:

> Hi,
>
> On 3 May 2014 00:26, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> Following two blocking issues were found with the oracle script for AM_DB
>> on 29th April pack. Please have a look.
>>
>
>> [1] https://wso2.org/jira/browse/APIMANAGER-2266
>>
>
> Had been Fixed now.
>
> [2] https://wso2.org/jira/browse/APIMANAGER-2268
>>
>
>  It seems this issue has occurred due to user not having permissions to
> create triggers.
>
>  Fixed the issue[3] in r201794.
>
> [3] https://wso2.org/jira/browse/APIMANAGER-2264
>
>  Thanks,
> Lakmali
>
>>
>> regards,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Lakmali Baminiwatta
>  Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>


-- 

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

Re: [Dev] [Blocker] Issues with AM_DB scripts for Oracle

[Nirodha Pramod]

Hi,

For issue [2] I have given the privileges as mentioned in [4] but did not
work. And as Lakmali mentioned offline we need to give privileges as below.
Hence the docs need to be updated. Created a JIRA [5] for that.

sqlplus>create user lakmaliuser identified by wso2;
sqlplus>grant connect,resource to lakmaliuser with admin option;
sqlplus>connect lakmaliuser/wso2


[4] https://docs.wso2.org/display/AM160/Setting+up+with+Oracle
[5] https://wso2.org/jira/browse/DOCUMENTATION-796


thanks,
Nirodha


On Mon, May 5, 2014 at 10:56 AM, Lakmali Baminiwatta wrote:

> Hi,
>
> On 3 May 2014 00:26, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> Following two blocking issues were found with the oracle script for AM_DB
>> on 29th April pack. Please have a look.
>>
>
>> [1] https://wso2.org/jira/browse/APIMANAGER-2266
>>
>
> Had been Fixed now.
>
> [2] https://wso2.org/jira/browse/APIMANAGER-2268
>>
>
>  It seems this issue has occurred due to user not having permissions to
> create triggers.
>
>  Fixed the issue[3] in r201794.
>
> [3] https://wso2.org/jira/browse/APIMANAGER-2264
>
>  Thanks,
> Lakmali
>
>>
>> regards,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Lakmali Baminiwatta
>  Software Engineer
> WSO2, Inc.: http://wso2.com
> lean.enterprise.middleware
> mobile:  +94 71 2335936
> blog : lakmali.com
>
>


-- 

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

[Dev] [Blocker] Issues with AM_DB scripts for Oracle

[Nirodha Pramod]

Hi,

Following two blocking issues were found with the oracle script for AM_DB
on 29th April pack. Please have a look.

[1] https://wso2.org/jira/browse/APIMANAGER-2266
[2] https://wso2.org/jira/browse/APIMANAGER-2268

regards,
Nirodha

-- 

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

Re: [Dev] API Gateway alters POST request URLs in API-Manager 1.7.0

[Nirodha Pramod]

Hi Nuwan,

Isn't this a bug?  When we tested this we used a RESTful service (starbucks
sample) as the back end. And you can't expect the client would always send
application/xml as the Content-Type when calling a rest backend. Sending a
text/xml is totally valid when calling a RESTful backend.

regards,
Nirodha


On Thu, May 1, 2014 at 12:35 PM, Nuwan Dias  wrote:

> Its not that it alters request urls, it drops the request parameters from
> the outgoing request when the Content-Type is text/xml.
>
> If the API context is:  /stockquote/1.0.0
>
> Endpoint is: http://host:port/StockQuoteService
>
> Request url is:  /stockquote/1.0.0/getQuote
>
> In the case of applcation/xml, the outgoing request is http://host:port
> /StockQuoteService/getQuote
>
> In the case of text/xml, the outgoing request is http://host:port
> /StockQuoteService
>
> As you see, in the case of text/xml, 'getQuote' is not sent to the back
> end.
>
> I presume this is the correct behavior since text/xml is normally used for
> SOAP?
>
> Thanks,
> NuwanD.
>
>
> On Thu, May 1, 2014 at 11:37 AM, Asanthi Kulasinghe wrote:
>
>> Hi,
>>
>> Context path of POST request URLs of APIs get dropped at the gateway
>> when  invoked with the content-type 'text/xml'.
>> I have reported the issue under [1].
>> Please look into this.
>>
>> [1] - https://wso2.org/jira/browse/APIMANAGER-2256
>>
>>
>> Regards
>>  *Asanthi Kulasinghe*
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94777355522
>>
>>
>>
>
>
> --
> Nuwan Dias
>
> Associate Tech Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] Multiple 'Scope' support in API-M 1.7.0

[Nirodha Pramod]

 <@dev>

Hi,

Cannot ad scopes for APIs in the latest pack (29 Apr) due to [1], please
have a look.

[1] https://wso2.org/jira/browse/APIMANAGER-2246

regards,
Nirodha


On Mon, Apr 28, 2014 at 8:57 AM, Nuwan Dias  wrote:

> On Sun, Apr 27, 2014 at 10:59 PM, Nirodha Pramod  wrote:
>
>>
>> ​Hi,
>>
>> As we are doing the proper implementation of OAuth2 'scope' this time, do
>> we have the $subject in API-M 1.7.0 release, ​If so,
>>
>
> Yes.
>
>>
>> 1) Is it possible to generate a token for multiple scopes? How?
>>
>
> Just pass in the scopes in the token generation request. For example,
>
> grant_type=password&username=&password=&scope=read_tweet
> update_status
>
>>
>> 2) Is it possible to restrict a particular resource in an API, for
>> multiple scopes?
>>
>
> No, a resource (ex: GET /tweets) can only be given a single scope.
>
>>
>> thanks,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Nuwan Dias
>
> Associate Tech Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

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

Re: [Dev] Not possible to log into API store in the cluster set up after replacing ELB 2.1.0 with ELB 2.1.1

[Nirodha Pramod]

This is a blocker for using ELB 2.1.1 for testing with the cluster setup.
We have reverted back to 2.1.0.


On Tue, Apr 29, 2014 at 10:04 AM, Asanthi Kulasinghe wrote:

>
> Hi,
>
> Please look into the issue reported under [1] with relevance to $Subject.
>
> [1] https://wso2.org/jira/browse/APIMANAGER-2239
>
>
> Thanks & Regards
> *Asanthi Kulasinghe*
> Software Engineer - QA
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94777355522
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

[Dev] [API-M] Preferred way of providing scope details for subscribers ?

[Nirodha Pramod]

Hi,

What is the preferred way of providing information on 'scope' restrictions
of an API. At the moment we don't show any information about scopes on the
Store, and the subscribers has no way knowing that information. We can
provide that with API documentation but is it the standard/preferred way?

regards,
Nirodha

-- 

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

[Dev] [Blocker] [API-M 1.7.0] KeyManager cluster fronted with ELB doesn't function properly

[Nirodha Pramod]

Hi,

APIs cannot be invoked when we use clustered keymanger fronted with ELB, in
the distributed setup. This is blocker to continue testing on the
keymanager cluster. Please have a look.

https://wso2.org/jira/browse/APIMANAGER-2192

regards,
Nirodha
-- 

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

Re: [Dev] Migration scripts for API-M 1.6.0 to 1.7.0

[Nirodha Pramod]

Ping!! On the $subject.


On Thu, Apr 10, 2014 at 11:37 AM, Nirodha Pramod  wrote:

> Hi,
>
> Do we have the $subject ready?
>
> regards,
> Nirodha
>
> --
>
> *Nirodha Gallage*
> Senior Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>



-- 

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

[Dev] Migration scripts for API-M 1.6.0 to 1.7.0

[Nirodha Pramod]

Hi,

Do we have the $subject ready?

regards,
Nirodha

-- 

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

[Dev] [Doc] API-M gateway node has to use the shared registry database

[Nirodha Pramod]

Hi,

As per the clustering doc [1] we do not have to use the shared user DB and
the registry DB in the gateway node of the API-M distributed setup. But
doing that leads to not being able to publish APIs in tenant mode [2]. Only
for supertenant mode it works. Please fix the docs. I have created a doc
jira [3] for this.

[1] https://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager
[2] https://wso2.org/jira/browse/APIMANAGER-2147
[3] https://wso2.org/jira/browse/DOCUMENTATION-703

regards,
Nirodha

-- 

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

[Dev] Blocking UI issue with IE in chunk8 release

[Nirodha Pramod]

Hi All,

This issue [1] was reported by me few weeks back and its a UI blocker for
using Internet Explorer. Are we going to release chunk 8 products with this
issue??

[1] https://wso2.org/jira/browse/APIMANAGER-2056

regards,
Nirodha


-- 

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

[Dev] new ELB pack for test with this release

[Nirodha Pramod]

Hi,

Is it possible to get an new ELB pack (v2.1.1 ??) to test with the products
releasing in this chunk8?

regards,
Nirodha


-- 

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

[Dev] Can we have a P2 repo for the upcoming release

[Nirodha Pramod]

Hi,

Can we please have the $subject. This is much needed for API-M testing.

regards,
Nirodha

-- 

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

[Dev] Tenant specific external store feature is totally broken in API-M 2.0.0

[Nirodha Pramod]

Hi,

This new feature is totally broken in the 14th March pack. Please see the
below issues reported.

[1] https://wso2.org/jira/browse/APIMANAGER-2081
[2] https://wso2.org/jira/browse/APIMANAGER-2082
[3] https://wso2.org/jira/browse/APIMANAGER-2083
[4] https://wso2.org/jira/browse/APIMANAGER-2084

regards,
Nirodha


-- 

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

[Dev] Issue with API-M failover endpoints

[Nirodha Pramod]

Hi,

Observed following two blocking issues with API-M latest (14March) pack
with regard to Failover endpoints.

[1] https://wso2.org/jira/browse/APIMANAGER-1910
[2] https://wso2.org/jira/browse/APIMANAGER-2078

regards,
Nirodha

-- 

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

Re: [Dev] is broken in API-M 2.0.0

[Nirodha Pramod]

Hi Nuwan,

For the default configurations in api-manager.xml (everything is localhost)
why cannot we consider the webcontext root, same as we consider that in
server URL in carbon.xml.

https://${carbon.local.ip}:${carbon.management.port}
*${carbon.context}*/services/

This would be really "user friendly" for the end user rather than changing
several places in apimanager.xml. WDYT?

regards,
Nirodha






On Mon, Mar 17, 2014 at 4:55 PM, Nuwan Dias  wrote:

> Hi Nirodha,
>
> AFAIK you have to change the admin service url's which are configured on
> the api-manager.xml if you are changing the web context root.
>
> Thanks,
> NuwanD.
>
>
> On Mon, Mar 17, 2014 at 3:05 PM, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> When a web context root is used in API-M, users cannot log in to
>> publisher and store, because the AuthenticationAdmin service request URL
>> doesn't include the context root.
>>
>> [1] https://wso2.org/jira/browse/APIMANAGER-2057
>>
>> regards,
>> Nirodha
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

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

[Dev] is broken in API-M 2.0.0

[Nirodha Pramod]

Hi,

When a web context root is used in API-M, users cannot log in to publisher
and store, because the AuthenticationAdmin service request URL doesn't
include the context root.

[1] https://wso2.org/jira/browse/APIMANAGER-2057

regards,
Nirodha

-- 

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

[Dev] Usage of 'AccessTokenDefaultValidityPeriod' in identity.xml

[Nirodha Pramod]

Hi,

What's the usage of  in identity.xml  in
the context of API-M. There is already,
   and
 configurations as well which are
used to configure expiration times of Application Access token and User
Tokens.  So what's the usage of the first one.

thanks,
Nirodha
-- 

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

Re: [Dev] API MANAGER - Clarification on behavior of (identity.xml)

[Nirodha Pramod]

Makes sense. Thanks Nuwan.


On Thu, Mar 6, 2014 at 12:33 PM, Nuwan Dias  wrote:

> Hi,
>
> AFAIK the token object which is in the cache is aware of its creation
> time, lifetime, etc. So when you make a request with a particular token,
> the token validator will first check whether there is a cache entry for
> that token. If there is, it will pick it up from the cache and check its
> validity (by comparing system time to token creation time) and decide
> whether the token is expired or not.
>
> Thanks,
> NuwanD.
>
>
> On Thu, Mar 6, 2014 at 12:20 PM, Nirodha Pramod  wrote:
>
>> Hi Johann,
>>
>> But since true is set to true,
>> doesn't it cache the token (for 15mins? AFAIK) ? If I am wrong how does the
>> OAuth Cache behave in this case?
>>
>> regards,
>> Nirodha
>>
>>
>>  On Thu, Mar 6, 2014 at 11:31 AM, Johann Nallathamby wrote:
>>
>>>  This behavior is correct since you have set the token validity as 60s.
>>> After one minute the token is invalid.
>>>
>>>
>>> On Thu, Mar 6, 2014 at 11:03 AM, Asanthi Kulasinghe wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> Can someone explain the behaviour of
>>>> true , in identity.xml of API-Manager.
>>>>
>>>> Does it have an impact on the token expiration time?
>>>>
>>>> With the following configurations, my token expires exactly after 60
>>>> seconds, even if the API has been invoked before the expiration.
>>>>
>>>> identity.xml :
>>>>
>>>> 60
>>>>   0
>>>>   true
>>>>
>>>> api-manager.xml :
>>>>
>>>> false
>>>>
>>>> false
>>>>
>>>> Is this correct or should the token be cached for the default duration
>>>> of 15 mins since  is set to true?
>>>>
>>>> Regards
>>>>
>>>> *Asanthi Kulasinghe*
>>>> Software Engineer - QA
>>>> WSO2 Inc; http://www.wso2.com/.
>>>> Mobile: +94777355522
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Senior Software Engineer
>>> Integration Technologies Team
>>>  WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



-- 

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

Re: [Dev] API MANAGER - Clarification on behavior of (identity.xml)

[Nirodha Pramod]

Hi Johann,

But since true is set to true, doesn't
it cache the token (for 15mins? AFAIK) ? If I am wrong how does the OAuth
Cache behave in this case?

regards,
Nirodha


On Thu, Mar 6, 2014 at 11:31 AM, Johann Nallathamby  wrote:

> This behavior is correct since you have set the token validity as 60s.
> After one minute the token is invalid.
>
>
> On Thu, Mar 6, 2014 at 11:03 AM, Asanthi Kulasinghe wrote:
>
>>
>> Hi,
>>
>> Can someone explain the behaviour of
>> true , in identity.xml of API-Manager.
>>
>> Does it have an impact on the token expiration time?
>>
>> With the following configurations, my token expires exactly after 60
>> seconds, even if the API has been invoked before the expiration.
>>
>> identity.xml :
>>
>> 60
>>   0
>>   true
>>
>> api-manager.xml :
>>   false
>>   false
>>
>> Is this correct or should the token be cached for the default duration of
>> 15 mins since  is set to true?
>>
>> Regards
>>
>> *Asanthi Kulasinghe*
>> Software Engineer - QA
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile: +94777355522
>>
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Senior Software Engineer
> Integration Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

Re: [Dev] [APIM] Status update on improving automated tests for API manager

[Nirodha Pramod]

Hi,

I think it would be a lot easy if Sanjeewa could mark the scenarios he
wrote test cases for, in our test plan [1]. It would be a lot more time
consuming if we have to go through the java test classes he wrote and try
to figure out the test cases.

regards,
Nirodha

[1]
https://docs.google.com/a/wso2.com/spreadsheet/ccc?key=0AmcQWA48EWBddEdzVVZ4aDJTVTBOeV9fVkE0dU9KMWc&usp=drive_web#gid=62



On Wed, Feb 26, 2014 at 3:09 PM, Krishantha Samaraweera  wrote:

> Hi Evanthika,
>
> Shall we update QA Test plan and mark the scenarios which are automated by
> Sanjeewa. Maintaining Test scenario and test case mapping correctly would
> help us a lot in future.
>
> Thanks,
> Krishantha.
>
>
>
> On Tue, Feb 25, 2014 at 10:40 AM, Sanjeewa Malalgoda wrote:
>
>> Hi All,
>> We were able to cover following test cases with newly introduced test
>> cases. These test cases were committed to 2.0.0 product source. Now you can
>> run product build with test enabled before you add new features or changes.
>>
>> *Publisher & Store*
>> Login with username
>> Add API / Edit API
>> Create new version of API
>> API Documentation
>> Publish API
>> Tags
>> Delete API
>> Search/
>> search Paginated APIs, search API by Type
>> Search by Tags / API Grouping
>> Resource Level Auth
>> User permissions per tiers
>> Self Sign up
>> Store - non tenant mode and tenant mode
>> Add Applications / Edit Applications
>> Delete Applications
>> Create Subscriptions - production/sandbox
>> Remove subscriptions  - production/sandbox
>> Domain Restrictions  - production/sandbox
>> Key Generation  - production/sandbox
>> Token Expiration
>> API Comments
>> Rating APIs (with multiple users)
>> Download Documentation
>> Application Level Throttling
>> Subscription Level Throttling
>> Resource Level Throttling
>> Add / Edit tiers (tiers.xml)
>> Ability to define additional tier attributes
>> IP Based throttling test mechanism
>> checking permissions of users
>>
>> *Gateway*
>> API Invocation - app token and user token
>> Invalid app token and invalid user token
>> Expired app token and expired user token
>> Uri-template based APIs
>>
>> *KeyMgt*
>> Thrift Client and WS Client
>> Gateway caching enabled
>> API Manager gateway and key manager caching enable.
>> Enable JWT Token
>> Token API - /token
>> Support for grant types of Token API-password,client credentials
>> Refresh Token
>> EnableAssertions
>> Access Token Partitioning
>> Keymanager caching enabled
>> Token types (Bearer and HMAC)
>> Encrypt access tokens & refresh tokens - Rajeev
>> Revoke Tokens
>>
>> *Samples*
>> Youtube sample
>>
>> Thanks,
>> Sanjeewa.
>>
>>
>> On Mon, Feb 17, 2014 at 11:24 PM, Madhuka Udantha wrote:
>>
>>> Hi,
>>>
>>> In AM we have considerable js and jaggery coding and all above test can
>>> cover HostObject (java) and jaggery REST api only. So I think having js or
>>> jaggery code test (unit level test and integration level) will improve
>>> $subject.
>>>
>>>
>>>
>>> On Mon, Feb 17, 2014 at 5:42 PM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi All,
 Here is the latest update on test automation of API manager integration
 tests. Last week i was mainly focused on  API store and publisher
 operations(operations exposed to out side by hostobject classes). For that
 we need to add sample jaggery application and invoke all possible
 operations for API store and publisher host objects. Then we can get single
 response for all operations available and fetch the results according to
 method order. After that we need to validate response against method. With
 these tests line coverage reached* 55%* and method and class coverage
 reached to *70%* and *73%*. I will add some more tests to cover other
 remaining edge cases.  Still there are some issues and we need to address
 them as well.

 01. Integrating with BAM and BPS to cover stats and workflow
 scenarios(we have considerable amount of code to cover usage metering
 related stuff).
 02. Need to add some more negative test cases to cover exception
 classes and exception code blocks.
 03. Need to add test case to cover external API store scenario.

 WDYT?

 Thanks,
 sanjeewa.


 On Mon, Jan 27, 2014 at 8:48 PM, Sanjeewa Malalgoda 
 wrote:

> Hi All,
> After adding tests to cover comment, rating, token generation and host
> object functionalities i was able to reach 37% line coverage and 52% 
> method
> coverage. At this point we have covered most of the common API management
> related use cases. Now we need to pay attention to workflow integration,
> usage publishing,  token partition and some other edge cases. Also we 
> might
> need to add test cases to cover negative test cases to cover exception
> classes as well. I found that auto generated thrift code is having large
> number of lines and some of them never get executed. Shall we filter out
> them? Any suggestions or ide

Re: [Dev] [API-M] Error when running a load test against /token API

[Nirodha Pramod]

Hi,

If it is a configuration issue then it should occur for a single request as
well. But this happens only for a moderate load test. Can be an issue when
fronted with ELB.

/Nirodha




On Wed, Dec 18, 2013 at 1:19 AM, Ishara Karunarathna wrote:

> Hi Nirodha,
>
> I ran this test directly pointing Key managers and gateways. Run without
> any issues.
> It only comes only when pointing to ELB.
> Then it can be a issue in ELB configurations.
>
> Please check it.
> Thanks,
> Ishara
>
>
> On Tue, Dec 17, 2013 at 6:44 PM, Nirodha Pramod  wrote:
>
>> This issue occurs when trying to insert this invalid value
>> "PRODUCTIONGRANT_TYPE=PASSWORD" in to "TOKEN_SCOPE" column in the
>> "IDN_OAUTH2_ACCESS_TOKEN" table.
>>
>>
>> On Tue, Dec 17, 2013 at 5:55 PM, Nirodha Pramod  wrote:
>>
>>> Hi,
>>>
>>> Get the below exception in KM nodes frequently while running a load test
>>> with about 50 threads against the token API, and the request fails. Please
>>> have a look.
>>>
>>> [1] https://wso2.org/jira/browse/APIMANAGER-1927
>>>
>>> regards,
>>> Nirodha
>>>
>>> --
>>>
>>> *Nirodha Gallage*
>>> Senior Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>
>>
>>
>> --
>>
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Ishara Karunarathna
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> email: isha...@wso2.com,   blog: isharaaruna.blogspot.com,   mobile: +94
> 718211678
>



-- 

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

Re: [Dev] [API-M] Error when running a load test against /token API

[Nirodha Pramod]

This issue occurs when trying to insert this invalid value
"PRODUCTIONGRANT_TYPE=PASSWORD" in to "TOKEN_SCOPE" column in the
"IDN_OAUTH2_ACCESS_TOKEN" table.


On Tue, Dec 17, 2013 at 5:55 PM, Nirodha Pramod  wrote:

> Hi,
>
> Get the below exception in KM nodes frequently while running a load test
> with about 50 threads against the token API, and the request fails. Please
> have a look.
>
> [1] https://wso2.org/jira/browse/APIMANAGER-1927
>
> regards,
> Nirodha
>
> --
>
> *Nirodha Gallage*
> Senior Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>



-- 

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

Re: [Dev] Is the P2 repo ready for test with chunk 6 products??

[Nirodha Pramod]

Can we get the subject please?


On Mon, Dec 16, 2013 at 7:41 AM, Nirodha Pramod  wrote:

> Hi,
>
> Do we have the $subject. This is need to test API-M with IS. Please
> provide the relevant p2 repo location.
>
> regards,
> Nirodha
>
> --
>
> *Nirodha Gallage*
> Senior Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>



-- 

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

[Dev] [API-M] Error when running a load test against /token API

[Nirodha Pramod]

Hi,

Get the below exception in KM nodes frequently while running a load test
with about 50 threads against the token API, and the request fails. Please
have a look.

[1] https://wso2.org/jira/browse/APIMANAGER-1927

regards,
Nirodha

-- 

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

[Dev] Is the P2 repo ready for test with chunk 6 products??

[Nirodha Pramod]

Hi,

Do we have the $subject. This is need to test API-M with IS. Please provide
the relevant p2 repo location.

regards,
Nirodha

-- 

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

Re: [Dev] API Manager-1.6.0 nightly build pack - 12/12/2013

[Nirodha Pramod]

Hi Dinusha,

Still the WSClient issue is not fixed in this pack. Please have a look.

https://wso2.org/jira/browse/APIMANAGER-1871

regards,
Nirodha


On Thu, Dec 12, 2013 at 9:06 PM, Dinusha Senanayaka wrote:

> Hi All,
>
> Please find the $subject in [1].
>
> [1]. http://builder1.us1.wso2.org/~apim/12-12-2013/
>
>
> Regards,
> Dinusha.
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> 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
>
>


-- 

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

Re: [Dev] [WSO2 SS - RSS]Username length restricted to 7 characters

[Nirodha Pramod]

Hi Thayalan,

AFAIR this is due to a limitation in some DBMSs. When you give database
name it appends another string based on your tenant name to make it a
unique one in the common DBMS. That full name is usually a lengthy one and
some DBMSs like oracle doesnt support having lengthy names for Database
name.

Nirodha


On Wed, Dec 4, 2013 at 5:19 PM, Thayalan  wrote:

> Hi,
>
> Is there any particular reason to restrict the username length to 7
> characters in RSS Database User creation. I'm getting the following
> exception when trying to create a username with the length more than 7
> characters.
>
> *Value in the username field entered exceeds the maximum permitted length
> of 7*
>
> --
> 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.*
>
>


-- 

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

Re: [Dev] BAM Server Profile UI doesn't show the streams defined, once you save it.

[Nirodha Pramod]

Yes, Even though those fields are marked as optional if you dont specify
them while creating the stream, then the stream wont get saved :(.  thats
a bug!


On Sun, Oct 27, 2013 at 11:40 AM, Nirmal Fernando  wrote:

> Ok, I just found the pattern. Add a stream without a nick name and
> description, you will not see it via the UI.
>
> If those are not optional, that should have been validated when I save it.
>
>
> On Sun, Oct 27, 2013 at 11:30 AM, Nirmal Fernando  wrote:
>
>> For some reason, BAM server profiles of my ESB pack seems to be busted. I
>> could see event streams configured in a new pack.
>>
>>
>> On Sat, Oct 26, 2013 at 2:18 PM, Nirmal Fernando  wrote:
>>
>>> I did. But once it is saved, though you can see the correct profile
>>> config in registry you can't see streams via UI. Plz do yourself and see.
>>> Also, BAM server profiles working so weirdly once you define multiple of
>>> them.
>>>
>>> Sent via my mobile
>>> -- Nirmal --
>>> On Oct 26, 2013 11:57 AM, "Maninda Edirisooriya" 
>>> wrote:
>>>
 You need to press Update button before click on save button according
 to documents.

 *
 Maninda Edirisooriya*
 Software Engineer
 *WSO2, Inc.
 *lean.enterprise.middleware.

 *Blog* : http://maninda.blogspot.com/
 *Phone* : +94 777603226


 On Sat, Oct 26, 2013 at 7:39 AM, Nirmal Fernando wrote:

> Please fix $subject, noticed in ESB 4.7.
>
> --
>
> 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/
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] Response body is dropped when coming through ELB

[Nirodha Pramod]

Hi,

I created and CBR proxy (with a switch mediator) in our QA setup and When I
invoke it directly from the worker nodes response comes properly back to
the client. But when  it is invoked through ELB the response body gets
dropped, only gets a 200OK response.

[1] https://wso2.org/jira/browse/ESBJAVA-2577

regards,
Nirodha

-- 
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
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

[Nirodha Pramod]

Hi Sanjeewa,

Can we have the latest ELB pack too.

thanks,
Nirodha


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
>
>  
> wso2bam-2.4.0.zip
>
>  
> wso2cep-3.0.0.zip
>
>  
> wso2esb-4.8.0.zip
>  
> wso2greg-4.6.0.zip
>
>  
> wso2ues-1.0.1.zip
>
>
>
>
> Thanks,
> sanjeewa.
> --
> *
> *
> *Sanjeewa Malalgoda*
> Senior Software Engineer
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] [API-M] Cannot login to IS as a tenant, after installing AM Key management features

[Nirodha Pramod]

Hi,

This is a blocker for using IS as Key manager in API-M distributed setup.
After installing key management features in IS you cannot log in as tenant,
get http 500 error page. Also you get invalid credentials error when the
token API endpoint is pointed to the OAuth2 web app in IS.

https://wso2.org/jira/browse/APIMANAGER-1728

regards,
Nirodha

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

Re: [Dev] [Blocker] [API-M] Message body is dropped when a custom sequence is specified in API level

[Nirodha Pramod]

Hi,

The message body get dropped initially in IN sequence. I used the default
sequences given in AM registry, which simply logs the message.

regards,
Nirodha




On Wed, Sep 25, 2013 at 6:47 AM, Nuwan Dias  wrote:

> Its a strange issue. The only difference between the global and api level
> sequences are in its name. So essentially what is being claimed here is
> that the message is being dropped when you give a different name for that
> sequence.
>
> Do you have both a global and api level sequence? Is it in the in or out
> flow? Can you share the sequences you have used? I do not see them on the
> JiRA.
>
>
>
>
> On Wed, Sep 25, 2013 at 6:43 AM, Sumedha Rubasinghe wrote:
>
>> Request or Response?
>> What have you included in custom sequence?
>>
>>
>> On Wed, Sep 25, 2013 at 6:10 AM, Nirodha Pramod  wrote:
>>
>>>
>>> Hi,
>>>
>>> Please note the $subject. This happens only when the custom sequence is
>>> specified in API level. When global sequences are specified this does not
>>> happen.
>>>
>>> https://wso2.org/jira/browse/APIMANAGER-1723
>>>
>>> regards,
>>> Nirodha
>>>
>>> --
>>> *
>>> *
>>> *Nirodha Gallage*
>>> Senior Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> Nuwan Dias
>
> Senior Software Engineer - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>



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

[Dev] [Blocker] [API-M] Message body is dropped when a custom sequence is specified in API level

[Nirodha Pramod]

Hi,

Please note the $subject. This happens only when the custom sequence is
specified in API level. When global sequences are specified this does not
happen.

https://wso2.org/jira/browse/APIMANAGER-1723

regards,
Nirodha

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

Re: [Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB

[Nirodha Pramod]

ELB 2.1.0 from sept10th build.


On Fri, Sep 13, 2013 at 3:09 PM, Nirmal Fernando  wrote:

> Geeth,
>
> Did you commit your fixes to trunk which fix this AuthenticationAdmin
> requests getting dispatched to ELB issue?
>
>
> On Fri, Sep 13, 2013 at 3:07 PM, Nuwan Dias  wrote:
>
>> What is the ELB version being used?
>>
>>
>> On Fri, Sep 13, 2013 at 3:05 PM, Nirodha Pramod  wrote:
>>
>>> Hi,
>>>
>>> Please note the $subject. This is a blocker for using a Gateway cluster
>>> fronted by ELB. Seems like the message body get distorted inside the ELB
>>> which sent to an admin service in Gateway.
>>>
>>>
>>> https://wso2.org/jira/browse/APIMANAGER-1649
>>>
>>>
>>> TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
>>> {org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
>>> dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
>>> {org.apache.synapse.mediators.builtin.LogMediator}
>>> TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
>>> {org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
>>> arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
>>> java.lang.IllegalArgumentException: wrong number of arguments
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> 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)
>>> TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
>>> {org.apache.synapse.transport.passthru.ServerWorker} - Error processing
>>> POST request for : /services/AuthenticationAdmin
>>> {org.apache.synapse.transport.passthru.ServerWorker}
>>> org.apache.axis2.AxisFault: wrong number of arguments
>>> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
>>> at
>>> org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
>>> at
>>> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at
>>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
>>> at
>>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>> 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.IllegalArgumentException: wrong number of arguments
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at
>>> org.apache.axis2.rpc.re

[Dev] [Blocker] Cannot Publish APIs to External Gateway cluster when fronted with ELB

[Nirodha Pramod]

Hi,

Please note the $subject. This is a blocker for using a Gateway cluster
fronted by ELB. Seems like the message body get distorted inside the ELB
which sent to an admin service in Gateway.


https://wso2.org/jira/browse/APIMANAGER-1649


TID: [0] [AM] [2013-09-13 12:11:44,599] INFO
{org.apache.synapse.mediators.builtin.LogMediator} - STATUS = Message
dispatched to the main sequence. Invalid URL., RESOURCE = /carbon
{org.apache.synapse.mediators.builtin.LogMediator}
TID: [0] [AM] [2013-09-13 12:28:46,751] ERROR
{org.apache.axis2.rpc.receivers.RPCMessageReceiver} - wrong number of
arguments {org.apache.axis2.rpc.receivers.RPCMessageReceiver}
java.lang.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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)
TID: [0] [AM] [2013-09-13 12:28:46,760] ERROR
{org.apache.synapse.transport.passthru.ServerWorker} - Error processing
POST request for : /services/AuthenticationAdmin
{org.apache.synapse.transport.passthru.ServerWorker}
org.apache.axis2.AxisFault: wrong number of arguments
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:211)
at
org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:404)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:184)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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.IllegalArgumentException: wrong number of arguments
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178)
at
org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
... 9 more

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

[Dev] AM features are not available in RC8(released) feature repo

[Nirodha Pramod]

Hi,

Please note the $subject. Due to this cannot test IS integration with AM
(Using IS as keymanager).

regards,
Nirodha


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

Re: [Dev] Latest packs won't start. Throws "java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put"

[Nirodha Pramod]

I
ssue was fixed with the patch given by Geeth.

regards,
Nirodha


On Wed, Aug 28, 2013 at 1:55 PM, Geeth Munasinghe  wrote:

> This issue caused multi versioned webapp with GD enabled, could not create
> a ghost file. Fix is attached in the patch.
>
> *G. K. S. Munasinghe
> *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com *
> *lean.enterprise.middleware.*
> *
> *
> email: ge...@wso2.com
> phone:(+94) 777911226
>
>
> On Wed, Aug 28, 2013 at 1:26 PM, Kasun Gajasinghe  wrote:
>
>> btw, this seems to be using the tomcat default classloader,
>> org.apache.catalina.loade.WebappClassLoader, instead of customized as
>> classloader?
>>
>>
>> On Wednesday, August 28, 2013, Evanthika Amarasiri 
>> wrote:
>> > Yes. We were able to start the server when we removed the versioned
>> webapp. This happens when GD is enabled.
>> > Evanthika
>> >
>> >
>> > On Wed, Aug 28, 2013 at 12:16 PM, Sagara Gunathunga 
>> wrote:
>> >
>> >
>> >
>> > On Wed, Aug 28, 2013 at 11:30 AM, Afkham Azeez  wrote:
>> >
>> > You are getting this on all packs or only AS? Looks like a Null
>> key/value is being stored in the Map.
>> >
>> >  This only occur when we deploy a multiversioned webapp through GD, I
>> will look into this now. BTW we should have find and fix this kind of
>> issues before this stage of the release.
>> >
>> >  Thanks !
>> >
>> >
>> > On Wed, Aug 28, 2013 at 11:14 AM, Evanthika Amarasiri <
>> evanth...@wso2.com> wrote:
>> >
>> > We deployed the RC4 packs on our setup pointing to the same svn &
>> pointing to the same database. When starting the servers, we see the below
>> exception & servers won't start. We have patched the servers with the new
>> Hazelcast jar (3.0)
>> >
>> **
>> > TID: [0] [AS] [2013-08-28 11:03:56,448]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon... {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,449]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Linux 3.2.0-29-generic, amd64
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,449]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> /home/wso2/jdk1.7.0/jre {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,449]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.7.0 {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,450]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 21.0-b17,Oracle Corporation
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,450]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> /home/wso2/4.2.0/RC4/mgr/wso2as-5.2.0
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,450]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> /home/wso2/4.2.0/RC4/mgr/wso2as-5.2.0/tmp
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,450]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> wso2, en-US, Asia/Colombo
>> {org.wso2.carbon.core.internal.CarbonCoreActivator}
>> > TID: [0] [AS] [2013-08-28 11:03:56,501]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -  The
>> default keystore (wso2carbon.jks) is currently being used. To maximize
>> security when deploying to a production environment, configure a new
>> keystore with a unique password in the production server profile.
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter}
>> > TID: [0] [AS] [2013-08-28 11:03:56,516]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>> {org.wso2.carbon.databridge.age
>>
>> --
>> ~~--~~
>> Sending this mail via my phone. Do excuse any typo or short replies
>>
>> ___
>> 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
>
>


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

Re: [Dev] Hazlecast exception thrown continuously in ELB with new version

[Nirodha Pramod]

Hi Azeez,

Found out that one node was not patched (Hazlecast 3.0 jars) properly and
have caused this issue. Sorry for the noice.

thanks,
Nirodha


On Wed, Aug 28, 2013 at 11:50 AM, Afkham Azeez  wrote:

> Are you using two different versions of Hazelcast? Looks like 2.6 & 3.0
> are used together. This won't work. All nodes in all clusters should run
> 3.0.
>
>
> On Wed, Aug 28, 2013 at 11:48 AM, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> Get the following exception continuously in ELB with the new packs and
>> with the new hazlecast 3.0 jars.
>>
>> use:java.lang.IllegalArgumentException: Packet versions are not matching!
>> This -> 1, Incoming -> 0 {com.hazelcast.nio.ReadHandler}
>> java.lang.IllegalArgumentException: Packet versions are not matching!
>> This -> 1, Incoming -> 0
>> at com.hazelcast.nio.Packet.readFrom(Packet.java:113)
>>  at
>> com.hazelcast.nio.SocketPacketReader$DefaultPacketReader.readPacket(SocketPacketReader.java:67)
>>  at com.hazelcast.nio.SocketPacketReader.read(SocketPacketReader.java:49)
>>  at com.hazelcast.nio.ReadHandler.handle(ReadHandler.java:67)
>> at
>> com.hazelcast.nio.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:33)
>>  at com.hazelcast.nio.AbstractIOSelector.run(AbstractIOSelector.java:124)
>> TID: [0] [ELB] [2013-08-28 11:16:01,948]  INFO
>> {com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
>> [as.qa.420.domain] Accepting socket connection from 
>> /192.168.18.3:39326{com.hazelcast.nio.SocketAcceptor}
>> TID: [0] [ELB] [2013-08-28 11:16:01,949]  INFO
>> {com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
>> [as.qa.420.domain] 4000 accepted socket connection from /
>> 192.168.18.3:39326 {com.hazelcast.nio.TcpIpConnectionManager}
>> TID: [0] [ELB] [2013-08-28 11:16:01,949]  INFO
>> {com.hazelcast.nio.TcpIpConnection} -  [192.168.18.1]:4000
>> [as.qa.420.domain] Connection [/192.168.18.3:39326] lost. Reason:
>> java.lang.IllegalArgumentException[Packet versions are not matching! This
>> -> 1, Incoming -> 0] {com.hazelcast.nio.TcpIpConnection}
>> TID: [0] [ELB] [2013-08-28 11:16:01,950]  WARN
>> {com.hazelcast.nio.ReadHandler} -  [192.168.18.1]:4000 [as.qa.420.domain]
>> hz.as.qa.420.domain.IO.thread-in-1 Closing socket to endpoint null,
>> Cause:java.lang.IllegalArgumentException: Packet versions are not matching!
>> This -> 1, Incoming -> 0 {com.hazelcast.nio.ReadHandler}
>> java.lang.IllegalArgumentException: Packet versions are not matching!
>> This -> 1, Incoming -> 0
>> at com.hazelcast.nio.Packet.readFrom(Packet.java:113)
>>  at
>> com.hazelcast.nio.SocketPacketReader$DefaultPacketReader.readPacket(SocketPacketReader.java:67)
>>  at com.hazelcast.nio.SocketPacketReader.read(SocketPacketReader.java:49)
>>  at com.hazelcast.nio.ReadHandler.handle(ReadHandler.java:67)
>> at
>> com.hazelcast.nio.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:33)
>>  at com.hazelcast.nio.AbstractIOSelector.run(AbstractIOSelector.java:124)
>> TID: [0] [ELB] [2013-08-28 11:17:28,843]  INFO
>> {com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
>> [as.qa.420.domain] Accepting socket connection from 
>> /192.168.18.3:45983{com.hazelcast.nio.SocketAcceptor}
>> TID: [0] [ELB] [2013-08-28 11:17:28,844]  INFO
>> {com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
>> [as.qa.420.domain] 4000 accepted socket connection from /
>> 192.168.18.3:45983 {com.hazelcast.nio.TcpIpConnectionManager}
>> TID: [0] [ELB] [2013-08-28 11:17:29,037]  INFO
>> {com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
>> [as.qa.420.domain] Accepting socket connection from 
>> /192.168.18.3:45810{com.hazelcast.nio.SocketAcceptor}
>> TID: [0] [ELB] [2013-08-28 11:17:29,038]  INFO
>> {com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
>> [as.qa.420.domain] 4000 accepted socket connection from /
>> 192.168.18.3:45810 {com.hazelcast.nio.TcpIpConnectionManager}
>> TID: [0] [ELB] [2013-08-28 11:17:29,052]  INFO
>> {com.hazelcast.nio.TcpIpConnection} -  [192.168.18.1]:4000
>> [as.qa.420.domain] Connection [/192.168.18.3:45810] lost. Reason:
>> java.lang.IllegalArgumentException[Packet versions are not matching! This
>> -> 1, Incoming -> 0] {com.hazelcast.nio.TcpIpConnection}
>> TID: [0] [ELB] [2013-08-28 11:17:29,053]  WARN
>> {com.hazelcast.nio.ReadHandler} -  [192.168.18.1]:4000 [as.qa.420.domain]
>> hz.as.qa.420.domain.IO.thread-in-0 Closing socket to endpoint null,
>> Cause:java.lang.IllegalArgumentException: Packet versions are

[Dev] Hazlecast exception thrown continuously in ELB with new version

[Nirodha Pramod]

Hi,

Get the following exception continuously in ELB with the new packs and with
the new hazlecast 3.0 jars.

use:java.lang.IllegalArgumentException: Packet versions are not matching!
This -> 1, Incoming -> 0 {com.hazelcast.nio.ReadHandler}
java.lang.IllegalArgumentException: Packet versions are not matching! This
-> 1, Incoming -> 0
at com.hazelcast.nio.Packet.readFrom(Packet.java:113)
at
com.hazelcast.nio.SocketPacketReader$DefaultPacketReader.readPacket(SocketPacketReader.java:67)
at com.hazelcast.nio.SocketPacketReader.read(SocketPacketReader.java:49)
at com.hazelcast.nio.ReadHandler.handle(ReadHandler.java:67)
at
com.hazelcast.nio.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:33)
at com.hazelcast.nio.AbstractIOSelector.run(AbstractIOSelector.java:124)
TID: [0] [ELB] [2013-08-28 11:16:01,948]  INFO
{com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
[as.qa.420.domain] Accepting socket connection from
/192.168.18.3:39326{com.hazelcast.nio.SocketAcceptor}
TID: [0] [ELB] [2013-08-28 11:16:01,949]  INFO
{com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
[as.qa.420.domain] 4000 accepted socket connection from
/192.168.18.3:39326{com.hazelcast.nio.TcpIpConnectionManager}
TID: [0] [ELB] [2013-08-28 11:16:01,949]  INFO
{com.hazelcast.nio.TcpIpConnection} -  [192.168.18.1]:4000
[as.qa.420.domain] Connection [/192.168.18.3:39326] lost. Reason:
java.lang.IllegalArgumentException[Packet versions are not matching! This
-> 1, Incoming -> 0] {com.hazelcast.nio.TcpIpConnection}
TID: [0] [ELB] [2013-08-28 11:16:01,950]  WARN
{com.hazelcast.nio.ReadHandler} -  [192.168.18.1]:4000 [as.qa.420.domain]
hz.as.qa.420.domain.IO.thread-in-1 Closing socket to endpoint null,
Cause:java.lang.IllegalArgumentException: Packet versions are not matching!
This -> 1, Incoming -> 0 {com.hazelcast.nio.ReadHandler}
java.lang.IllegalArgumentException: Packet versions are not matching! This
-> 1, Incoming -> 0
at com.hazelcast.nio.Packet.readFrom(Packet.java:113)
at
com.hazelcast.nio.SocketPacketReader$DefaultPacketReader.readPacket(SocketPacketReader.java:67)
at com.hazelcast.nio.SocketPacketReader.read(SocketPacketReader.java:49)
at com.hazelcast.nio.ReadHandler.handle(ReadHandler.java:67)
at
com.hazelcast.nio.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:33)
at com.hazelcast.nio.AbstractIOSelector.run(AbstractIOSelector.java:124)
TID: [0] [ELB] [2013-08-28 11:17:28,843]  INFO
{com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
[as.qa.420.domain] Accepting socket connection from
/192.168.18.3:45983{com.hazelcast.nio.SocketAcceptor}
TID: [0] [ELB] [2013-08-28 11:17:28,844]  INFO
{com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
[as.qa.420.domain] 4000 accepted socket connection from
/192.168.18.3:45983{com.hazelcast.nio.TcpIpConnectionManager}
TID: [0] [ELB] [2013-08-28 11:17:29,037]  INFO
{com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
[as.qa.420.domain] Accepting socket connection from
/192.168.18.3:45810{com.hazelcast.nio.SocketAcceptor}
TID: [0] [ELB] [2013-08-28 11:17:29,038]  INFO
{com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
[as.qa.420.domain] 4000 accepted socket connection from
/192.168.18.3:45810{com.hazelcast.nio.TcpIpConnectionManager}
TID: [0] [ELB] [2013-08-28 11:17:29,052]  INFO
{com.hazelcast.nio.TcpIpConnection} -  [192.168.18.1]:4000
[as.qa.420.domain] Connection [/192.168.18.3:45810] lost. Reason:
java.lang.IllegalArgumentException[Packet versions are not matching! This
-> 1, Incoming -> 0] {com.hazelcast.nio.TcpIpConnection}
TID: [0] [ELB] [2013-08-28 11:17:29,053]  WARN
{com.hazelcast.nio.ReadHandler} -  [192.168.18.1]:4000 [as.qa.420.domain]
hz.as.qa.420.domain.IO.thread-in-0 Closing socket to endpoint null,
Cause:java.lang.IllegalArgumentException: Packet versions are not matching!
This -> 1, Incoming -> 0 {com.hazelcast.nio.ReadHandler}
java.lang.IllegalArgumentException: Packet versions are not matching! This
-> 1, Incoming -> 0
at com.hazelcast.nio.Packet.readFrom(Packet.java:113)
at
com.hazelcast.nio.SocketPacketReader$DefaultPacketReader.readPacket(SocketPacketReader.java:67)
at com.hazelcast.nio.SocketPacketReader.read(SocketPacketReader.java:49)
at com.hazelcast.nio.ReadHandler.handle(ReadHandler.java:67)
at
com.hazelcast.nio.InSelectorImpl.handleSelectionKey(InSelectorImpl.java:33)
at com.hazelcast.nio.AbstractIOSelector.run(AbstractIOSelector.java:124)
TID: [0] [ELB] [2013-08-28 11:17:30,035]  INFO
{com.hazelcast.nio.SocketAcceptor} -  [192.168.18.1]:4000
[as.qa.420.domain] Accepting socket connection from
/192.168.18.3:33794{com.hazelcast.nio.SocketAcceptor}
TID: [0] [ELB] [2013-08-28 11:17:30,036]  INFO
{com.hazelcast.nio.TcpIpConnectionManager} -  [192.168.18.1]:4000
[as.qa.420.domain] 4000 accepted socket connection from
/192.168.18.3:33794{com.hazelcast.nio.TcpIpConnectionManager}
TID: [0] [ELB] [2013-08-28 11:17:30,037]  INFO
{com.hazelcast.nio.TcpIpConnection} -  [192.168.18.1]:4000
[as.qa.420.domain] Connection [/

[Dev] Usage of "localMemberBindPort" in clustering?

[Nirodha Pramod]

Hi,

What is the usage of this parameter? What are the deployment patterns where
we have to use this parameter. We don't use this parameter in our setup so
haven't tested it ever.

thanks,
Nirodha



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

Re: [Dev] OAuth2 'implicit' and 'Authorization code' grant types are not working in API-M

[Nirodha Pramod]

Hi Sumedha,

Used the Auth2PlayGround webapp to send requests. However as I noticed the
request message doesn't set the Content-Type header. I was following the
below blog [1]

[1]
http://charithaka.blogspot.com/2013/07/oauth-20-grant-types-with-wso2-api.html

GET
/authorize?scope=PRODUCTION&response_type=token&redirect_uri=http%3A%2F%2F10.100.1.89%3A9773%2Fplayground2.0%2Foauth2client&client_id=bYXWoC14UQNha85dRtjsAefOf6ka
HTTP/1.1
Host: 127.0.0.1:5050
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:19.0) Gecko/20100101
Firefox/19.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Referer: http://10.100.1.89:9773/playground2.0/oauth2.jsp?reset=true
Cookie: menuPanel=visible; menuPanelType=main;
requestedURI=../../carbon/admin/index.jsp;
current-breadcrumb=manage_menu%2Cwebapps_menu%2Cwebapps_list_menu%23;
MSG13771085497540.5996941729877883=true;
MSG13771086110030.2703039760546523=true
Connection: keep-alive

/Nirodha



On Fri, Aug 23, 2013 at 5:22 PM, Sumedha Rubasinghe wrote:

> What is the content type used?
> It should be application/x-www-form-urlencoded
>
> Please follow http://docs.wso2.org/wiki/display/AM140/Token+APIs . That
> will also help to verify product documentation.
>
>
>
>
> On Fri, Aug 23, 2013 at 5:20 AM, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> Please note the $subject in latest API-M packs. JIRA reported at
>> [1] https://wso2.org/jira/browse/APIMANAGER-1465
>> [2] https://wso2.org/jira/browse/APIMANAGER-1466
>>
>> regards,
>> Nirodha
>>
>>  --
>> *
>> *
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



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

[Dev] OAuth2 'implicit' and 'Authorization code' grant types are not working in API-M

[Nirodha Pramod]

Hi,

Please note the $subject in latest API-M packs. JIRA reported at
[1] https://wso2.org/jira/browse/APIMANAGER-1465
[2] https://wso2.org/jira/browse/APIMANAGER-1466

regards,
Nirodha

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

Re: [Dev] Need a latest p2repo with KeyManagement feature

[Nirodha Pramod]

Hi,

Even though AM features are there, only APP server and Governance Registry
features are listed in feature management wizard when this repo is given.

/Nirodha


On Thu, Aug 22, 2013 at 2:11 PM, Lalaji Sureshika  wrote:

> Hi Nirodha,
>
> Pradeep provided the latest p2-repo url in [1].Hope you can use its
> contained p2-repo.
>
>
> [1] http://ec2-54-224-94-128.compute-1.amazonaws.com/rc1/
>
> Thanks;
>
>
> On Thu, Aug 22, 2013 at 1:27 AM, Prabath Siriwardena wrote:
>
>> We should be having this in the builder machine. Please talk to Sameera
>> or Pradeep...
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>> On Thu, Aug 22, 2013 at 1:56 PM, Nirodha Pramod  wrote:
>>
>>> Hi,
>>>
>>> The latest p2repo at [1]  does not include KeyManagement features. When
>>> testing API-M integration with IS need to install key management feature in
>>> IS. Hence AM IS integration scenario testing is blocked due to this.
>>>
>>> regards,
>>> Nirodha
>>>
>>>
>>>
>>> --
>>> *
>>> *
>>> *Nirodha Gallage*
>>> Senior Software Engineer, QA.
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94716429078
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Prabath
>>
>> Mobile : +94 71 809 6732
>>
>> http://blog.facilelogin.com
>> http://RampartFAQ.com
>>
>
>
>
> --
> Lalaji Sureshika
> WSO2, Inc.;  http://wso2.com/
> email: lal...@wso2.com; cell: +94 71 608 6811
> blog: http://lalajisureshika.blogspot.com
>
>
>


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

[Dev] Need a latest p2repo with KeyManagement feature

[Nirodha Pramod]

Hi,

The latest p2repo at [1]  does not include KeyManagement features. When
testing API-M integration with IS need to install key management feature in
IS. Hence AM IS integration scenario testing is blocked due to this.

regards,
Nirodha



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

Re: [Dev] SSO is broken with latest IS and API-M packs

[Nirodha Pramod]

Hi Prabath,

Pack is here
http://builder3.us1.wso2.org/builds/APIM-1.5.0/20_08_13/wso2am-1.5.0.zip

regards,


On Thu, Aug 22, 2013 at 7:37 AM, Prabath Siriwardena wrote:

> Can you please give the link to get API-M pack ?
>
> Thanks & regards,
> -Prabath
>
>
> On Thu, Aug 22, 2013 at 7:20 AM, Nirodha Pramod  wrote:
>
>> Hi,
>>
>> After configuring SSO with latest API-M and IS packs, when trying to
>> access the publisher or store url, it redirects to IS but doesn't prompt a
>> login page. Instead it says  try to log in again. Followed doc [2] given
>> for previous release. Are there any config changes?
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-1714
>> [2] http://docs.wso2.org/wiki/display/AM140/Single+Sign-on+with+SAML+2.0
>>
>> regards,
>> Nirodha
>>
>> --
>> *
>> *
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>



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

[Dev] SSO is broken with latest IS and API-M packs

[Nirodha Pramod]

Hi,

After configuring SSO with latest API-M and IS packs, when trying to access
the publisher or store url, it redirects to IS but doesn't prompt a login
page. Instead it says  try to log in again. Followed doc [2] given for
previous release. Are there any config changes?

[1] https://wso2.org/jira/browse/IDENTITY-1714
[2] http://docs.wso2.org/wiki/display/AM140/Single+Sign-on+with+SAML+2.0

regards,
Nirodha

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

[Dev] Worker Manager separated setup cannot be accessed with Chrome

[Nirodha Pramod]

Hi,

This issue was reported few months back when doing ESB testing, still no
solution for this. Can we live with this issue with Chrome?

https://wso2.org/jira/browse/LB-78

/Nirodha

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

[Dev] WS-Discovery is broken in 4.2.0

[Nirodha Pramod]

Hi,

WS-Discovery is broken in Carbon 4.2.0 latest packs. Observed the below
issues with regard to service list updating.

[1] https://wso2.org/jira/browse/CARBON-14380
[2] https://wso2.org/jira/browse/CARBON-14381
[3] https://wso2.org/jira/browse/CARBON-14382
[4] https://wso2.org/jira/browse/CARBON-14386
[5] https://wso2.org/jira/browse/CARBON-14387


regards,
Nirodha


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

[Dev] [Blocker] Data Service Add output mappings UI is broken in AS

[Nirodha Pramod]

Hi,

$Subject is blocker for creating data services using the wizard.

https://wso2.org/jira/browse/WSAS-1464

regards,
Nirodha

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

[Dev] HTTPS requests get hanged on ELB side in AS cluster setup

[Nirodha Pramod]

Hi,

After requests are being served for sometime then the ELB sometimes get
hanged for https requests. Cannot exactly mention the steps to reproduce
this issue but looks like  it happens while the https requests are being
served.

https://wso2.org/jira/browse/LB-90

regards,
Nirodha

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

[Dev] Empty folder called Jaxrs_sample_02 in AS samples folder

[Nirodha Pramod]

Hi,

Observed the $subject in latest AS packs.

regards,

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

[Dev] Session times out when you click on a "Go to url" of webapp, or tryit, wsdl of a service

[Nirodha Pramod]

Hi,

Subject happens immediately after you click on wsdl, tryit links etc.

https://wso2.org/jira/browse/CARBON-14342

regards,
Nirodha



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

Re: [Dev] java.nio.channels.ClosedChannelException thrown time to time on ELB console

[Nirodha Pramod]

Hi,

This issue occurs very frequently now. When this exception occurred
then the mgt console operations become annoyingly slow. and have to restart
ELB.

regards,
Nirodha




On Thu, Aug 1, 2013 at 9:10 AM, Nirodha Pramod  wrote:

> Hi,
>
> Observed that this usually happens when working with the mgt console
> operations. Didn't occur much when doing service invocations.
>
> regards,
> Nirodha
>
>
> On Wed, Jul 31, 2013 at 11:38 AM, Evanthika Amarasiri 
> wrote:
>
>> Hi,
>>
>> We see a java.nio.channels.ClosedChannelException on the ELB node of a
>> worker manager separated setup time to time. [1]
>>
>>
>> TID: [0] [ELB] [2013-07-31 11:23:07,866]  WARN
>> {org.apache.synapse.transport.passthru.SourceHandler} -  Illegal incoming
>> connection state: REQUEST_DONE . Possibly two send backs are happening for
>> the same request {org.apache.synapse.transport.passthru.SourceHandler}
>> TID: [0] [ELB] [2013-07-31 11:23:07,866]  WARN
>> {org.apache.synapse.transport.passthru.SourceHandler} -  Trying to write
>> response body while the handler is in an inconsistent state REQUEST_DONE
>> {org.apache.synapse.transport.passthru.SourceHandler}
>> TID: [0] [ELB] [2013-07-31 11:23:07,867] ERROR
>> {org.apache.synapse.transport.passthru.SourceHandler} -  Unexpected I/O
>> error: java.nio.channels.ClosedChannelException
>> {org.apache.synapse.transport.passthru.SourceHandler}
>> java.nio.channels.ClosedChannelException
>> at
>> sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:249)
>> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:440)
>>  at
>> org.apache.http.nio.reactor.ssl.SSLIOSession.sendEncryptedData(SSLIOSession.java:331)
>> at
>> org.apache.http.nio.reactor.ssl.SSLIOSession.outboundTransport(SSLIOSession.java:411)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:150)
>> at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:181)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:346)
>> at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
>> at
>> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
>>  at
>> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
>> at java.lang.Thread.run(Thread.java:722)
>>
>> [1] - https://wso2.org/jira/browse/LB-74
>>
>> Regards,
>> Evanthika Amarasiri
>> Technical Lead - Quality Assurance
>> Management Committee - QA Technologies
>> Mobile: +94773125935
>> *
>> *
>> wso2.com Lean Enterprise Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *
> *
> *Nirodha Gallage*
> Senior Software Engineer, QA.
> WSO2 Inc.: http://wso2.com/
> Mobile: +94716429078
>



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

[Dev] File called "rolling.log" in

[Nirodha Pramod]

Hi,

There's a file called "rolling.log" in the HOME directory of every nodes in
the cluster setup, with out any content. Any idea what is it?? And why it
is in HOME directory itself? This cannot be seen in standalone packs.

$ ls -la

drwxr-xr-x 11 wso2 wso2  4096 Jul 30 16:39 .
drwxrwxr-x  3 wso2 wso2  4096 Jul 30 07:43 ..
drwxr-xr-x  3 wso2 wso2  4096 Jul 30 07:41 bin
drwxr-xr-x  3 wso2 wso2  4096 Jul 30 07:38 dbscripts
-rw-r--r--  1 wso2 wso2  3602 Jul 30 07:38 INSTALL.txt
drwxr-xr-x  5 wso2 wso2  4096 Jul 30 07:37 lib
-rw-r--r--  1 wso2 wso2 60940 Jul 30 07:37 LICENSE.txt
drwxrwxr-x  2 wso2 wso2  4096 Jul 30 16:39 log
-rw-r--r--  1 wso2 wso2 11315 Jul 30 07:38 README.txt
-rw-r--r--  1 wso2 wso2  8628 Jul 30 07:38 release-notes.html
drwxr-xr-x 12 wso2 wso2  4096 Jul 30 10:06 repository
drwxr-xr-x  3 wso2 wso2  4096 Jul 30 07:37 resources
*-rw-rw-r--  1 wso2 wso2 0 Jul 30 16:39 rolling.log*
drwxr-xr-x 28 wso2 wso2  4096 Jul 30 07:37 samples
drwxr-xr-x 37 wso2 wso2  4096 Aug  1 03:11 tmp
drwxr-xr-x  4 wso2 wso2  4096 Jul 30 07:38 webapp-mode
-rw-rw-r--  1 wso2 wso2   100 Jul 31 22:09 wso2carbon.pid


regards,
Nirodha

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

Re: [Dev] java.nio.channels.ClosedChannelException thrown time to time on ELB console

[Nirodha Pramod]

Hi,

Observed that this usually happens when working with the mgt console
operations. Didn't occur much when doing service invocations.

regards,
Nirodha


On Wed, Jul 31, 2013 at 11:38 AM, Evanthika Amarasiri wrote:

> Hi,
>
> We see a java.nio.channels.ClosedChannelException on the ELB node of a
> worker manager separated setup time to time. [1]
>
>
> TID: [0] [ELB] [2013-07-31 11:23:07,866]  WARN
> {org.apache.synapse.transport.passthru.SourceHandler} -  Illegal incoming
> connection state: REQUEST_DONE . Possibly two send backs are happening for
> the same request {org.apache.synapse.transport.passthru.SourceHandler}
> TID: [0] [ELB] [2013-07-31 11:23:07,866]  WARN
> {org.apache.synapse.transport.passthru.SourceHandler} -  Trying to write
> response body while the handler is in an inconsistent state REQUEST_DONE
> {org.apache.synapse.transport.passthru.SourceHandler}
> TID: [0] [ELB] [2013-07-31 11:23:07,867] ERROR
> {org.apache.synapse.transport.passthru.SourceHandler} -  Unexpected I/O
> error: java.nio.channels.ClosedChannelException
> {org.apache.synapse.transport.passthru.SourceHandler}
> java.nio.channels.ClosedChannelException
> at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:249)
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:440)
>  at
> org.apache.http.nio.reactor.ssl.SSLIOSession.sendEncryptedData(SSLIOSession.java:331)
> at
> org.apache.http.nio.reactor.ssl.SSLIOSession.outboundTransport(SSLIOSession.java:411)
>  at
> org.apache.http.impl.nio.reactor.AbstractIODispatch.outputReady(AbstractIODispatch.java:150)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.writable(BaseIOReactor.java:181)
>  at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:346)
> at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:320)
>  at
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:280)
> at
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
>  at
> org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
> at java.lang.Thread.run(Thread.java:722)
>
> [1] - https://wso2.org/jira/browse/LB-74
>
> Regards,
> Evanthika Amarasiri
> Technical Lead - Quality Assurance
> Management Committee - QA Technologies
> Mobile: +94773125935
> *
> *
> wso2.com Lean Enterprise Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] Jaxrs Webapps Totally Broken in latest AS

[Nirodha Pramod]

Hi,

Jaxrs services are totally broken in latest AS pack. Earlier when you click
on "Find Services" link it goes to eg:
http://192.168.4.52:9913/jaxrs_basic/services/ but now the url goes as
http://192.168.4.52:9913/jaxrs_basic/services/services . Due to this old
jaxrs services cannot be invoked. See the below JIRAs.

[1] https://wso2.org/jira/browse/WSAS-1336
[2] https://wso2.org/jira/browse/WSAS-1337
[3] https://wso2.org/jira/browse/WSAS-1338

regards,
Nirodha

-- 
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
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

[Nirodha Pramod]

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 >> > 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 :) )

>
>>>>
>>>> Just realized that I'm getting the same exception above when invoking a
>>>> service as well. Could this be a configuration issue? Note that the ELB &
>>>> App server nodes are running on different machines.
>>>>
>>>> [1]  - https://wso2.org/jira/browse/CARBON-14240
>>>>
>>>> Regards,
>>>> Evanthika
>>>>
>>>> ___
>>>> 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/
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *
>> *
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>


-- 
*
*
*Nirodha Gallage*
Senior Software Engineer, QA.
WSO2 Inc.: http://wso2.com/
Mobile: +94716429078
___
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

[Nirodha Pramod]

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 
> 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. Also 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.

>
>>
>> Just realized that I'm getting the same exception above when invoking a
>> service as well. Could this be a configuration issue? Note that the ELB &
>> App server nodes are running on different machines.
>>
>> [1]  - https://wso2.org/jira/browse/CARBON-14240
>>
>> Regards,
>> Evanthika
>>
>> ___
>> 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/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

[Dev] NPE - Error occurred while running CacheCleanupTask

[Nirodha Pramod]

Hi Azeez,

In the cluster setup we see the following NPE when Cache Cleanup Task is
running.

TID: [0] [AS] [2013-07-29 18:16:45,285] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} -  Error occurred while
running CacheCleanupTask {org.wso2.carbon.caching.impl.CacheCleanupTask}
java.lang.NullPointerException
at org.wso2.carbon.caching.impl.CacheImpl.expire(CacheImpl.java:684)
at org.wso2.carbon.caching.impl.CacheImpl.runCacheExpiry(CacheImpl.java:800)
at
org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
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)


See the below JIRA,

https://wso2.org/jira/browse/CARBON-14232

- Nirodha





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

[Dev] Cluster nodes not properly joining with the ELB

[Nirodha Pramod]

Hi,

When the WRK/MGR separated cluster is created fronted with the latest ELB
we noticed the $subject. Even though it logs that the the member joined to
the ELB but it really does not.

Issue reported at [1]
[1] https://wso2.org/jira/browse/CARBON-14238

-Nirodha


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

Re: [Dev] Registry caching issue observed while ELB startup..

[Nirodha Pramod]

Hi Sameera,

We used the configuration you sent for configuring the ELB and configured
AS according to previous release's docs.
But when we try to access the management console(Mgr node) it always
timeouts. And on the ELB we see the same error again. Cannot access the
management console.


TID: [0] [ELB] [2013-07-26 20:19:13,098]  WARN
{org.apache.synapse.transport.passthru.SourceHandler} -  Connection time
out after request is read: http-incoming-1
{org.apache.synapse.transport.passthru.SourceHandler}
TID: [0] [ELB] [2013-07-26 20:19:13,293] ERROR
{org.apache.axis2.transport.base.threads.NativeWorkerPool} -  Uncaught
exception {org.apache.axis2.transport.base.threads.NativeWorkerPool}
java.lang.NullPointerException: Tenant domain has not been set in
CarbonContext
at
org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79)
at
org.wso2.carbon.security.pox.POXSecurityHandler.getPOXCache(POXSecurityHandler.java:309)
at
org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:123)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:337)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:169)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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)
TID: [0] [ELB] [2013-07-26 20:20:13,361]  WARN
{org.apache.synapse.transport.passthru.SourceHandler} -  Connection time
out after request is read: http-incoming-2
{org.apache.synapse.transport.passthru.SourceHandler}



On Fri, Jul 26, 2013 at 7:21 PM, Evanthika Amarasiri wrote:

> I'm still seeing this issue with the latest ELB packs.
>
> [1] - https://wso2.org/jira/browse/CARBON-14230
>
> Regards,
> Evanthika
>
>
> On Thu, Jul 25, 2013 at 3:38 PM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> Thanks, will look in to this..
>>
>>
>> On Thu, Jul 25, 2013 at 2:58 PM, Ajith Vitharana  wrote:
>>
>>> AFAIK , The code accessing the registry should set the domain/id.
>>>
>>> Thanks
>>> Ajith.
>>>
>>>
>>> On Thu, Jul 25, 2013 at 2:54 PM, Senaka Fernando wrote:
>>>
 Hi all,

 Should the registry set the tenant domain in this case, or the code
 accessing the registry set the tenant domain? AFAIU, its the code accessing
 the registry which needs to ensure that this is done isn't it? In other
 words, whoever responsible for creating this thread should be doing this
 isn't it?

 Thanks,
 Senaka.


 On Thu, Jul 25, 2013 at 2:43 PM, Pradeep Fernando wrote:

> Hi Senaka/Ajith,
>
> FYI,
>
> java.lang.NullPointerException: Tenant domain has not been set in
> CarbonContext
> at
> org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79)
> at
> org.wso2.carbon.registry.core.utils.RegistryUtils.getCacheManager(RegistryUtils.java:289)
> at
> org.wso2.carbon.registry.core.utils.RegistryUtils.getResourcePathCache(RegistryUtils.java:283)
> at
> org.wso2.carbon.registry.core.caching.PathCache.getCache(PathCache.java:35)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache.getPathID(JDBCPathCache.java:298)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResourceID(JDBCResourceDAO.java:67)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.resourceExists(JDBCResourceDAO.java:151)
> at
> org.wso2.carbon.registry.core.utils.RegistryUtils.systemResourceShouldBeAdded(RegistryUtils.java:630)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:374)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:481)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:477)
> at
> org.wso2.carbo

Re: [Dev] Nodes leaving and joining back to the cluster frequently

[Nirodha Pramod]

I intended to send this to dev, was a mistake.

On Fri, Jul 26, 2013 at 6:51 PM, Afkham Azeez  wrote:

> Did you change the multicast timeout values?
>
timeout values are default in all nodes. (60s)


>
>
> On Fri, Jul 26, 2013 at 6:50 PM, Nirodha Pramod  wrote:
>
>> Hi Azeez,
>>
>> I noticed that some nodes are leaving and joining back frequently in the
>> cluster. Is this the normal behavior. See the logs below.
>>
>> TID: [0] [AS] [2013-07-26 18:22:57,499]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member left [d3793454-58db-485d-8864-9b701a067ce6]: 
>> /192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:23:55,581]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member joined [d3793454-58db-485d-8864-9b701a067ce6]: /
>> 192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:28:57,499]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member left [d3793454-58db-485d-8864-9b701a067ce6]: 
>> /192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:29:56,003]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member joined [d3793454-58db-485d-8864-9b701a067ce6]: /
>> 192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:34:58,499]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member left [d3793454-58db-485d-8864-9b701a067ce6]: 
>> /192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:35:55,420]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member joined [d3793454-58db-485d-8864-9b701a067ce6]: /
>> 192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:40:57,498]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member left [d3793454-58db-485d-8864-9b701a067ce6]: 
>> /192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> TID: [0] [AS] [2013-07-26 18:41:55,581]  INFO
>> {org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>> -  Member joined [d3793454-58db-485d-8864-9b701a067ce6]: /
>> 192.168.4.50:4000{org.wso2.carbon.core.clustering.hazelcast.multicast.MulticastBasedMembershipScheme}
>>
>>
>> /Nirodha
>>
>>
>> --
>> *
>> *
>> *Nirodha Gallage*
>> Senior Software Engineer, QA.
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94716429078
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>



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

Re: [Dev] Cluster initialization delays the server start up by almost 1 minute

[Nirodha Pramod]

Yes, I too think it's fine to for the very first node, and since that
waiting time is configurable it is ok.



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

Re: [Dev] Cluster initialization delays the server start up by almost 1 minute

[Nirodha Pramod]

Hi Azeez,

Yes this happens only in the first node of the cluster. Basically when
other nodes of the cluster are not started yet, then the first node waits
for other nodes to initialize the cluster. And as you pointed out that time
can be configured by changing,
60  in axis2.xml.

thanks,
Nirodha


On Fri, Jul 26, 2013 at 4:59 PM, Afkham Azeez  wrote:

> Here is the response I got from the Hazelcast forum. The startup delay you
> experience should be there only for the very first node in the cluster.
> Please confirm that this delay was seen only for the very first node.
>
>
> ---
>
> Yes, it's by design.
>
> MulticastTimeoutSeconds defines the time that a node should wait for a
> valid multicast response from another node running in the network before
> declaring itself as master node and creating its own cluster.
>
> This applies to only the first node, other nodes should get a reply from
> the first in a short time and join to it.
>
> @mmdogan
>
>
>
> On Fri, Jul 26, 2013 at 12:25 PM, Afkham Azeez  wrote:
>
>> Hi,
>>
>>
>> I set the multicast timeout using the following method;
>>
>> MulticastConfig#setMulticastTimeoutSeconds
>>
>> Then I create a Hazelcast instance as follows:
>> Hazelcast.newHazelcastInstance(primaryHazelcastConfig)
>>
>>
>> I noticed that the time it takes for the new Hazelcast instance creation
>> is proportional to the time I set in the setMulticastTimeoutSeconds. For
>> example, if I set the timeout to 60s, Hazelcast instance creation takes
>> about 63s, and so on.
>>
>> Is this by design? How is the timeout related to Hazelcast instance
>> creation time?
>>
>> Thanks
>> Azeez
>>
>
>
> On Fri, Jul 26, 2013 at 2:57 PM, Afkham Azeez  wrote:
>
>> I looked into this, and narrowed the problem down to the mcast timeout
>> value. For some reason, Hazelcast instance creation increases with an
>> increased mcast timeout value. I have raised this on the Hazelcast forum.
>>
>> Azeez
>>
>>
>> On Thu, Jul 25, 2013 at 7:58 PM, Afkham Azeez  wrote:
>>
>>> This is the time it takes for Hazelcast to initialize. We will have to
>>> dig into the Hazelcast code to see why it takes so long.
>>>
>>> Suho, when you guys were using Hazelcast, did you notice such delays as
>>> well?
>>>
>>>
>>> On Thu, Jul 25, 2013 at 12:21 PM, Nirodha Pramod wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jul 25, 2013 at 12:01 PM, Nirodha Pramod wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> You can see the below logs, when multicast clustering is enabled, it
>>>>> takes around 1 minute to do the cluster initialization.
>>>>>
>>>>> [2013-07-25 11:54:50,339]  INFO
>>>>> {org.wso2.carbon.core.transports.http.HttpsTransportListener} -  HTTPS 
>>>>> port
>>>>>   : 9443
>>>>> [2013-07-25 11:54:50,339]  INFO
>>>>> {org.wso2.carbon.core.transports.http.HttpTransportListener} -  HTTP port
>>>>>  : 9763
>>>>> [2013-07-25 11:54:50,361]  INFO
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>  Cluster domain: qa.420.com
>>>>> *[2013-07-25 11:54:50,361]*  INFO
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>  Using multicast based membership management scheme
>>>>>
>>>>> *2013-07-25 11:55:53,924]*  INFO
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>  Local member: [16c42b2b-79c8-4832-a0dc-c8d331f7ea26] - Host:localhost,
>>>>> Remote Host:null, Port: 4000, HTTP:9763, HTTPS:9443, Domain:
>>>>> qa.420.com, Sub-domain:worker, Active:true
>>>>> [2013-07-25 11:55:54,050]  INFO
>>>>> {org.wso2.carbon.core.clustering.hazelcast.HazelcastClusteringAgent} -
>>>>>  Cluster initialization completed
>>>>>
>>>>>
>>>>> regards,
>>>>> Nirodha
>>>>>
>>>>> --
>>>>> *
>>>>> *
>>>>> *Nirodha Gallage*
>>>>> Senior Software Engineer, QA.
>>>>> WSO2 Inc.: http://wso2.com/
>>>>> Mobile: +94716429078
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *
>>>> *
>>>> *N