nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Analytics and BI Publisher hangs on sign in

3310714

Hi,

We have an intermittent issue in which Analytics and BI Publisher hangs when a user signs in. After entering the username and password, the Analytics page just shows "Signing In.." while the BI Publisher page doesn't go anywhere. The sign-in pages loads fine, but when you click "Sign In", that's when it gets stuck. I also tried intentionally entering the wrong password, and the response comes back immediately saying "Wrong Password". So I think the authentication isn't the issue. I have to bounce the BI services in Enterprise Manager to resolve this. This issue occurs intermittently, sometimes once a week, sometimes once every two weeks. This issue has happened since our clean installation of OBIEE 12c in both of our environments. We are using OBIEE 12.2.1.0.0 on AIX 7.1. My guess is it's a bug, but it's hard to troubleshoot since it doesn't happen consistently. Does anyone experience this? I have already open a ticket with Oracle, but they are taking a while....

Here's what I found in the BI logs. I don't know what it's timing out on. Why would bouncing the services resolve it?

####<Nov 16, 2016 2:30:43 PM HST> <Error> <HTTP> <obidev1> <bi_server1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <dbd3042d-d9e8-46eb-857f-e5aee9912d1c-00040767> <1479342643135> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-101017> <[ServletContext@-751668558[app:analytics module:analytics path:null spec-version:3.1]] Root cause of ServletException.

java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.socketRead(SocketInputStream.java:127)

at java.net.SocketInputStream.read(SocketInputStream.java:181)

at java.net.SocketInputStream.read(SocketInputStream.java:152)

at com.siebel.analytics.web.sawconnect.SAWConnection$NotifyInputStream.read(SAWConnection.java:165)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:257)

at java.io.BufferedInputStream.read(BufferedInputStream.java:276)

at com.siebel.analytics.web.sawconnect.sawprotocol.SAWProtocol.readInt(SAWProtocol.java:188)

at com.siebel.analytics.web.sawconnect.sawprotocol.SAWProtocolInputStreamImpl.readChunkHeader(SAWProtocolInputStreamImpl.java:282)

at com.siebel.analytics.web.sawconnect.sawprotocol.SAWProtocolInputStreamImpl.startReadingNewMessage(SAWProtocolInputStreamImpl.java:49)

at com.siebel.analytics.web.sawconnect.SAWServletHttpBinding.forwardResponse(SAWServletHttpBinding.java:215)

at com.siebel.analytics.web.SAWBridge.processRequest(SAWBridge.java:224)

at com.siebel.analytics.web.SAWBridge.doPost(SAWBridge.java:270)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)

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

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

at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)

at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:350)

at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

at com.siebel.analytics.web.integration.HyperionCSSAuthenticatorFilter.doFilter(HyperionCSSAuthenticatorFilter.java:108)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

at com.siebel.analytics.web.integration.ApplCoreSessionIntegrationFilter.doFilter(ApplCoreSessionIntegrationFilter.java:209)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

at oracle.bi.security.filter.BISecurityFilter.handleAnonymousSubject(BISecurityFilter.java:162)

at oracle.bi.security.filter.BISecurityFilter.doFilter(BISecurityFilter.java:136)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

at com.siebel.analytics.web.integration.LoadBalancerHTTPFilter.doFilter(LoadBalancerHTTPFilter.java:180)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

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

at java.security.AccessController.doPrivileged(AccessController.java:686)

at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)

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

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

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

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

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:224)

at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)

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

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

at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)

at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:196)

at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)

at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)

at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2423)

at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2280)

at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2258)

at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1626)

at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1586)

at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:270)

at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)

at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)

at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)

at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)

at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:617)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:397)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)

Find more posts tagged with

Accepted answers

All comments

Andrew Fomin.

I presume this isn't an absolutely fresh system with default settings/rpd/webcat etc. Was it ever working before? What been changed since it was working?

Federico Venturin - Oracle

Hi,

Have you already increased the Node Manager Java heap size?

https://blogs.oracle.com/pa/entry/obiee_12c_increasing_the_node

Regards

3310714

Hi Andrew,

This issue had occurred after a fresh install of OBIEE 12c. By now, we have a 1 user, 2 folders, and 2 analyses. As I mentioned, it works fine for awhile, then this issue pops up. If I reboot the BI services, it'll work fine again. We have this issue in both of our environments, shortly right after a clean install.

3310714

Hi Federico,

I haven't increase the Node Manager Java heap size. It is interesting you brought this up. What's the rationale for increasing the Node Manager Java Heap size to this issue?

Federico Venturin - Oracle

In 12c, Node Manager is monitoring not only managed servers but also BI System components. When starting all the BI processes using start.sh, Node Manager may take longer time to start, so it is recommended to increase the java heap size for Node Manager. Moreover I noticed that it usually improves login times.

3310714

OK, I will look into increasing the java heap size for Node Manager.

When we have this issue, I bounce the obips1 and obis1 and the issue is resolved, until it craps out again. Any insights on what's behind obips1 and obis1 that could stall the login issue?

asim cholas

Check all your RPD initialization blocks

User_GNQ12

We are having the exact same issue 12 c version latest one . The only difference in our case is SSO . Oracle has told us to refer to tuning guide but I feel this has nothing to do with tuning . Are you using F5 or ssl ? Or it's just http ?

3310714

Hi Asim,

We don't have any initialization blocks. As I mentioned, this issue occurs shortly after a clean installation with nothing customized.

3310714

Hi,

Yes, Oracle also told me to refer to the tuning guide. But we only have 1 user (weblogic) and the issue is happened shortly after a clean install. So there is really nothing to tune!

We are just HTTP and didn't do much customization. Mostly out of the box and we noticed this issue already. Are you using AIX and 12.2.1.2.0?