My Oracle Support Banner

Unable to upload attachments when backend OCI VNIC is changed from Paravirtualized to HW accelerated (Doc ID 2772301.1)

Last updated on JUNE 21, 2023

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
JD Edwards EnterpriseOne Tools - Version 9.1 and later
PeopleSoft Enterprise PT PeopleTools - Version 8.59 and later
EBS on Oracle Cloud: Provisioning and Administration - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Unable to upload attachments in Siebel Application on OCI. The issue has been reported for Siebel product, but it could affect many other products as well.

For Siebel CRM the issue can be reproduced at will with the following steps:

1. Open Chrome or Firefox browser and login in Siebel Application;
2. Navigate to Service Request Details applet and click on Attachment tab, this will send the user to "Service Request detail view w/attachments";
3. Click on Attachment list applet button New File;
4. Select a file with couple of MB on size and click OK;
5. After that the pop up message show up an attachment, but is not uploaded to Siebel.

The issue can be confirmed with fiddler trace output and UI.log from AI Tomcat backend.

In UI.log below events coincide with upload request: 

[INFO ] 2021-04-12 11:50:42.657 [https-openssl-nio-4433-exec-14 : 0DD4242F9B034981BFD829D8C39A6239] UI - com.siebel.swsm.handlers.UIHandler:processRequest Entered into Module : Start
[INFO ] 2021-04-12 11:50:42.657 [https-openssl-nio-4433-exec-14 : 0DD4242F9B034981BFD829D8C39A6239] UI - com.siebel.swsm.handlers.UIHandler:processRequest Exited from Module : Start
[INFO ] 2021-04-12 11:50:42.657 [https-openssl-nio-4433-exec-14 : 0DD4242F9B034981BFD829D8C39A6239] UI - com.siebel.swsm.handlers.UIHandler:processRequest Entered into Module : UIContextInitialize

Then get timeout 10 minutes later:

[DEBUG] 2021-04-12 12:00:42.669 [https-openssl-nio-4433-exec-14 : 0DD4242F9B034981BFD829D8C39A6239] UI - com.siebel.swsm.context.SWSMRequestStreamer:readNBytes Unable to process request body due to IO error : java.net.SocketTimeoutException
org.apache.catalina.connector.ClientAbortException: java.net.SocketTimeoutException
at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:340) ~[catalina.jar:9.0.37]
at org.apache.catalina.connector.InputBuffer.checkByteBufferEof(InputBuffer.java:632) ~[catalina.jar:9.0.37]
at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:362) ~[catalina.jar:9.0.37]
at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:132) ~[catalina.jar:9.0.37]
at java.io.DataInputStream.readFully(DataInputStream.java:195) ~[?:1.8.0]
at java.io.DataInputStream.readFully(DataInputStream.java:169) ~[?:1.8.0]
at com.siebel.swsm.context.SWSMRequestStreamer.readNBytes(SWSMRequestStreamer.java:283) [ai.jar:?]
at com.siebel.swsm.context.SWSMRequestStreamer.ReadFirstChunk(SWSMRequestStreamer.java:315) [ai.jar:?]
at com.siebel.swsm.context.SWSMRequestStreamer.ProcessRequestBody(SWSMRequestStreamer.java:236) [ai.jar:?]
at com.siebel.swsm.context.SWSMHttpRequestWrapper.Initialize(SWSMHttpRequestWrapper.java:253) [ai.jar:?]
at com.siebel.swsm.init.UIContextInitialize.processModule(UIContextInitialize.java:100) [ai.jar:?]
at com.siebel.swsm.handlers.UIHandler.processRequest(UIHandler.java:47) [ai.jar:?]
at com.siebel.swsm.siebelendpoints.SWSMServlet.doPost(SWSMServlet.java:26) [ai.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:652) [servlet-api.jar:4.0.FR]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:733) [servlet-api.jar:4.0.FR]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:9.0.37]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-websocket.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:9.0.37]
at org.apache.catalina.filters.HttpHeaderSecurityFilter.doFilter(HttpHeaderSecurityFilter.java:126) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:9.0.37]
at com.siebel.swsm.bootstrap.SWSMBoot.doFilterWithSessionLogs(SWSMBoot.java:111) [ai.jar:?]
at com.siebel.swsm.bootstrap.SWSMBoot.doFilter(SWSMBoot.java:99) [ai.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:9.0.37]
at org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71) [log4j-web-2.9.1.jar:2.9.1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:9.0.37]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:9.0.37]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [catalina.jar:9.0.37]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) [catalina.jar:9.0.37]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:666) [catalina.jar:9.0.37]
at org.apache.catalina.valves.rewrite.RewriteValve.invoke(RewriteValve.java:289) [catalina.jar:9.0.37]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139) [catalina.jar:9.0.37]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [catalina.jar:9.0.37]
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690) [catalina.jar:9.0.37]
at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:747) [catalina.jar:9.0.37]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) [catalina.jar:9.0.37]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) [catalina.jar:9.0.37]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373) [tomcat-coyote.jar:9.0.37]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-coyote.jar:9.0.37]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) [tomcat-coyote.jar:9.0.37]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1589) [tomcat-coyote.jar:9.0.37]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-coyote.jar:9.0.37]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-util.jar:9.0.37]
at java.lang.Thread.run(Thread.java:744) [?:1.8.0]

This thread is waiting for 10 minutes for some data from client, then it's timeout 10 minutes later due to handshake fail.

The response in fiddler trace is HTTP 504 Gateway Time-out:

Relevant Information Collection
---------------------------------------
# Result Protocol Host URL Body Caching Content-Type Process Comments Custom
189 504 HTTPS <url> /siebel/app/debug/enu?SRN=xxxx 573 text/html chrome:18164 [#146]

Request Count: 1
Bytes Sent: 10,463,396 (headers:1,328; body:10,462,068)
Bytes Received: 713 (headers:140; body:573)

ACTUAL PERFORMANCE
--------------

NOTE: This request was retried after a Send operation failed.

 

 The issue is reproduced only when using OCI Load Balancer (for example, LBaaS Shape: 400 Mbit/s) in front of AI Tomcat. If the LBaaS is bypassed, then the issue is not observed.

Changes

 Changing the OCI VNIC setting for Back End machines from Paravirtualized to HW accelerated.

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
References


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