Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-14074

(7.2.z) OutOfMemoryError: Direct buffer memory when repeating reload

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.2.4.CR1, 7.2.4.GA
    • 7.1.0.GA, 7.2.0.GA.CR1
    • Undertow
    • None
    • Hide
      • Configure -XX:MaxDirectMemorySize=16M for server to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf
      • run server
      • Run this reproducer
        loop.sh
        #!/bin/bash
for i in {1..100}
do
  echo $i
  ${jboss.home}/bin/jboss-cli.sh -c ":reload"
  if [ $? == 1 ]
  then
      break
  fi
done
      Show
      Configure -XX:MaxDirectMemorySize=16M for server to hit error earlier . E.g. add into JAVA_OPTS of standalone.conf run server Run this reproducer loop.sh #!/bin/bash for i in {1..100} do echo $i ${jboss.home}/bin/jboss-cli.sh -c ":reload" if [ $? == 1 ] then break fi done

    Description

      Approximately on 40th reload server starts to emit OutOfMemoryError: Direct buffer memory

      19:07:12,655 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Failed to start service
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.OutOfMemoryError: Direct buffer memory
	at java.nio.Bits.reserveMemory(Bits.java:693)
	at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123)
	at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
	at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57)
	at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55)
	at org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:147)
	at io.undertow.server.XnioByteBufferPool.<init>(XnioByteBufferPool.java:40)
	at io.undertow.server.protocol.http.HttpOpenListener.<init>(HttpOpenListener.java:72)
	at org.wildfly.extension.undertow.HttpListenerService.createOpenListener(HttpListenerService.java:85)
	at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:160)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
	... 3 more

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-16362 [GSS](7.2.z) Upgrade XNIO from 3.6.5.Final-redhat-00001 to 3.6.6.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-17109 (7.2.z) Upgrade XNIO from 3.6.6.Final-redhat-00001 to 3.7.3.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16364 Clear XnioByteBufferPool.PooledByteBuffer pool when close() to avoid direct memory leaking

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-16363 (7.2.z) XNIO-317 - Introduce API to clean ThreadLocal caches from ByteBufferSlicePool

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) XNIO-317 Introduce API to clean ThreadLocal caches from ByteBufferSlicePool

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17380 (7.2.z) WFCORE-4600 - Memory leak caused by ByteBufferSlicePool usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-12366 (7.4.z) CLI is unable to start embed-server multiple times in a loop

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25789 CLI is unable to start embed-server multiple times in a loop

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) UNDERTOW-1277 Clear XnioByteBufferPool.PooledByteBuffer pool when close() to avoid direct memory leaking

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-support-iweiss Ingo Weiss
              mchoma@redhat.com Martin Choma
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: