Profile Image
mohan

OSB server was going to warning

Hi Team, My OSb server wa runnig on 12.2.1.4 and it was keep on going to warning statet due to stuck threads .

 

"[STUCK] ExecuteThread: '82' for queue: 'weblogic.kernel.Default (self-tuning)'" #233 daemon prio=1 os_prio=0 tid=0x00007fe1426b1000 nid=0x2ef6e2 runnable [0x00007fe0cd34a000]
          
               java.lang.Thread.State: RUNNABLE
          
                at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
          
                at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
          
                at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
          
                at sun.nio.ch.IOUtil.read(IOUtil.java:197)
          
                at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
          
                - locked <0x00000006847d25e0> (a java.lang.Object)
          
                at oracle.net.nt.TimeoutSocketChannel.read(TimeoutSocketChannel.java:175)
          
                at oracle.net.ns.NSProtocolNIO.doSocketRead(NSProtocolNIO.java:571)
          
                at oracle.net.ns.NIOPacket.readNIOPacket(NIOPacket.java:404)
          
                at oracle.net.ns.NSProtocolNIO.negotiateConnection(NSProtocolNIO.java:136)
          
                at oracle.net.ns.NSProtocol.connect(NSProtocol.java:356)
          
                at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1602)
          
                at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:589)
          
                at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:924)
          
                at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:58)
          
                at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:760)
          
                at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:575)
          
                at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection0(ConnectionEnvFactory.java:321)
          
                at weblogic.jdbc.common.internal.ConnectionEnvFactory.access$000(ConnectionEnvFactory.java:20)
          
                at weblogic.jdbc.common.internal.ConnectionEnvFactory$1.run(ConnectionEnvFactory.java:219)
          
                at java.security.AccessController.doPrivileged(Native Method)
          
                at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:216)
          
                at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:447)
          
                at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:2092)
          


Report URL - https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjMvMDkvMTMvMWZiZjI4ODQtMDlmNy00NjU0LWE4OWItNDVmY2VmNGM4OGUyLnR4dC0tNi0yOC00Mg==

    Profile Image

    mohan

    possible can you please post the steps to fix the issue ?.

    Please Sign In or to post your comment or answer

    Profile Image

    Mahesh

    Hello Mohan,

     

    Your thread is stuck in the "sun.nio.ch.FileDispatcherImpl.read0()" method, which is a native method responsible for reading a file or socket. This indicates that the thread is performing a socket read operation and is waiting for data to be received from the socket.

     

    There are a few possible reasons why the data might not be available:

    • Network or Socket issue. The remote server might not be responding. The thread might be waiting for data from a remote server, and there could be network issues causing the data to be delayed or not arrive at all.
    • The network connection might be congested.
    • The socket might be closed.

    Profile Image

    Ram Lakshmanan

    Hello Mohan!

     

     This sounds like a problem on the Oracle DB that your application is trying to connect. The JDBC driver running on your application is trying to establish connection on Oracle DB and it's taking long time. Can you check whether there any connection limit is reached on the Oracle DB side. Connection limits can be reached on the Oracle DB side for following reasons:

     

    a. Less number of connection has been allocated: In that circumstance you can increase the connection limit on the Oracle DB side

     

    b. Connection Leak from your application: Sometimes if your application isn't closing the connection after the usage, then connection count will build up. You might want to check whether you are closing the connections properly.

    Got something else on mind? Post Your Question