OutOfMemoryError：在WildFly中使用WebSocket时直接缓冲内存

问题描述

在我们的WildFly 18服务器上生产一段时间后，我们遇到了此错误：

[org.xnio.listener] (default I/O-1) XNIO001007: A channel event listener threw an exception: 
java.lang.OutOfMemoryError: Direct buffer memory
    at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
    at java.base/java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:118)
    at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:317)
    at [email protected]//org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:57)
    at [email protected]//org.xnio.BufferAllocator$2.allocate(BufferAllocator.java:55)
    at [email protected]//org.xnio.ByteBufferSlicePool.allocateSlices(ByteBufferSlicePool.java:162)
    at [email protected]//org.xnio.ByteBufferSlicePool.allocate(ByteBufferSlicePool.java:149)
    at [email protected]//io.undertow.server.XnioByteBufferPool.allocate(XnioByteBufferPool.java:53)
    at [email protected]//io.undertow.server.protocol.framed.AbstractFramedChannel.allocateReferenceCountedBuffer(AbstractFramedChannel.java:549)
    at [email protected]//io.undertow.server.protocol.framed.AbstractFramedChannel.receive(AbstractFramedChannel.java:370)
    at [email protected]//io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:38)
    at [email protected]//io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:33)
    at [email protected]//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    at [email protected]//io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:950)
    at [email protected]//io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:931)
    at [email protected]//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
    at [email protected]//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
    at [email protected]//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
    at [email protected]//org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

我们通过jxray检查了JVM转储，看来websockets是罪魁祸首：

事实是我们的网络套接字很简单：

@ApplicationScoped
@ServerEndpoint(value = "/ws/messenger/{accountId}")
public class MessengerSocket implements Serializable
{
    private static final long serialVersionUID = -3173234888004281582L;

    @Inject
    private Logger log;
    @Inject
    private MessengerHandler handler;

    @Onopen
    public void onopen(@PathParam("accountId") String accountId,Session session,EndpointConfig config)
    {
        log.debug("opening for {}",accountId);
        handler.subscribeSocket(session,UUID.fromString(accountId));
    }

    @OnClose
    public void onClose(@PathParam("accountId") String accountId,CloseReason closeReason)
    {
        log.debug("Closing {}",accountId);
        handler.unsubscribeSocket(session,UUID.fromString(accountId));
    }
}

它与一个简单的处理程序结合在一起，可以管理用户会话图：

@ApplicationScoped
public class MessengerHandler
{
    @Inject
    private Logger log;

    // key: Account id
    private Map<UUID,AccountMessengerSessions> sessions;

    public void init()
    {
        sessions = new ConcurrentHashMap<>();
    }

    public void subscribeSocket(Session session,UUID accountId)
    {
        // build and store the account messenger session if new
        AccountMessengerSessions messenger = sessions.getorDefault(accountId,new AccountMessengerSessions(accountId));
        messenger.getWsSessions().add(session);
        sessions.putIfAbsent(accountId,messenger);
        log.debug("{} has {} messenger socket session(s) (one added)",messenger.getAccountId(),messenger.getWsSessions().size());
    }

    /**
     * Unsubscribes the provided WebSocket from the Messenger.
     */
    public void unsubscribeSocket(Session session,UUID accountId)
    {
        if (!sessions.containsKey(accountId))
        {
            log.warn("Ignore unsubscription from {} socket,as {} is unknwon from messenger",session.getId(),accountId);
            return;
        }
        AccountMessengerSessions messenger = sessions.get(accountId);
        messenger.getWsSessions().remove(session);
        log.debug("{} has {} messenger socket session(s) (one removed)",messenger.getWsSessions().size());
        if (!messenger.getWsSessions().isEmpty())
        {
            return;
        }
        // no more socket sessions,fully remove
        sessions.remove(messenger.getAccountId());
    }
}

客户端，页面加载时，我们会调用一些javascript，同样，没有花哨：

var accountId = // some string found in DOM
var websocketUrl = "wss://" + window.location.host + "/ws/messenger/" + accountId;
var websocket = new WebSocket(websocketUrl);
websocket.onmessage = function (event) {
  var data = JSON.parse(event.data);
  // nothing fancy here...
};

我们的用户没有使用websocket（即时通讯程序）所提供的功能，因此在生产中真正发生的事情基本上是在每个页面上打开和关闭websocket，很少发送消息。

在哪里可以弄错并造成此缓冲区泄漏？我们忘记了关键的事情吗？

解决方法

看看这个post，如果您有很多CPU，则可能会发生这种情况。通过减少IO工人的数量解决了这一问题。不确定这是否对您有帮助。