Big Data Form crashing Planning

JanGLi

Hi,

Is it possible that very large data form can crash the planning managed server?

This is last entry of planning0.log  what i have found :

"

####<Aug 24, 2016 2:59:32 PM PKT> <Error> <WebLogicServer> <testhyperion.fatima-group.com> <Planning0> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1472032772492> <BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "711" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 711398 ms

[

POST /HyperionPlanning/servlet/HspEnterDataHelper?Action=clearAdhocSess&Application=HypUAT1 HTTP/1.1

Accept: */*

Referer: http://10.0.1.199:19000/workspace/index.jsp?framed=true

Accept-Language: en-US

Content-Type: text/plain;charset=UTF-8

Accept-Encoding: gzip, deflate

User-Agent: Mozilla/5.0 (Windows NT 10.0; Trident/7.0; Touch; rv:11.0) like Gecko

Content-Length: 9

Pragma: no-cache

Cookie: ORA_HP_HspRedirectString=%2fHyperionPlanning%2fslickgrid%2fSlickGrid.jsp%3fApplication%3dHypCRP1%26RND%3d0.3549482733485685%26Application%3dHypCRP1; ORA_HP_MRUApplication=HypUAT1; ORA_HP_MRUUsername=hakim; JSESSIONID=hTxQX9jQLQnrdPHXffh4KcdQfymBjvyQYygGcnfs7Xv3v1wXwlyq!-751110299; ORA_EPMWS_User=hakim; ORA_EPMWS_Locale=en_US; ORA_EPMWS_AccessibilityMode=false; ORA_EPMWS_ThemeSelection=Skyros; ORA_EPMWS_timeZone=-300

Via: 1.1 it-wcg1.fatima-group.com 0A0001F4

Cache-Control: no-cache

ECID-Context: 1.005Egsg6LVpF8D05zzk3yW0002hp00000C;kXjE0ZDLIPJPj8HUkLQSdVQRGSPOiUPQiNRBnLQSqSPPoV8InGTHiKTPmKHOoHOI_SOS_IS

Connection: Keep-Alive

X-Forwarded-For: 10.0.1.244

Proxy-Client-IP: 10.0.1.244

X-WebLogic-KeepAliveSecs: 30

X-WebLogic-Force-JVMID: -751110299

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

Thread-966 "[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> {

    -- Blocked trying to get lock: [email protected][fat lock]

    com.hyperion.planning.HyperionPlanningBean.IsValid(HyperionPlanningBean.java:1159)

    HspEnterDataHelper.Handle(HspEnterDataHelper.java:47)

    HspHttpServlet.initialize(HspHttpServlet.java:38)

    HspHttpServlet.doPost(HspHttpServlet.java:32)

    javax.servlet.http.HttpServlet.service(HttpServlet.java:700)

    javax.servlet.http.HttpServlet.service(HttpServlet.java:815)

    weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:224)

    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:108)

    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:207)

    weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)

    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)

    HspValidationFilter.doFilter(HspValidationFilter.java:10)

    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)

    oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)

    oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:310)

    oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:452)

    oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)

    oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:107)

    oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)

    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)

    oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:90)

    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)

    weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:25)

    weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:55)

    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3702)

    weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)

    weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:308)

    weblogic.security.service.SecurityManager.runAs(SecurityManager.java:116)

    weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2209)

    weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2131)

    weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1457)

    weblogic.work.ExecuteThread.execute(ExecuteThread.java:250)

    weblogic.work.ExecuteThread.run(ExecuteThread.java:213)

}

> "

Regards

JohnGoodwin

It is possible a very large form can cause out of memory errors and if that is the case then the form should really be redesigned there are tips in the following support document - Hyperion Planning Data Form Design Considerations (Doc ID 779502.1)

The error you are posting is due a stuck thread which has not completed after 600 seconds, I can't say whether that caused the web application to crash.

If it starts to be a recurring issue then you can enable a crash dump for analysing, for more information have a read of Monitoring the Planning JVM in EPM Environment (Doc ID 1636657.1)

Cheers

John

_Sanjay_

Most of the Hyperion customers do not understand the multi dimensional structure. They are used to see relation database/tables and reports. They expect more than one dimension at row level. Planning is not designed to work that way. Large data form does crash planning. I would suggest to re-design the data form.

How large is the data form ? I have a form with 3000 rows and 10 columns so far It is working fine.