My Oracle Support Banner

Getting Message <BEA-320068> on "GET /nms//nms_config.jar HTTP/1.1" (Doc ID 2268768.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle Utilities Network Management System - Version to [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version to [Release 1.12 to 2.3]
Information in this document applies to any platform.


Getting intermittent corba timeouts in WebLogic Server Log:

<May 15, 2017 3:47:19 PM EDT> <Notice> <Diagnostics> <BEA-320068> <Watch 'CORBA-TimeOut' with severity 'Info' on server 'nmsadmin' has triggered at May 15, 2017 3:47:19 PM EDT. Notification details:
WatchRuleType: Log
WatchRule: (MESSAGE LIKE '%StuckThreadMaxTime%') OR (MESSAGE LIKE '%CORBA.TIMEOUT%')
WatchData: DATE = May 15, 2017 3:47:19 PM EDT SERVER = nmsadmin MESSAGE = [STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "707" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 707348 ms
GET /nms//nms_config.jar HTTP/1.1
content-type: application/x-java-archive
accept-encoding: pack200-gzip,gzip
User-Agent: JNLP/1.7.0 javaws/(<internal>) Java/1.7.0_141
UA-Java-Version: 1.7.0_141
Cache-Control: no-cache
Pragma: no-cache
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
If-Modified-Since: Wed, 05 Apr 2017 15:20:38 GMT



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

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