My Oracle Support Banner

OBDx Login Not Possible Post Java Update (Doc ID 2749243.1)

Last updated on FEBRUARY 02, 2021

Applies to:

Oracle Banking Digital Experience - Version 18.1.0.0.0 to 20.1.0.0.0 [Release 18 to 20]
Information in this document applies to any platform.

Symptoms


When attempting to login in obdx application, user is unable to login
the following error in observed in Weblogic Admin Server logs.

ERROR
-----------------------
<Error> <WebLogicServer><[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <9083e955-7923-4d54-926f-a6ae3671a9e6-00000083> <1612263174981> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "665" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@3e90f0ea[POST /digx/failedlogin.jsp]

", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:

java.io.FileInputStream.readBytes(Native Method)

java.io.FileInputStream.read(FileInputStream.java:255)

sun.security.provider.NativePRNG$RandomIO.readFully(NativePRNG.java:424)

sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(NativePRNG.java:526)

sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:545)

sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)

sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)

java.security.SecureRandom.nextBytes(SecureRandom.java:478)

com.sun.crypto.provider.AESKeyGenerator.engineGenerateKey(AESKeyGenerator.java:113)

javax.crypto.KeyGenerator.generateKey(KeyGenerator.java:546)

com.ofss.digx.infra.crypto.impl.aes.AESCryptographyProvider.generateRandomSecretKey(AESCryptographyProvider.java:144)

com.ofss.digx.appx.servlet.listener.HttpSessionNonceListener.sessionCreated(HttpSessionNonceListener.java:61)

weblogic.servlet.internal.EventsManager.notifySessionCreatedEvent(EventsManager.java:321)

weblogic.servlet.internal.EventsManager.notifySessionLifetimeEvent(EventsManager.java:343)

weblogic.servlet.internal.session.ReplicatedSessionData.initialize(ReplicatedSessionData.java:116)

weblogic.servlet.internal.session.ReplicatedSessionContext.createReplicatedSessionData(ReplicatedSessionContext.java:313)

weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:303)

weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getNewSession(ServletRequestImpl.java:3463)

weblogic.servlet.internal.ServletRequestImpl$SessionHelper._getSessionInternal(ServletRequestImpl.java:2923)

weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSessionInternal(ServletRequestImpl.java:2883)

weblogic.servlet.internal.ServletRequestImpl$SessionHelper.getSession(ServletRequestImpl.java:2873)

weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1527)

jsp_servlet.__failedlogin._jspService(__failedlogin.java:74)

weblogic.servlet.jsp.JspBase.service(JspBase.java:35)

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

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

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

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

weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:489)

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

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

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

oracle.security.jps.ee.http.JpsAbsFilter$3.run(JpsAbsFilter.java:172)

java.security.AccessController.doPrivileged(Native Method)

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

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

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

oracle.security.jps.ee.http.JpsAbsFilter.doFilterInternal(JpsAbsFilter.java:273)

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

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

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

weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:631)

weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:287)

weblogic.servlet.internal.ForwardAction.run(ForwardAction.java:22)

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

weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)

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

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

weblogic.servlet.security.internal.FormSecurityModule.sendErrorPage(FormSecurityModule.java:472)

weblogic.servlet.security.internal.FormSecurityModule.sendError(FormSecurityModule.java:459)

weblogic.servlet.security.internal.FormSecurityModule.processJSecurityCheck(FormSecurityModule.java:273)

weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:198)

weblogic.servlet.security.internal.FormSecurityModule.checkAccess(FormSecurityModule.java:96)

weblogic.servlet.security.internal.ChainedSecurityModule.checkAccess(ChainedSecurityModule.java:69)

weblogic.servlet.security.internal.SecurityModule.isAuthorized(SecurityModule.java:731)

weblogic.servlet.security.internal.WebAppSecurity.checkAccess(

 





STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login with Admin/retail/corporate
2. login page post entering credentials will be stuck and will not login or return failure message


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are unable to login in obdx system

Changes

 JDK update jdk1.8.0_172 was performed.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.