Delay issues when EAP is deploying

Solution Verified - Updated

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.4
    • 7.0

Issue

  • We are experiencing some delay issues when EAP is deploying our portlets, when we start EAP with all deployments, it takes about 10 minutes to finish.

      "MSC service thread 1-3" prio=10 tid=0x00007fbaa565d800 nid=0x537 runnable [0x00007fba1d1d7000]
       java.lang.Thread.State: RUNNABLE
       at java.util.zip.ZipFile.getNextEntry(Native Method)
      at java.util.zip.ZipFile.access$500(ZipFile.java:56)
      at java.util.zip.ZipFile$1.nextElement(ZipFile.java:497)
      - locked <0x0000000722444298> (a java.util.jar.JarFile)
    
      "MSC service thread 1-2" prio=10 tid=0x00007fb9e8001800 nid=0x536 waiting for monitor entry [0x00007fba1d2d8000]
       java.lang.Thread.State: BLOCKED (on object monitor)
      at java.util.zip.ZipFile$1.hasMoreElements(ZipFile.java:486)
      - waiting to lock <0x0000000722444298> (a java.util.jar.JarFile)
       ...
      "MSC service thread 1-1" prio=10 tid=0x00007fbaa565c000 nid=0x535 waiting for monitor entry [0x00007fba40153000]
       java.lang.Thread.State: BLOCKED (on object monitor)
      at java.util.zip.ZipFile$1.hasMoreElements(ZipFile.java:486)
      - waiting to lock <0x0000000722444298> (a java.util.jar.JarFile)
    

Resolution

  • Apply cumulative patch (CP) 16 or later for JBoss EAP 6.4
  • Apply cumulative patch (CP) 7 or later for JBoss EAP 7.0

Root Cause

This content is not included.BZ1449932Content from issues.jboss.org is not included.JBEAP-10942

Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.