Fix “BEA-000394: Deadlock detected” for Weblogic with ADF Applications 12.2.1.2

If you try the newest version 12.2.1.2 (or maybe earlier versions too) you see, that your managed server does not restart, when

  • you have deployed your ADF application(s)
  • you try to restart the managed server with ADF
  • you use intentionally or not shared libraries in your weblogic-application.xml (see example below)
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                      xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd"
                      xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
  <listener>
    <listener-class>oracle.adf.share.weblogic.listeners.ADFApplicationLifecycleListener</listener-class>
  </listener>
  <listener>
    <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
  </listener>
  <library-ref>
    <library-name>adf.oracle.domain</library-name>
  </library-ref>
</weblogic-application>

You run into unpublished Bug 24490566: INTERMITTENT DEADLOCK IN WLS STARTUP DURING ADF-SHARE-DEPLOYED-TESTS.

But no problem, Oracle has created Patch 24490566: INTERMITTENT DEADLOCK IN WLS STARTUP DURING ADF-SHARE-DEPLOYED-TESTS for us for version 12.2.1.2.

Remember to install the patches for all of your developers too!

Remember too, if you want to install more than one patch, there can be conflicts. Please test carefully, if all of your problems are solved for all patches after adding one more patch. Maybe you have to create a merge request in Oracle My Support.

That’s it!

Advertisements

, , , , , ,

  1. #1 by atul on December 13, 2016 - 18:25

    Thanks for this post … I do so this in 12.2.1.1 WLS … will have apply PSU to go to 12.2.1.2 … and then apply that patch.
    or Will ask oracle if they can give backport of this Patch 24490566 for 12.2.1.1

    • #2 by Torsten Kleiber on December 13, 2016 - 19:46

      Both are possible, but I would prefer the first one. The newer patch set contains lot of bug fixes for WebLogic and the corresponding patch set for ADF too. I prefer to install a parallel fresh Fusion Middleware home on the same ports and the same hardware to replace the old one instead of upgrading it. My installation is completely scripted. Requesting a backport could need some time, maybe you have to escalate the SR as we did for this patch.

  2. #3 by Apoorv Jain on January 30, 2017 - 08:39

    Hi Torsten,

    I am getting this issue in my Production environment, do you think above patch(Patch 24490566) will be a help in this case?

    <Deadlock detected:
    [deadlocked thread] [ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)':
    —————————————————————————————————
    Thread '[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'' is waiting to acquire lock 'oracle.mds.core.CachedMOContent@26077320' that is held by thread '[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)''

    Stack trace:
    ————
    oracle.mds.core.CachedMOContent.setDocumentContent(CachedMOContent.java:832)
    oracle.mds.core.MOContent.clearContent(MOContent.java:264)
    oracle.mds.core.MOValueProvider.clearValue(MOValueProvider.java:325)
    oracle.mds.internal.cache.CacheNode.clear(CacheNode.java:143)
    oracle.mds.internal.cache.CacheNode.clear(CacheNode.java:178)
    oracle.mds.internal.cache.CacheNode.clear(CacheNode.java:114)
    oracle.mds.internal.cache.LayeredCache$MyCacheListener.objectInvalidated(LayeredCache.java:1749)
    oracle.mds.internal.cache.coherence.CoherenceCache$CacheMapListener.handleEvent(CoherenceCache.java:756)
    oracle.mds.internal.cache.coherence.CoherenceCache$CacheMapListener.entryDeleted(CoherenceCache.java:692)

  3. #4 by Apoorv Jain on January 30, 2017 - 10:33

    it looks the WLS version(my WLS version version=”12.2.1.0.0″) is not the same
    Verifying environment and performing prerequisite checks…
    Skip patch 24490566 from list of patches to apply: This patch is not needed.
    After skipping patches with missing components, there are no patches to apply.
    OPatch Session completed with warnings.

    Is there any other Patch for 12.2.1.0.0?

    • #5 by Torsten Kleiber on January 30, 2017 - 13:56

      Patch Search on Oracle MOS shows only patches for 12.2.1.1.0 and 12.2.1.2.0. As the bug itself is not public, I cannot say, if this problem is known for 12.2.1.0.0. So you have two options:

      1. Create a SR to analyze, if this is the same problem in 12.2.1.0.0 and if yes request a backport
      2. Install patchset 12.2.1.2 and the patch 24490566

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s