You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Prashant Punekar <Pr...@mindtree.com> on 2010/07/09 23:50:36 UTC
100% CPU usage !
Hi,
Here is the error log which takes the CPU usage to around 100%.
2010-07-09 17:17:58,551 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
2010-07-09 17:17:58,553 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
This error is thrown inside a method sessionDestroyed() of class CartEventListener.
The cause of the above error is because we have commented out the visit hits as we do not store any visit hits.
The main concern is the session gets destroyed and a new session gets created.
Can someone please throw some light on the session creation/destruction.
I have observed for the same browser window and the same request ofbiz starts new sessions which is confusing.
Appreciate your fast response.
Thanks in advance.
Regards,
Prashant
________________________________
http://www.mindtree.com/email/disclaimer.html
Re: 100% CPU usage !
Posted by Scott Gray <sc...@hotwaxmedia.com>.
On 10/07/2010, at 11:40 AM, Scott Gray wrote:
> One of the main causes I have seen for multiple sessions being created is when your html head contains html encoded hrefs within the link elements.
>
> A side effect of the security enhancements made a while back to OFBiz is that sometimes things that shouldn't be html encoded (such as urls) are being encoded automatically by OFBiz. I can remember why this causes a problem, I think the browser fails to send the session cookie with the request because of the strange url.
I meant to say: I *can't* remember why...
>
> Regards
> Scott
>
> HotWax Media
> http://www.hotwaxmedia.com
>
> On 10/07/2010, at 9:50 AM, Prashant Punekar wrote:
>
>> Hi,
>>
>> Here is the error log which takes the CPU usage to around 100%.
>>
>> 2010-07-09 17:17:58,551 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
>> 2010-07-09 17:17:58,553 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
>>
>> This error is thrown inside a method sessionDestroyed() of class CartEventListener.
>> The cause of the above error is because we have commented out the visit hits as we do not store any visit hits.
>>
>> The main concern is the session gets destroyed and a new session gets created.
>>
>> Can someone please throw some light on the session creation/destruction.
>> I have observed for the same browser window and the same request ofbiz starts new sessions which is confusing.
>>
>> Appreciate your fast response.
>>
>> Thanks in advance.
>>
>> Regards,
>> Prashant
>>
>>
>> ________________________________
>> http://www.mindtree.com/email/disclaimer.html
>
Re: 100% CPU usage !
Posted by Scott Gray <sc...@hotwaxmedia.com>.
One of the main causes I have seen for multiple sessions being created is when your html head contains html encoded hrefs within the link elements.
A side effect of the security enhancements made a while back to OFBiz is that sometimes things that shouldn't be html encoded (such as urls) are being encoded automatically by OFBiz. I can remember why this causes a problem, I think the browser fails to send the session cookie with the request because of the strange url.
Regards
Scott
HotWax Media
http://www.hotwaxmedia.com
On 10/07/2010, at 9:50 AM, Prashant Punekar wrote:
> Hi,
>
> Here is the error log which takes the CPU usage to around 100%.
>
> 2010-07-09 17:17:58,551 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
> 2010-07-09 17:17:58,553 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
>
> This error is thrown inside a method sessionDestroyed() of class CartEventListener.
> The cause of the above error is because we have commented out the visit hits as we do not store any visit hits.
>
> The main concern is the session gets destroyed and a new session gets created.
>
> Can someone please throw some light on the session creation/destruction.
> I have observed for the same browser window and the same request ofbiz starts new sessions which is confusing.
>
> Appreciate your fast response.
>
> Thanks in advance.
>
> Regards,
> Prashant
>
>
> ________________________________
> http://www.mindtree.com/email/disclaimer.html
Re: 100% CPU usage !
Posted by BJ Freeman <bj...@free-man.net>.
need more information,
Memory allocations
CPU speed
type of db
Prashant Punekar sent the following on 7/9/2010 2:50 PM:
> Hi,
>
> Here is the error log which takes the CPU usage to around 100%.
>
> 2010-07-09 17:17:58,551 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
> 2010-07-09 17:17:58,553 (ContainerBackgroundProcessor[StandardEngine[default-server]]) [ CartEventListener.java:74 :ERROR] Could not get the current visit, not saving abandoned cart info.
>
> This error is thrown inside a method sessionDestroyed() of class CartEventListener.
> The cause of the above error is because we have commented out the visit hits as we do not store any visit hits.
>
> The main concern is the session gets destroyed and a new session gets created.
>
> Can someone please throw some light on the session creation/destruction.
> I have observed for the same browser window and the same request ofbiz starts new sessions which is confusing.
>
> Appreciate your fast response.
>
> Thanks in advance.
>
> Regards,
> Prashant
>
>
> ________________________________
> http://www.mindtree.com/email/disclaimer.html
>