Re: [Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
Cashed invalid request should get overwrite after the subscription or the first invocation after the subscription? first invocation fails and second invocation pass. So the should't the overwrite happened in first call? Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 On Fri, Mar 13, 2015 at 10:47 AM, Nuwan Dias wrote: > We cache the invalid access requests as well. So that someone with an > invalid token can't overload the system (much). > > Thanks, > NuwanD. > > On Fri, Mar 13, 2015 at 10:33 AM, Saneth Dharmakeerthi > wrote: > >> Hi Nuwan, >> >> With *false* it is >> working correctly. First new API invocation after re-subscription is not >> getting failed even a false invocation happens before doing the >> re-subscription. >> >> But it is strange the behaviour with >> *true*, >> because first new API invocation after re-subscription is getting >> failed when false invocation happens before doing the re-subscription and >> first API invocation after re-subscription is not getting failed when >> false invocation is not attempt before doing the re-subscription. >> >> Can't this be a issue with caching mechanism? because with or without >> cash, the first invocation after re-subscription should pass regardless of >> what has happened before the re-subscription. >> >> >> Thanks and Best Regards, >> >> Saneth Dharmakeerthi >> Senior Software Engineer >> WSO2, Inc. >> Mobile: +94772325511 >> >> On Fri, Mar 13, 2015 at 9:24 AM, Nuwan Dias wrote: >> >>> Hi Saneth, >>> >>> I think this is due to the caching of the older token. Can you please >>> try again by setting to 'false' in the >>> api-manager.xml? >>> >>> Thanks, >>> NuwanD. >>> >>> On Fri, Mar 13, 2015 at 8:51 AM, Saneth Dharmakeerthi >>> wrote: >>> [Adding: Kala and Krishantha ] Hi, I tested this issue with both 1.9.0 SNAPSHOT version and 1.8.0. Both versions I was able to recreate the isssue. I created Jira :APIMANAGER-3374 [1] for tracking purpose. Automation test case "AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase [2]" will be disable until this issue is fixed. I have updated the API-M 1.9.0 Test Plan [3] with JIRA information. [1] https://wso2.org/jira/browse/APIMANAGER-3374 [2] org.wso2.am.integration.tests.api.lifecycle.AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase.java [3] API-M 1.9.0 Test Plan Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 On Fri, Mar 6, 2015 at 10:14 AM, Saneth Dharmakeerthi >>> > wrote: > Hi, > >1. After copy and publish a new API version with the require >re-subscription option and invoke the new API version without >doing re-subscription it give an error, which is correct. >2. But after that if I do a re-subscription and invoke the new API >version again, the first new API version invocation after > re-subscription >is getting failed and getting success from 2nd invocation after >re-subscription. >3. This behaviour is not happening if I do not invoke the new API >version before doing the re-subscription. In that case, first >invocation of new API version after re-subscription is getting >succeed. > > Is there any reason for the above 2nd observation?. > > Thanks and Best Regards, > > Saneth Dharmakeerthi > Senior Software Engineer > WSO2, Inc. > Mobile: +94772325511 > >>> >>> >>> -- >>> Nuwan Dias >>> >>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> > > > -- > 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
Re: [Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
We cache the invalid access requests as well. So that someone with an invalid token can't overload the system (much). Thanks, NuwanD. On Fri, Mar 13, 2015 at 10:33 AM, Saneth Dharmakeerthi wrote: > Hi Nuwan, > > With *false* it is > working correctly. First new API invocation after re-subscription is not > getting failed even a false invocation happens before doing the > re-subscription. > > But it is strange the behaviour with > *true*, > because first new API invocation after re-subscription is getting failed > when false invocation happens before doing the re-subscription and first > API invocation after re-subscription is not getting failed when false > invocation > is not attempt before doing the re-subscription. > > Can't this be a issue with caching mechanism? because with or without > cash, the first invocation after re-subscription should pass regardless of > what has happened before the re-subscription. > > > Thanks and Best Regards, > > Saneth Dharmakeerthi > Senior Software Engineer > WSO2, Inc. > Mobile: +94772325511 > > On Fri, Mar 13, 2015 at 9:24 AM, Nuwan Dias wrote: > >> Hi Saneth, >> >> I think this is due to the caching of the older token. Can you please try >> again by setting to 'false' in the >> api-manager.xml? >> >> Thanks, >> NuwanD. >> >> On Fri, Mar 13, 2015 at 8:51 AM, Saneth Dharmakeerthi >> wrote: >> >>> [Adding: Kala and Krishantha ] >>> >>> Hi, >>> >>> I tested this issue with both 1.9.0 SNAPSHOT version and 1.8.0. Both >>> versions I was able to recreate the isssue. >>> I created Jira :APIMANAGER-3374 [1] for tracking purpose. >>> >>> Automation test case >>> "AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase [2]" will be >>> disable until this issue is fixed. >>> I have updated the API-M 1.9.0 Test Plan [3] with JIRA information. >>> >>> >>> [1] https://wso2.org/jira/browse/APIMANAGER-3374 >>> >>> [2] >>> org.wso2.am.integration.tests.api.lifecycle.AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase.java >>> [3] API-M 1.9.0 Test Plan >>> >>> Thanks and Best Regards, >>> >>> Saneth Dharmakeerthi >>> Senior Software Engineer >>> WSO2, Inc. >>> Mobile: +94772325511 >>> >>> On Fri, Mar 6, 2015 at 10:14 AM, Saneth Dharmakeerthi >>> wrote: >>> Hi, 1. After copy and publish a new API version with the require re-subscription option and invoke the new API version without doing re-subscription it give an error, which is correct. 2. But after that if I do a re-subscription and invoke the new API version again, the first new API version invocation after re-subscription is getting failed and getting success from 2nd invocation after re-subscription. 3. This behaviour is not happening if I do not invoke the new API version before doing the re-subscription. In that case, first invocation of new API version after re-subscription is getting succeed. Is there any reason for the above 2nd observation?. Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 >>> >>> >> >> >> -- >> Nuwan Dias >> >> Associate Tech Lead - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> > > -- 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
Re: [Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
Hi Nuwan, With *false* it is working correctly. First new API invocation after re-subscription is not getting failed even a false invocation happens before doing the re-subscription. But it is strange the behaviour with *true*, because first new API invocation after re-subscription is getting failed when false invocation happens before doing the re-subscription and first API invocation after re-subscription is not getting failed when false invocation is not attempt before doing the re-subscription. Can't this be a issue with caching mechanism? because with or without cash, the first invocation after re-subscription should pass regardless of what has happened before the re-subscription. Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 On Fri, Mar 13, 2015 at 9:24 AM, Nuwan Dias wrote: > Hi Saneth, > > I think this is due to the caching of the older token. Can you please try > again by setting to 'false' in the > api-manager.xml? > > Thanks, > NuwanD. > > On Fri, Mar 13, 2015 at 8:51 AM, Saneth Dharmakeerthi > wrote: > >> [Adding: Kala and Krishantha ] >> >> Hi, >> >> I tested this issue with both 1.9.0 SNAPSHOT version and 1.8.0. Both >> versions I was able to recreate the isssue. >> I created Jira :APIMANAGER-3374 [1] for tracking purpose. >> >> Automation test case >> "AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase [2]" will be >> disable until this issue is fixed. >> I have updated the API-M 1.9.0 Test Plan [3] with JIRA information. >> >> >> [1] https://wso2.org/jira/browse/APIMANAGER-3374 >> >> [2] >> org.wso2.am.integration.tests.api.lifecycle.AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase.java >> [3] API-M 1.9.0 Test Plan >> >> Thanks and Best Regards, >> >> Saneth Dharmakeerthi >> Senior Software Engineer >> WSO2, Inc. >> Mobile: +94772325511 >> >> On Fri, Mar 6, 2015 at 10:14 AM, Saneth Dharmakeerthi >> wrote: >> >>> Hi, >>> >>>1. After copy and publish a new API version with the require >>>re-subscription option and invoke the new API version without doing >>>re-subscription it give an error, which is correct. >>>2. But after that if I do a re-subscription and invoke the new API >>>version again, the first new API version invocation after re-subscription >>>is getting failed and getting success from 2nd invocation after >>>re-subscription. >>>3. This behaviour is not happening if I do not invoke the new API >>>version before doing the re-subscription. In that case, first >>>invocation of new API version after re-subscription is getting >>>succeed. >>> >>> Is there any reason for the above 2nd observation?. >>> >>> Thanks and Best Regards, >>> >>> Saneth Dharmakeerthi >>> Senior Software Engineer >>> WSO2, Inc. >>> Mobile: +94772325511 >>> >> >> > > > -- > 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
Re: [Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
Hi Saneth, I think this is due to the caching of the older token. Can you please try again by setting to 'false' in the api-manager.xml? Thanks, NuwanD. On Fri, Mar 13, 2015 at 8:51 AM, Saneth Dharmakeerthi wrote: > [Adding: Kala and Krishantha ] > > Hi, > > I tested this issue with both 1.9.0 SNAPSHOT version and 1.8.0. Both > versions I was able to recreate the isssue. > I created Jira :APIMANAGER-3374 [1] for tracking purpose. > > Automation test case > "AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase [2]" will be > disable until this issue is fixed. > I have updated the API-M 1.9.0 Test Plan [3] with JIRA information. > > > [1] https://wso2.org/jira/browse/APIMANAGER-3374 > > [2] > org.wso2.am.integration.tests.api.lifecycle.AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase.java > [3] API-M 1.9.0 Test Plan > > Thanks and Best Regards, > > Saneth Dharmakeerthi > Senior Software Engineer > WSO2, Inc. > Mobile: +94772325511 > > On Fri, Mar 6, 2015 at 10:14 AM, Saneth Dharmakeerthi > wrote: > >> Hi, >> >>1. After copy and publish a new API version with the require >>re-subscription option and invoke the new API version without doing >>re-subscription it give an error, which is correct. >>2. But after that if I do a re-subscription and invoke the new API >>version again, the first new API version invocation after re-subscription >>is getting failed and getting success from 2nd invocation after >>re-subscription. >>3. This behaviour is not happening if I do not invoke the new API >>version before doing the re-subscription. In that case, first >>invocation of new API version after re-subscription is getting >>succeed. >> >> Is there any reason for the above 2nd observation?. >> >> Thanks and Best Regards, >> >> Saneth Dharmakeerthi >> Senior Software Engineer >> WSO2, Inc. >> Mobile: +94772325511 >> > > -- 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
Re: [Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
[Adding: Kala and Krishantha ] Hi, I tested this issue with both 1.9.0 SNAPSHOT version and 1.8.0. Both versions I was able to recreate the isssue. I created Jira :APIMANAGER-3374 [1] for tracking purpose. Automation test case "AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase [2]" will be disable until this issue is fixed. I have updated the API-M 1.9.0 Test Plan [3] with JIRA information. [1] https://wso2.org/jira/browse/APIMANAGER-3374 [2] org.wso2.am.integration.tests.api.lifecycle.AccessibilityOfOldAPIAndCopyAPIWithReSubscriptionTestCase.java [3] API-M 1.9.0 Test Plan Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 On Fri, Mar 6, 2015 at 10:14 AM, Saneth Dharmakeerthi wrote: > Hi, > >1. After copy and publish a new API version with the require >re-subscription option and invoke the new API version without doing >re-subscription it give an error, which is correct. >2. But after that if I do a re-subscription and invoke the new API >version again, the first new API version invocation after re-subscription >is getting failed and getting success from 2nd invocation after >re-subscription. >3. This behaviour is not happening if I do not invoke the new API >version before doing the re-subscription. In that case, first >invocation of new API version after re-subscription is getting succeed. > > Is there any reason for the above 2nd observation?. > > Thanks and Best Regards, > > Saneth Dharmakeerthi > Senior Software Engineer > WSO2, Inc. > Mobile: +94772325511 > ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [APIM] First API invocation failed after re-subscription when a false invocation done before the re-subscription
Hi, 1. After copy and publish a new API version with the require re-subscription option and invoke the new API version without doing re-subscription it give an error, which is correct. 2. But after that if I do a re-subscription and invoke the new API version again, the first new API version invocation after re-subscription is getting failed and getting success from 2nd invocation after re-subscription. 3. This behaviour is not happening if I do not invoke the new API version before doing the re-subscription. In that case, first invocation of new API version after re-subscription is getting succeed. Is there any reason for the above 2nd observation?. Thanks and Best Regards, Saneth Dharmakeerthi Senior Software Engineer WSO2, Inc. Mobile: +94772325511 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
