[et_pb_section fb_built=”1″ admin_label=”section” _builder_version=”3.0.51″ custom_padding=”0px||50px|”][et_pb_row custom_padding=”0px|||” admin_label=”Row” _builder_version=”3.0.51″ background_size=”initial” background_position=”top_left” background_repeat=”repeat”][et_pb_column type=”4_4″ _builder_version=”3.0.47″ parallax=”off” parallax_method=”on”][et_pb_text admin_label=”Text” _builder_version=”3.0.106″ custom_margin=”||30px|”]<\/p>\n
For Oracle Forms 11gR2 and 12c protected by OAM using WebGate, there are known reports where users may encounter errors after being logged into the application for 60 minutes.<\/p>\n
FRM-92091: Unexpected fatal error in client-side Java code<\/p>\n
or<\/p>\n
FRM-92102: A network error or server failure has occurred<\/p>\n
[\/et_pb_text][et_pb_divider color=”#e2e2e2″ divider_position=”center” disabled_on=”on|on|off” admin_label=”Divider” _builder_version=”3.2″ custom_css_main_element=”margin-bottom:30px !important;”][\/et_pb_divider][et_pb_text admin_label=”Text” _builder_version=”3.0.51″ custom_margin=”||30px|”]<\/p>\n
\u2713<\/strong>\u00a0Which reports where users may experience errors [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row custom_padding=”40px|40px|30px|40px” background_position_1=”top_left” background_repeat_1=”no-repeat” admin_label=”Row” _builder_version=”3.0.51″ background_color=”#006bb3″][et_pb_column type=”4_4″ _builder_version=”3.0.47″ parallax=”off” parallax_method=”on” background_position=”top_left” background_repeat=”no-repeat”][et_pb_text admin_label=”Text” _builder_version=”3.0.106″ background_color=”#006bb3″ background_layout=”dark”]<\/p>\n [\/et_pb_text][et_pb_code admin_label=”Code” module_class=”white-text” _builder_version=”3.3.1″][ninja_form id=41][\/et_pb_code][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":" For Oracle Forms 11gR2 and 12c protected by OAM using WebGate, there are known reports where users may encounter errors after being logged into the application for 60 minutes. FRM-92091: Unexpected fatal error in client-side Java code or FRM-92102: A network error or server failure has occurredWhat you’ll learn in this article: \u2713\u00a0Which reports where […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"For Oracle Forms 11gR2 and 12c protected by OAM using WebGate, there are known reports where users may encounter errors after being logged into the application for 60 minutes:\r\n\r\nFRM-92091: Unexpected fatal error in client-side Java code\r\n\r\nor\r\n\r\nFRM-92102: A network error or server failure has occurred\r\n\r\nThe reason for these errors is because the \"Token Validity Period\" is being reached. This is a setting configured in the webgate agent. By default, this parameter is set to 60 minutes or 1 hour. This means that regardless if the end user has been using Forms for a full hour or if the user has left his or her Forms session idle for an hour, a timeout will occur. To solve this problem, the Token Validity Period setting in the webgate agent will need to be increased to a value (in minutes) where end users will not encounter these errors (i.e. 480 minutes (8 hours) or 540 minutes (9 hours)). You will need to determine the amount of time before this timeout occurs.\r\n\r\nNOTE: When you update the Token Validity Period for the webgate, you will need to redeploy the WebGate files generated in the $OAM_DOMAIN_HOME\/output\/<WebGateAgentName> directory into the OHS home's webgate\/conf folder as well as restart OHS.\r\n\r\nAfter making the change above, the errors should no longer occur once 60 minutes has passed.\r\n\r\nSource: Oracle Support Document ID 2178936.1<\/strong>","_et_gb_content_width":"","footnotes":""},"categories":[94,22,14],"tags":[16,89,41,25,12,23,47,46],"class_list":["post-8775","post","type-post","status-publish","format-standard","hentry","category-access-management","category-forms","category-resolve-issues","tag-11gr2","tag-12c","tag-configuration","tag-customer-support-request","tag-error","tag-forms","tag-oam","tag-ohs"],"_links":{"self":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/comments?post=8775"}],"version-history":[{"count":4,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8775\/revisions"}],"predecessor-version":[{"id":11385,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/posts\/8775\/revisions\/11385"}],"wp:attachment":[{"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/media?parent=8775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/categories?post=8775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pitss.org\/us\/wp-json\/wp\/v2\/tags?post=8775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\u2713<\/strong>\u00a0<\/span>The reason for these errors
<\/span>\u2713<\/strong>\u00a0<\/span>How to solve the errors experienced
<\/span>\u2713<\/strong>\u00a0Expected outcome<\/span><\/p>\nFill out the form below to access this blog post.<\/strong><\/h2>\n