[Dev] Looks like access token persistance stopped working with new improvements

2014-09-03 Thread Vijayaratha Vijayasingam 
 IS team;

The new perf improvement we did at Oauth component has broken the token
persistency.
In the new implementation, we save the tokens in a queue and allowing BE
task to persist tokens.
Looks like now, tokens are not persisting at all. I have waited more than
20 mins..DB is not getting updated..
You can check the behavior in AM pack[2], when you regenerate token for an
application.

[1]

  if (maxPoolSize > 0){

accessContextTokenQueue.push(new AccessContextTokenDO(
accessToken, consumerKey, accessTokenDO, userStoreDomain));

} else {

persistAccessToken(accessToken, consumerKey, accessTokenDO,
userStoreDomain);

}
[2]
https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/

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

Re: [Dev] Looks like access token persistance stopped working with new improvements

2014-09-03 Thread Prasad Tissera 
We will look into this. Thanks.

Regards,
Prasad.
On Sep 3, 2014 5:55 PM, "Vijayaratha Vijayasingam"  wrote:

>  IS team;
>
> The new perf improvement we did at Oauth component has broken the token
> persistency.
> In the new implementation, we save the tokens in a queue and allowing BE
> task to persist tokens.
> Looks like now, tokens are not persisting at all. I have waited more than
> 20 mins..DB is not getting updated..
> You can check the behavior in AM pack[2], when you regenerate token for an
> application.
>
> [1]
>
>   if (maxPoolSize > 0){
>
> accessContextTokenQueue.push(new AccessContextTokenDO(
> accessToken, consumerKey, accessTokenDO, userStoreDomain));
>
> } else {
>
> persistAccessToken(accessToken, consumerKey, accessTokenDO,
> userStoreDomain);
>
> }
> [2]
> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>
> Thanks.
> --
> -Ratha
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Looks like access token persistance stopped working with new improvements

2014-09-04 Thread Prasad Tissera 
Fixed with r206858. Please verify. Thanks.



On Wed, Sep 3, 2014 at 7:30 PM, Prasad Tissera  wrote:

> We will look into this. Thanks.
>
> Regards,
> Prasad.
> On Sep 3, 2014 5:55 PM, "Vijayaratha Vijayasingam" 
> wrote:
>
>>  IS team;
>>
>> The new perf improvement we did at Oauth component has broken the token
>> persistency.
>> In the new implementation, we save the tokens in a queue and allowing BE
>> task to persist tokens.
>> Looks like now, tokens are not persisting at all. I have waited more than
>> 20 mins..DB is not getting updated..
>> You can check the behavior in AM pack[2], when you regenerate token for
>> an application.
>>
>> [1]
>>
>>   if (maxPoolSize > 0){
>>
>> accessContextTokenQueue.push(new AccessContextTokenDO(
>> accessToken, consumerKey, accessTokenDO, userStoreDomain));
>>
>> } else {
>>
>> persistAccessToken(accessToken, consumerKey, accessTokenDO,
>> userStoreDomain);
>>
>> }
>> [2]
>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>>
>> Thanks.
>> --
>> -Ratha
>>
>


-- 
Prasad Tissera
Software Engineer.
Mobile : +94777223444
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Looks like access token persistance stopped working with new improvements

2014-09-04 Thread Vijayaratha Vijayasingam 
Thanks this works.


On 4 September 2014 13:34, Prasad Tissera  wrote:

> Fixed with r206858. Please verify. Thanks.
>
>
>
> On Wed, Sep 3, 2014 at 7:30 PM, Prasad Tissera  wrote:
>
>> We will look into this. Thanks.
>>
>> Regards,
>> Prasad.
>> On Sep 3, 2014 5:55 PM, "Vijayaratha Vijayasingam" 
>> wrote:
>>
>>>  IS team;
>>>
>>> The new perf improvement we did at Oauth component has broken the token
>>> persistency.
>>> In the new implementation, we save the tokens in a queue and allowing BE
>>> task to persist tokens.
>>> Looks like now, tokens are not persisting at all. I have waited more
>>> than 20 mins..DB is not getting updated..
>>> You can check the behavior in AM pack[2], when you regenerate token for
>>> an application.
>>>
>>> [1]
>>>
>>>   if (maxPoolSize > 0){
>>>
>>> accessContextTokenQueue.push(new AccessContextTokenDO(
>>> accessToken, consumerKey, accessTokenDO, userStoreDomain));
>>>
>>> } else {
>>>
>>> persistAccessToken(accessToken, consumerKey, accessTokenDO,
>>> userStoreDomain);
>>>
>>> }
>>> [2]
>>> https://svn.wso2.org/repos/wso2/scratch/chunk13-release/03-09-2014/
>>>
>>> Thanks.
>>> --
>>> -Ratha
>>>
>>
>
>
> --
> Prasad Tissera
> Software Engineer.
> Mobile : +94777223444
>



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