stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lasindu Charith (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (STRATOS-1048) CEP OOM error when used in Single JVM mode for several days
Date Thu, 25 Jun 2015 14:36:05 GMT

     [ https://issues.apache.org/jira/browse/STRATOS-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lasindu Charith resolved STRATOS-1048.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 4.1.0 RC3

This is a duplicate of https://issues.apache.org/jira/browse/STRATOS-1108

> CEP OOM error when used in Single JVM mode for several days
> -----------------------------------------------------------
>
>                 Key: STRATOS-1048
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1048
>             Project: Stratos
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 4.1.0, FUTURE
>            Reporter: Lasindu Charith
>             Fix For: 4.1.0 RC3
>
>         Attachments: CEP_OOM.patch
>
>
> When Stratos is running for few days in single JVM mode, it throws a 'GC overhead limit
exceeded' error due to a large number of ScheduledFutureTask objects collected in heap over
time.
> TID: [0] [STRATOS] [2014-09-07 03:43:48,708] ERROR {org.apache.stratos.cep.extension.SecondDerivativeFinderWindowProcessor}
- GC overhead limit exceeded {org.apache.stratos.cep.extension.SecondDerivativeFinderWindowProcessor}

> java.lang.OutOfMemoryError: GC overhead limit exceeded 
>         at java.util.concurrent.Executors.callable(Executors.java:369) 
>         at java.util.concurrent.FutureTask.<init>(FutureTask.java:152) 
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.<init>(ScheduledThreadPoolExecutor.java:207)

>         at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:527)

>         at org.apache.stratos.cep.extension.SecondDerivativeFinderWindowProcessor.run(SecondDerivativeFinderWindowProcessor.java:156)

>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 
>         at java.util.concurrent.FutureTask.run(FutureTask.java:262) 
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)

>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)

>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

>         at java.lang.Thread.run(Thread.java:745) 
> Attached patch for CEP window processors provides a fix for 4.0.0. siddhi-core 2.0.0-wso2v4
should have a similar fix for TimeWindowProcessor & TimeBatchWindowProcessor as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message