Hello All,
Whenever we are trying to invoke any process that uses generatePDFOutput service. We get corba time out error in the log for the first time The same works perfectly fine second time. We have increased every possible timeout in the server such as JTA, MaxStuckthread timeout etc. Still it does not gets fixed. Restarting the server helps only for sometime. After few hours we again get those issues. The environment details are given below.
AEM Forms JEE 6.5 + Weblogic 12.2.1.3.0 + Linux + MS SQL Server 2016. The errors are given below.
For generatePDFOutput
======================================
####<Apr 6, 2021 12:47:17,538 AM EDT> <Error> <com.adobe.service.ProcessResource> <rpc15032.corp.ncr.com> <AEM65> <[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1D43CE0E532C58315DF7> <cc5e9581-738e-4615-88c5-7184e8db49c4-00000400> <1617684437538> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <ALC-BMC-001-031: An unexpected CORBA exception occurred while allocating a connection by service XMLFormService
org.omg.CORBA.COMM_FAILURE: Attempt to send message on closed socket vmcid: 0x0 minor code: 0 completed: No
Caused By: java.io.EOFException: Attempt to send message on closed socket
=============================================================================
The below error while we try to render a PDF in HTML
####<Apr 6, 2021 12:50:17,595 AM EDT> <Error> <com.adobe.service.ProcessResource> <rpc15032.corp.ncr.com> <AEM65> <[ACTIVE] ExecuteThread: '28' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1D43CE0E532C58315DF7> <cc5e9581-738e-4615-88c5-7184e8db49c4-00000400> <1617684617595> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> <ALC-BMC-001-031: An unexpected CORBA exception occurred while preparing to commit by service XMLFormService
org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds. vmcid: 0x0 minor code: 0 completed: Maybe
Caused By: weblogic.rmi.extensions.RequestTimeoutException: Response timed out after: '180000' milliseconds.
Thanks,
Bibhu.
Solved! Go to Solution.
Views
Replies
Total Likes
@Bibhu_Bikash_Na Seems to be an issue with socket timeout in WebLogic.
Caused By: java.io.EOFException: Attempt to send message on closed socket
I can see a solution been shared at [0] and [1] but as we do not have access to the oracle support account, we will not be able to review it. Please check at your end once.
[0] - https://support.oracle.com/knowledge/More%20Applications%20and%20Technologies/2403086_1.html
[1] -
@Bibhu_Bikash_Na you might want to capture strace and share with support for analysis
@Bibhu_Bikash_Na Seems to be an issue with socket timeout in WebLogic.
Caused By: java.io.EOFException: Attempt to send message on closed socket
I can see a solution been shared at [0] and [1] but as we do not have access to the oracle support account, we will not be able to review it. Please check at your end once.
[0] - https://support.oracle.com/knowledge/More%20Applications%20and%20Technologies/2403086_1.html
[1] -
Views
Likes
Replies