WildFly 17.0.1最后HeapMemory问题

Question

我需要一些建议或指导野生苍蝇版本，这是在最近的生产。

我们经常看到堆内存峰值，垃圾收集无法工作，堆被填充，达到最大2GB(这是堆的分配)，我们需要重新启动应用程序才能恢复正常。当我们分析内存转储时，我们找不到应用程序代码中的任何问题，但是我们发现有一个类占用了更多的内存。该类与ActiveMQ & WildFly集成相关，后者应用程序使用MDB，我们使用EJB3.0。并请更多地，我们使用亚马逊Corretto与WildFly。请您注意到WildFly中有关以下对象的问题。

当我们分析内存中的堆栈跟踪和对象时，下面的对象拥有更多的内存，它来自WildFly类。请有人分享有关这方面的任何想法或想法。

我们使用的是野蝇-17.0.1.Final和Corretto-8.212.04.2 (构建1.8.0_212-b04)。下面是JVM的配置

<jvms>
    <jvm name="default">
        <heap size="2048m" max-size="2048m"/>
        <jvm-options>
            <option value="-server"/>
            <option value="-XX:MetaspaceSize=256m"/>
            <option value="-XX:MaxMetaspaceSize=256m"/>
        </jvm-options>
    </jvm>

堆堆栈跟踪如下所示

**`**Who reference 1.25gb (71.7%) of byte[]?`**

Java静态org.wildfly.extension.messaging.activemq.broadcast.CommandDispatcherBroadcastEndpointFactory.BROADCAST_MANAGERS {java.util.concurrent.ConcurrentHashMap}.values org.wildfly.extension.messaging.activemq.broadcast.QueueBroadcastManager.broadcasts {java.util.concurrent.LinkedBlockingDeque}** 1,196,563 K **(65.3%)

我们正在野生蝇集群环境上运行我们的J2EE应用程序，其配置文件为"full-ha“，请查找我们的ACTIVEMQ配置文件。

 <subsystem xmlns="urn:jboss:domain:messaging-activemq:7.0">
            <server name="default">
                <cluster password="password"/>
                <statistics enabled="${wildfly.messaging-activemq.statistics-enabled:${wildfly.statistics-enabled:false}}"/>
                <security-setting name="#">
                    <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>
                </security-setting>
                <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/>
                <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>
                <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">
                    <param name="batch-delay" value="50"/>
                </http-connector>
                <in-vm-connector name="in-vm" server-id="0">
                    <param name="buffer-pooling" value="false"/>
                </in-vm-connector>
                <http-acceptor name="http-acceptor" http-listener="default"/>
                <http-acceptor name="http-acceptor-throughput" http-listener="default">
                    <param name="batch-delay" value="50"/>
                    <param name="direct-deliver" value="false"/>
                </http-acceptor>
                <in-vm-acceptor name="in-vm" server-id="0">
                    <param name="buffer-pooling" value="false"/>
                </in-vm-acceptor>
                <broadcast-group name="bg-group1" jgroups-cluster="activemq-cluster" connectors="http-connector"/>
                <discovery-group name="dg-group1" jgroups-cluster="activemq-cluster"/>
                <cluster-connection name="my-cluster" address="jms" connector-name="http-connector" discovery-group="bg-group1"/>
                <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
                <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
                <jms-queue name="CSVProcessPendingMessageBean" entries="java:/jms/queue/CSV_PROCESS_PENDING_Q java:jboss/exported/jms/queue/CSV_PROCESS_PENDING_Q"/>
                <jms-queue name="CSVUploadQMessageBean" entries="java:/jms/queue/CSV_UPLOAD_Q java:jboss/exported/jms/queue/CSV_UPLOAD_Q"/>
                <jms-queue name="InboundQMessageBean" entries="java:/jms/queue/CSV_INBOUND_Q java:jboss/exported/jms/queue/CSV_INBOUND_Q"/>
                <jms-queue name="OutboundQMessageBean" entries="java:/jms/queue/CSV_OUTBOUND_Q java:jboss/exported/jms/queue/CSV_OUTBOUND_Q"/>
                <jms-queue name="OutboundMessageBean" entries="java:/jms/queue/VFOREQUEST_Q java:jboss/exported/jms/queue/VFOREQUEST_Q"/>
                <jms-queue name="AutoManualInboundMessageBean" entries="java:/jms/queue/VFOAUTOMANUALRESPOSE_Q java:jboss/exported/jms/queue/VFOAUTOMANUALRESPOSE_Q"/>
                <jms-queue name="InboundMessageBean" entries="java:/jms/queue/VFORESPONSE_Q java:jboss/exported/jms/queue/VFORESPONSE_Q"/>
                <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>
                <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector" ha="true" block-on-acknowledge="true" reconnect-attempts="-1"/>
                <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
            </server>
        </subsystem>

Answer 1

也有同样的问题。这就是问题所在，因为我们搬到Azure，那里不支持多播：

<broadcast-group name="bg-group1" jgroups-cluster="activemq-cluster" connectors="http-connector"/>