My Oracle Support Banner

Managed Server Going into Warning State after Performing File Upload Transaction. (Doc ID 2692417.1)

Last updated on JULY 21, 2020

Applies to:

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

Symptoms


ACTUAL BEHAVIOR
---------------
After sometime of file upload at OBDX application, the threads start getting stuck for 'DIGX_FILEUPLOAD_STATUS_UPDATE' procedure
(synchronizes the file status with respect to host processing status) execution which in turn bringing the managed server(s) to a warning state.

Below is thread dump stack trace :

"[STUCK] ExecuteThread: '29' for queue: 'weblogic.kernel.Default (self-tuning)'" Id=141 RUNNABLE (in native)

at sun.nio.ch.FileDispatcherImpl.read0(Native Method)

at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:51)

at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:235)

at sun.nio.ch.IOUtil.read(IOUtil.java:209)

at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:394)

at oracle.net.nt.TimeoutSocketChannel.read(TimeoutSocketChannel.java:145)

at oracle.net.ns.NIOHeader.readHeaderBuffer(NIOHeader.java:83)

at oracle.net.ns.NIOPacket.readFromSocketChannel(NIOPacket.java:140)

at oracle.net.ns.NIOPacket.readFromSocketChannel(NIOPacket.java:102)

at oracle.net.ns.NIONSDataChannel.readDataFromSocketChannel(NIONSDataChannel.java:81)

at oracle.jdbc.driver.T4CMAREngineNIO.prepareForReading(T4CMAREngineNIO.java:99)

at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:535)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:486)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:253)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:613)

at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:224)

at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:57)

at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:908)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1194)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3833)

at oracle.jdbc.driver.T4CCallableStatement.executeInternal(T4CCallableStatement.java:1301)

at oracle.jdbc.driver.OraclePreparedStatement.executeLargeUpdate(OraclePreparedStatement.java:3918)

at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3898)

at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:4254)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1062)

at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:170)

at com.ofss.extsystem.business.extsystems.adapters.FCUBSFileUploadStatusSyncAdapter.processRequest(FCUBSFileUploadStatusSyncAdapter.java:73)

at com.ofss.extsystem.business.extsystems.HostAdapterManager.processRequest(HostAdapterManager.java:255)

at com.ofss.digx.extxface.fileuploads.fcore117.impl.FileUploadsHostAdapter.syncStatus(FileUploadsHostAdapter.java:382)

at com.ofss.digx.app.fileupload.service.UploadService.syncStatusWithHost(UploadService.java:1399)

at com.ofss.digx.timer.fileupload.FileStatusSyncTimer.execute(FileStatusSyncTimer.java:51)

 

EXPECTED BEHAVIOR
---------------
Status of uploaded file should be in synch with host
and managed server(s) should be in 'Ok' status.



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login with corporate user.
2. Perform File upload transaction.
3. After 20-30 mints managed server will go into the warning state.

 

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
Cause
Solution
References


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