3 Replies Latest reply on Jun 19, 2017 12:48 PM by Priyanka Tyagi

    Wildfly 9.0.1, Java 8, solaris sparc java.lang.OutOfMemoryError: Direct buffer memory errors

    Carolina Contiu Newbie

      We are using Wildfly 9.0.1, Java 8, solaris sparc.

       

       

      We are experiencing frequent ERROR [ChannelListeners] (default I/O-1) XNIO001007: A channel event listener threw an exception: java.lang.OutOfMemoryError: Direct buffer memory errors

       ERROR [ChannelListeners] (default I/O-1) XNIO001007: A channel event listener threw an exception: 
      java.lang.OutOfMemoryError: Direct buffer memory at java.nio.Bits.reserveMemory(Bits.java:693) [rt.jar:1.8.0_92]
      at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123) [rt.jar:1.8.0_92]
      at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311) [rt.jar:1.8.0_92]
      at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57) [xnio-api-3.3.1.Final.jar:3.3.1.Final]
      at org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55) [xnio-api-3.3.1.Final.jar:3.3.1.Final]
      at org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:143) [xnio-api-3.3.1.Final.jar:3.3.1.Final]
      at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:139)
      at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:128)
      at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:56)
      at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.3.1.Final.jar:3.3.1.Final]
      at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.3.1.Final.jar:3.3.1.Final]
      at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88) [xnio-nio-3.3.1.Final.jar:3.3.1.Final]
      at org.xnio.nio.WorkerThread.run(WorkerThread.java:539) [xnio-nio-3.3.1.Final.jar:3.3.1.Final]

      We have not determined a particular impact on the application flows. Could you please provide some insight into what is the impact of this error on the application or how to determine the exact root cause.
      Is there a workaround or a library that needs to be upgraded.