For Billing sample we do not need those components. Its completely depend
on stats gather through usage handler and summarized from toolbox.
Thanks,
sanjeewa.
On Tue, Nov 18, 2014 at 5:54 PM, Nuwan Dias wrote:
> @Sanjeewa, how about the billing sample? Do we need those components for
> that?
>
@Sanjeewa, how about the billing sample? Do we need those components for
that?
On Tue, Nov 18, 2014 at 5:20 PM, Sanjeewa Malalgoda
wrote:
> Hi,
> For API Manager we do not require usage agent or throttling agent since we
> have our own handlers/components to handle usage metering and throttling.
Hi,
For API Manager we do not require usage agent or throttling agent since we
have our own handlers/components to handle usage metering and throttling.
So IMO we can remove those from APIM P2. And usage agent component measure
service/webapp/registry usage against tenants and in APIM we do not hav
The pack contains CC non-refactored components. Some of them are,
1. In the org.wso2.carbon.registry.eventing 4.2.1 the CC refactoring is
done. But the org.wso2.carbon.deployment.synchronizer.server.feature 4.2.2
(which is the latest) [1] ships org.wso2.carbon.registry.eventing 4.2.0
which is not
This issue exists in DSS 3.2.2 pack as well.
https://wso2.org/jira/browse/DS-993
On Tue, Nov 18, 2014 at 11:28 AM, Nuwan Dias wrote:
> APIM 1.8.0 packs all the kernel patches up to patch0009 (latest). So
> there's nothing missing in terms of kernel patches.
>
> Is this fix entirely in the kernel
APIM 1.8.0 packs all the kernel patches up to patch0009 (latest). So
there's nothing missing in terms of kernel patches.
Is this fix entirely in the kernel patches or is there anything else
required?
On Tue, Nov 18, 2014 at 11:17 AM, Evanthika Amarasiri
wrote:
> In the pack, there are patches u
In the pack, there are patches up to patch0009. If this is a bug, the fix
should be included in the next API-M pack. AM team, please note.
Regards,
Evanthika
On Tue, Nov 18, 2014 at 10:59 AM, Danushka Fernando
wrote:
> BTW just found an issue.
>
> There is a missing CC refactoring in stratos us
BTW just found an issue.
There is a missing CC refactoring in stratos usage agent component. Apply
the diff [1] to [2] and patch and try.
[1]
https://wso2.org/jira/secure/attachment/31124/org.wso2.carbon.usage.agent.diff
[2]
https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/componen
Can you check what are the kernel patches included in the pack. And also
check what are the registry feature versions packed. It should be 4.2.2 or
later IIRC.
Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Tue, Nov 18, 2014 at 10:04 AM, K
Hi Danushka,
I tested this in 1.8.0 release packs.
On Mon, Nov 17, 2014 at 8:32 PM, Danushka Fernando
wrote:
> Hi Kala,Lakshman
> Actual issue is at tenant loading time. Due to a missing CC refactoring
> sometimes flow goes through a wrong path and we can see a weird error when
> tenant loads.
Hi Kala,Lakshman
Actual issue is at tenant loading time. Due to a missing CC refactoring
sometimes flow goes through a wrong path and we can see a weird error when
tenant loads. And tenant axis configuration load fails. The null pointer
caused by that since tenant cleanup task is accessing the last
Hi Kala,
Seems like the issue is resolved in carbon 4.3.0. see the linked issue[1].
It is look like API manager carbon core version 4.2.0. that's why you get
this error.
[1] https://wso2.org/jira/browse/CARBON-14504
Thanks
On Mon, Nov 17, 2014 at 1:31 PM, Kala Weerawardana wrote:
> Hi,
>
> Cr
Hi,
Created a new tenant
Tried to log in to the publisher with it
Had to try couple of times to log in
And then after some redirecting process the tenant was able to log in to
the publisher
Tried to create an API yet the process was not done properly
Tried to log in to the Store
Could not log i
13 matches
Mail list logo
