My Oracle Support Banner

User Is Not Able To Login To OBDx Application With No Error On The Screen And Stuck Threads On Application Server (Doc ID 2437166.1)

Last updated on APRIL 22, 2019

Applies to:

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

Symptoms

User is not able to login to OBDx application with no specific error shown on screen. But Application Server shows stuck threads in thread monitoring or thread dump. This issue, when due to specific underlying cause, is observed generally when application setup is done afresh on new application server.

Thread monitoring in Weblogic Server or thread dump analysis shows below threads stuck :

"[STUCK] ExecuteThread: '39' for queue: 'weblogic.kernel.Default (self-tuning)'" #124 daemon prio=1 os_prio=0 tid=0x00007efed8859800 nid=0x70b7 waiting for monitor entry [0x00007efea79bb000]
  java.lang.Thread.State: BLOCKED (on object monitor)
       at sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:543)
       - waiting to lock <0x0000000700f4df40> (a java.lang.Object)
       at sun.security.provider.NativePRNG$RandomIO.access$400(NativePRNG.java:331)
       at sun.security.provider.NativePRNG$Blocking.engineNextBytes(NativePRNG.java:268)
       at java.security.SecureRandom.nextBytes(SecureRandom.java:468)
       at com.sun.crypto.provider.AESKeyGenerator.engineGenerateKey(AESKeyGenerator.java:113)
       at javax.crypto.KeyGenerator.generateKey(KeyGenerator.java:546)
       at com.ofss.digx.infra.crypto.impl.aes.AESCryptographyProvider.generateRandomSecretKey(AESCryptographyProvider.java:144)

Changes

 

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.