Disable throttling is the best option. In a way usage and throttling was
designed we need to run 3 servers
BAM, Manager, Service(like AS,BPS,DSS).
Managers - summarize usage data, run throttling rules update validation info
Bam - Accumulate usage data and persist into database
Service - Usage agent - Collect data and publish to bam
Throttling agent - Controls user actions based on
validation info
All these are inter related and usage and throttling agents run on services
cannot work independently.
So we have to remove those agents. I have created usage agent and
throttling agent features and removed them
from common feature some times back. So simply we can remove those 2
features from p2 pom.
Thanks.
On Sun, May 27, 2012 at 11:02 AM, Afkham Azeez <[email protected]> wrote:
> If the tenant is loaded by logging into the mgt console, everything works
> fine. So, something that is required by throttling is loaded when tenants
> are loaded. So we have two solutions.
>
> 1. Load that "something" even if the tenant is not loaded
> 2. Disable throttling by default
>
>
> On Sun, May 27, 2012 at 10:58 AM, Afkham Azeez <[email protected]> wrote:
>
>> That won't work.
>>
>>
>> On Sun, May 27, 2012 at 10:55 AM, Sanjeewa Malalgoda
>> <[email protected]>wrote:
>>
>>> In that case we have to run throttling manager, usage service, usage
>>> summery generator, Billing inside each and every product.
>>> Ideally we have to add all the features running on summerizer(Stratos
>>> manager) in to products. Correct me if understand this
>>> in a wrong way.
>>>
>>> Thanks.
>>>
>>>
>>> On Sun, May 27, 2012 at 10:41 AM, Afkham Azeez <[email protected]> wrote:
>>>
>>>> We will no longer depend on Manager & products should be able to run
>>>> with multitenancy without any other server running.
>>>>
>>>>
>>>> On Sun, May 27, 2012 at 10:25 AM, Sanjeewa Malalgoda <[email protected]
>>>> > wrote:
>>>>
>>>>> Hi,
>>>>> Throttling validation info calculated by manager and put them into
>>>>> registry and throttling agent running on services
>>>>> update its memory map from registry. Above scenario map is not updated
>>>>> properly with new tenant and there is a bug
>>>>> i will fix it. What amilaM said was correct(We must run manager
>>>>> to execute throttling rules). Tenant loading do not effect to
>>>>> throttling agent or manager.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Sat, May 26, 2012 at 11:48 PM, Afkham Azeez <[email protected]> wrote:
>>>>>
>>>>>> There is no manager running. This is the merged AppServer with a
>>>>>> tenant. getTenantCacheInfo(1) returns null. However, if the first request
>>>>>> is made after the tenant was loaded by logging in to the mgt console,
>>>>>> everything works fine.
>>>>>>
>>>>>>
>>>>>> On Sat, May 26, 2012 at 9:08 PM, Amila Maha Arachchi <[email protected]
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Azeez,
>>>>>>>
>>>>>>> On Sat, May 26, 2012 at 12:16 PM, Afkham Azeez <[email protected]>wrote:
>>>>>>>
>>>>>>>> This is happening because of a fundamental error in the Stratos
>>>>>>>> Throttling component. It is trying to access tenant information before
>>>>>>>> the
>>>>>>>> tenant is loaded. This is an L1.
>>>>>>>>
>>>>>>>
>>>>>>> Throttling component does not need tenant to be loaded to when
>>>>>>> taking throttling decisions. It takes decisions based on the results of
>>>>>>> previous throttling rules executions. I had a quick look at the code
>>>>>>> and I
>>>>>>> feel that validation info (which is used to take throttling decisions)
>>>>>>> may
>>>>>>> not be available at the time this error occurred, where the reason can
>>>>>>> be,
>>>>>>> throttling rules were not executed for this tenant (of course this is a
>>>>>>> bug).
>>>>>>>
>>>>>>> May be you created a tenant, deployed the service and restarted the
>>>>>>> server, but there was no chance for throttling rules to run during that
>>>>>>> time period (it runs periodically). Ohh... throttling rules are run
>>>>>>> only in
>>>>>>> Manager, so without manager running, there may be no throttling
>>>>>>> validation
>>>>>>> info.
>>>>>>>
>>>>>>> If above is the correct explanation, we have to gracefully handle it.
>>>>>>>
>>>>>>> I hope Manager was not running at this moment?
>>>>>>>
>>>>>>> Regards,
>>>>>>> AmilaM.
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> You can easily reproduce this by hosting a service within your
>>>>>>>> tenant in AppServer, restarting the appserver, and trying to directly
>>>>>>>> invoke the service without logging in first from the management
>>>>>>>> console.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, May 26, 2012 at 12:05 PM, Afkham Azeez <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> I have a BPEL process which invokes a service deployed on a tenant
>>>>>>>>> in AppServer. When that invocation hits the AppServer, the following
>>>>>>>>> exception occurs on the AppServer.
>>>>>>>>>
>>>>>>>>> [2012-05-26 12:02:16,475] @azeez.org [1] [Application
>>>>>>>>> Server]ERROR {org.apache.axis2.transport.http.AxisServlet} -
>>>>>>>>> java.lang.NullPointerException
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.throttling.agent.listeners.ServiceRequestListener.invoke(
>>>>>>>>> *ServiceRequestListener.java:64*)
>>>>>>>>> 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:262)
>>>>>>>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
>>>>>>>>> at
>>>>>>>>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
>>>>>>>>> at
>>>>>>>>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:205)
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
>>>>>>>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Afkham Azeez*
>>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>>>> * <http://www.apache.org/>**
>>>>>>>>> email: **[email protected]* <[email protected]>* 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*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Afkham Azeez*
>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>>> * <http://www.apache.org/>**
>>>>>>>> email: **[email protected]* <[email protected]>* 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*
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Dev mailing list
>>>>>>>> [email protected]
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Amila Maharachchi*
>>>>>>> Technical Lead
>>>>>>> Member, Management Committee - Cloud & Platform TG
>>>>>>> WSO2, Inc.; http://wso2.com
>>>>>>>
>>>>>>> Blog: http://maharachchi.blogspot.com
>>>>>>> Mobile: +94719371446
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Afkham Azeez*
>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>> * <http://www.apache.org/>**
>>>>>> email: **[email protected]* <[email protected]>* 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*
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Sanjeewa Malalgoda*
>>>>> mobile : +94 713068779
>>>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Afkham Azeez*
>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> * <http://www.apache.org/>**
>>>> email: **[email protected]* <[email protected]>* 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*
>>>>
>>>>
>>>
>>>
>>> --
>>> *Sanjeewa Malalgoda*
>>> mobile : +94 713068779
>>> <http://sanjeewamalalgoda.blogspot.com/>blog
>>> :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **[email protected]* <[email protected]>* 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*
>>
>>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * <http://www.apache.org/>**
> email: **[email protected]* <[email protected]>* 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*
>
>
--
*Sanjeewa Malalgoda*
mobile : +94 713068779
<http://sanjeewamalalgoda.blogspot.com/>blog
:http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
