Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

FRM-93618 fatal error - after Critcal Patch Update 07/25 and 10/25

sigrid6 days ago

We use Oracle Forms Reports 12.2.1.19 on Windows Server 2019. The server is behind a proxy that forwards requests.
Since the critical patch update July 2025, we have been experiencing massive problems with requests via the proxy. We constantly get the error FRM-93618: fatal error reading data from runtime process. It is impossible to use the applications externally that previously worked without any problems. If you do not go through the proxy but only work within the internal network, we have no problems. The critical patch update in October 2025 did not provide a solution either.

formsapp-diagnostic.log (unfortunately in German):

[2026-01-23T09:39:59.908+01:00] [WLS_FORMS] [ERROR] [FRM-93614] [oracle.forms.servlet] [tid: 99] [userId: <anonymous>] [ecid: 00jdu1YoLUJBx0KayTR_6G0001eW000BRE,0:1] [APP: formsapp#12.2.1] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FORMS_SESSION_ID: WLS_FORMS.formsapp.69] [SRC_CLASS: oracle.forms.servlet.ListenerServlet$Request] [SRC_METHOD: forwardResponseFromRunform] Content-Länge von Runtime-Prozess ist ungültig oder fehlt
[2026-01-23T09:40:01.705+01:00] [WLS_FORMS] [ERROR] [FRM-91299] [oracle.forms.servlet] [tid: 99] [userId: <anonymous>] [ecid: 00jdu1YoLUJBx0KayTR_6G0001eW000BRE,0:1] [APP: formsapp#12.2.1] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FORMS_SESSION_ID: WLS_FORMS.formsapp.69] [SRC_CLASS: oracle.forms.servlet.RunformProcess] [SRC_METHOD: fromFrmwebToODL] Schwerwiegender Fehler in Runtime-Prozess: Verbindung zu Java-Client kann nicht hergestellt werden
[2026-01-23T09:40:01.705+01:00] [WLS_FORMS] [ERROR] [FRM-93618] [oracle.forms.servlet] [tid: 99] [userId: <anonymous>] [ecid: 00jdu1YoLUJBx0KayTR_6G0001eW000BRE,0:1] [APP: formsapp#12.2.1] [partition-name: DOMAIN] [tenant-name: GLOBAL] [FORMS_SESSION_ID: WLS_FORMS.formsapp.69] [SRC_CLASS: oracle.forms.servlet.BaseServlet] [SRC_METHOD: logConnectionException] Schwerwiegender Fehler beim Lesen von Daten aus dem Runtime-Prozess[[
java.io.IOException
at oracle.forms.servlet.ListenerServlet$Request.forwardResponseFromRunform(Unknown Source)
at oracle.forms.servlet.ListenerServlet$Request.doPost(Unknown Source)
at oracle.forms.servlet.ListenerServlet$Request.access$000(Unknown Source)
at oracle.forms.servlet.ListenerServlet.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:295)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:260)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:137)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:353)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:25)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.security.jps.ee.http.JpsAbsFilter$3.run(JpsAbsFilter.java:175)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:314)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:650)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:112)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilterInternal(JpsAbsFilter.java:293)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:150)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:94)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:248)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at oracle.jrf.servlet.ExtensibleGlobalFilter.doFilter(ExtensibleGlobalFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:78)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3800)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3766)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:344)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.servlet.provider.WlsSecurityProvider.runAsForUserCode(WlsSecurityProvider.java:203)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:71)
at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2454)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2302)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2280)
at weblogic.servlet.internal.ServletRequestImpl.runInternal(ServletRequestImpl.java:1741)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1701)
at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:274)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:655)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)

We do not use a load balancer. The proxy server uses an ngnix.

Something must have changed in the critical patch update of July 2025 that is preventing requests via the proxy from working.
What has changed, and where could the problem be?

We have checked that the form timeout settings are correct.

Are there any settings in Weblogic Server or OHS that we need to adjust?

We are grateful for every idea.

Best regards

Sigrid

Comments
Post Details
Added 6 days ago
0 comments
55 views