we switched from WildFly 13 to WildFly 26
in the past we got trouble with largeMessages. the buffers remained in memory and after a while the server runs out of memory.
so we decided to disable the largeMessages for us, setting the min-large-message size to 25 MB
<connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm" consumer-window-size="-1" producer-window-size="-1" min-large-message-size="25242880" scheduled-thread-pool-max-size="50" thread-pool-max-size="250"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" consumer-window-size="-1" producer-window-size="-1" min-large-message-size="25242880" scheduled-thread-pool-max-size="50" thread-pool-max-size="-1" transaction="xa" min-pool-size="50" max-pool-size="100"/>
this works fine for us.
now in WildFly 26 we are facing the problem again.
the min-large-message-size doesn't seem to work.
even we set the minimum to 25 MB like under WildFly 13 LargeMessages are created.
e.g. we got the following trace message
2022-05-03 15:07:27,428 TRACE [org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler] (Thread-3 (ActiveMQ-client-global-threads)) onMessage(ClientLargeMessageImpl[messageID=90295, durable=false, address=jms.topic.TRANSIENT,userID=fb40250a-cae1-11ec-97dd-dc7196878430,properties=TypedProperties[__AMQ_CID=9f6632c2-cae1-11ec-97dd-dc7196878430,CLIENT=app1,MSGID=pool-28-thread-61229995242071200,PROCESSOR=getTypeDescendants,REPOSITORYID=20000665_4,_AMQ_ROUTING_TYPE=0,MESSAGE_TYPE=TEXT,JMSCorrelationID=LM (default task-1)1229995171072700,_AMQ_LARGE_SIZE=513613]])
with _AMQ_LARGE_SIZE= 513613.
and these messages remain in memory
any idea what is wrong here?
regards
Sascha