Hyperion Essbase 11.1.2.2无法从Essbase管理控制台连接到Essbase Administrator服务器

时间:2012-08-02 15:50:25

标签: oracle11g hyperion essbase

所以我是Essbase的新手 - 我安装了EPM系统 - Essbase管理服务已启动并运行但由于某些原因,我无法通过EAS控制台连接到管理服务器。我收到此错误 - "Could not connect to Administration Service <IP>"

所以我查看了日志文件-HyS9EPMServer-sysout.log

<Aug 2, 2012 9:48:43 AM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.> 
<Aug 2, 2012 9:51:00 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.224.53.85:1,465 during the configured idle timeout of 5 secs> 
<Aug 2, 2012 9:51:00 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.224.53.85:1,464 during the configured idle timeout of 5 secs> 
<Aug 2, 2012 9:51:00 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.224.53.85:1,463 during the configured idle timeout of 5 secs> 
<Aug 2, 2012 9:51:05 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.224.53.85:1,470 during the configured idle timeout of 5 secs> 
[Lcom.brio.one.common.NetAddress;@3433a24
**<Aug 2, 2012 11:05:37 AM EDT> <Error> <HTTP> <BEA-101017> <[ServletContext@37297592[app:SHAREDSERVICES module:interop path:/interop spec-version:2.5 version:11.1.2.0]] Root cause of ServletException.
java.lang.IllegalStateException: HttpSession is invalid**
    at weblogic.servlet.internal.session.SessionData.check(SessionData.java:479)
    at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:392)
    at com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:112)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    Truncated. see log file for complete stacktrace
> 
**<Aug 2, 2012 11:05:37 AM EDT> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'EPMServer0' has triggered at Aug 2, 2012 11:05:37 AM EDT. Notification details: 
WatchRuleType: Log 
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802')) 
WatchData: DATE = Aug 2, 2012 11:05:37 AM EDT SERVER = EPMServer0 MESSAGE = [ServletContext@37297592[app:SHAREDSERVICES module:interop path:/interop spec-version:2.5 version:11.1.2.0]] Root cause of ServletException.
java.lang.IllegalStateException: HttpSession is invalid**
    at weblogic.servlet.internal.session.SessionData.check(SessionData.java:479)
    at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:392)
    at com.hyperion.cas.web.action.CASCommonAction.execute(CASCommonAction.java:112)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1198)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:416)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at com.hyperion.bpm.ServletFilter.doFilter(ServletFilter.java:93)
    at com.hyperion.bpm.logon.CredentialFilter.doFilter(CredentialFilter.java:81)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at com.hyperion.bpm.ServletFilter.doFilter(ServletFilter.java:93)
    at com.hyperion.bpm.LocalizationServletFilter.doFilter(LocalizationServletFilter.java:54)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
 SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = SGT-ESSPLAN01 TXID =  CONTEXTID = 0000JZbrhSTAdL0_JxO5yf1G6Q2s0000WO TIMESTAMP = 1343919937388  
WatchAlarmType: AutomaticReset 
WatchAlarmResetPeriod: 30000 

我无法理解服务器启动和运行后的问题。我在线搜索高低,并没有找到解决这个问题的方法。

1 个答案:

答案 0 :(得分:0)

另一个原因可能是EPM安装在一个端口上的所有服务(紧凑模式),然后你必须说明管理服务的端口。在紧凑模式下,所有受管服务器都在同一端口上运行(默认为9000)。

尝试给予(假设您的服务器在localhost上): 本地主机:9000

作为连接对话框中的服务器名称