BEA-000337 - java.util.HashMap.put Received in ASAP

(Doc ID 1539072.1)

Last updated on SEPTEMBER 29, 2017

Applies to:

Oracle Communications ASAP - Version 7.0.1 to 7.0.1 [Release 7.0.0]
Information in this document applies to any platform.

Goal

In production environment using WebLogic Server 9.2, below exception was received.

<Error> <WebLogicServer> <ukaal1hh> <AdminServer> <[STANDBY] ExecuteThread: '46' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1363651643008> <BEA-000337> <[STUCK] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "668" seconds working on the request "weblogic.jndi.internal.RootNamingNode", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
                       java.util.HashMap.put(HashMap.java:423)
                       java.util.HashSet.add(HashSet.java:194)
                       weblogic.rmi.internal.dgc.DGCServerImpl.addPhantomRef(DGCServerImpl.java:136)

 
Customer has a (custom) tool working with OSM that connects with a local ASAP queue (ASAPQueue) in order to get the response from work orders. On the ASAP side, there is a bridge that gets the response on a topic and puts it into the local ASAP queue. Due to this error, messages got stuck in the topic.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms