[jira] [Commented] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[
https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704306#comment-17704306
]
Timothy A. Bish commented on ARTEMIS-4217:
--
You could potentially work around this for now by increasing the
'{{{}minLargeMessageSize{}}}' option to avoid having core large messages which
get converted to AMQP messages as they cross to the AMQP client.
> AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
>
>
> Key: ARTEMIS-4217
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
>Affects Versions: 2.28.0
> Environment: Windows Server 2022 21H2
> openjdk 19.0.1 2022-10-18
> OpenJDK Runtime Environment (build 19.0.1+10-21)
> OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
>Reporter: daves
>Priority: Major
> Attachments: artemis-service.wrapper.log, artemis.log,
> artemis.log.2023-03-23-1.log.gz, artemis.log.2023-03-23-10.log.gz,
> artemis.log.2023-03-23-100.log.gz, artemis.log.2023-03-23-11.log.gz,
> artemis.log.2023-03-23-12.log.gz, artemis.log.2023-03-23-13.log.gz,
> artemis.log.2023-03-23-14.log.gz, artemis.log.2023-03-23-15.log.gz,
> artemis.log.2023-03-23-16.log.gz, artemis.log.2023-03-23-17.log.gz,
> artemis.log.2023-03-23-18.log.gz, artemis.log.2023-03-23-19.log.gz,
> artemis.log.2023-03-23-2.log.gz, artemis.log.2023-03-23-20.log.gz,
> artemis.log.2023-03-23-21.log.gz, artemis.log.2023-03-23-22.log.gz,
> artemis.log.2023-03-23-23.log.gz, artemis.log.2023-03-23-24.log.gz,
> artemis.log.2023-03-23-25.log.gz, artemis.log.2023-03-23-26.log.gz,
> artemis.log.2023-03-23-27.log.gz, artemis.log.2023-03-23-28.log.gz,
> artemis.log.2023-03-23-29.log.gz, artemis.log.2023-03-23-3.log.gz,
> artemis.log.2023-03-23-30.log.gz, artemis.log.2023-03-23-31.log.gz,
> artemis.log.2023-03-23-32.log.gz, artemis.log.2023-03-23-33.log.gz,
> artemis.log.2023-03-23-34.log.gz, artemis.log.2023-03-23-35.log.gz,
> artemis.log.2023-03-23-36.log.gz, artemis.log.2023-03-23-37.log.gz,
> artemis.log.2023-03-23-38.log.gz, artemis.log.2023-03-23-39.log.gz,
> artemis.log.2023-03-23-4.log.gz, artemis.log.2023-03-23-40.log.gz,
> artemis.log.2023-03-23-41.log.gz, artemis.log.2023-03-23-42.log.gz,
> artemis.log.2023-03-23-43.log.gz, artemis.log.2023-03-23-44.log.gz,
> artemis.log.2023-03-23-45.log.gz, artemis.log.2023-03-23-46.log.gz,
> artemis.log.2023-03-23-47.log.gz, artemis.log.2023-03-23-48.log.gz,
> artemis.log.2023-03-23-49.log.gz, artemis.log.2023-03-23-5.log.gz,
> artemis.log.2023-03-23-50.log.gz, artemis.log.2023-03-23-51.log.gz,
> artemis.log.2023-03-23-52.log.gz, artemis.log.2023-03-23-53.log.gz,
> artemis.log.2023-03-23-54.log.gz, artemis.log.2023-03-23-55.log.gz,
> artemis.log.2023-03-23-56.log.gz, artemis.log.2023-03-23-57.log.gz,
> artemis.log.2023-03-23-58.log.gz, artemis.log.2023-03-23-59.log.gz,
> artemis.log.2023-03-23-6.log.gz, artemis.log.2023-03-23-60.log.gz,
> artemis.log.2023-03-23-61.log.gz, artemis.log.2023-03-23-62.log.gz,
> artemis.log.2023-03-23-63.log.gz, artemis.log.2023-03-23-64.log.gz,
> artemis.log.2023-03-23-65.log.gz, artemis.log.2023-03-23-66.log.gz,
> artemis.log.2023-03-23-67.log.gz, artemis.log.2023-03-23-68.log.gz,
> artemis.log.2023-03-23-69.log.gz, artemis.log.2023-03-23-7.log.gz,
> artemis.log.2023-03-23-70.log.gz, artemis.log.2023-03-23-71.log.gz,
> artemis.log.2023-03-23-72.log.gz, artemis.log.2023-03-23-73.log.gz,
> artemis.log.2023-03-23-74.log.gz, artemis.log.2023-03-23-75.log.gz,
> artemis.log.2023-03-23-76.log.gz, artemis.log.2023-03-23-77.log.gz,
> artemis.log.2023-03-23-78.log.gz, artemis.log.2023-03-23-79.log.gz,
> artemis.log.2023-03-23-8.log.gz, artemis.log.2023-03-23-80.log.gz,
> artemis.log.2023-03-23-81.log.gz, artemis.log.2023-03-23-82.log.gz,
> artemis.log.2023-03-23-83.log.gz, artemis.log.2023-03-23-84.log.gz,
> artemis.log.2023-03-23-85.log.gz, artemis.log.2023-03-23-86.log.gz,
> artemis.log.2023-03-23-87.log.gz, artemis.log.2023-03-23-88.log.gz,
> artemis.log.2023-03-23-89.log.gz, artemis.log.2023-03-23-9.log.gz,
> artemis.log.2023-03-23-90.log.gz, artemis.log.2023-03-23-91.log.gz,
> artemis.log.2023-03-23-92.log.gz, artemis.log.2023-03-23-93.log.gz,
> artemis.log.2023-03-23-94.log.gz, artemis.log.2023-03-23-95.log.gz,
> artemis.log.2023-03-23-96.log.gz, artemis.log.2023-03-23-97.log.gz,
> artemis.log.2023-03-23-98.log.gz, artemis.log.2023-03-23-99.log.gz
>
>
> Some of the AMQP messages sent by my client never arrive at the consumer. In
> the Artemis log I found the following exception:
>
>
> {code:java}
> 2023-03-23 18:06:58,084 WARN
> [org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to
> convert message. Sending
[jira] [Updated] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
[ https://issues.apache.org/jira/browse/ARTEMIS-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] daves updated ARTEMIS-4217: --- Attachment: artemis.log.2023-03-23-94.log.gz artemis.log.2023-03-23-95.log.gz artemis.log.2023-03-23-96.log.gz artemis.log.2023-03-23-97.log.gz artemis.log.2023-03-23-98.log.gz artemis.log.2023-03-23-99.log.gz artemis.log.2023-03-23-100.log.gz artemis-service.wrapper.log artemis.log.2023-03-23-15.log.gz artemis.log.2023-03-23-16.log.gz artemis.log.2023-03-23-17.log.gz artemis.log.2023-03-23-18.log.gz artemis.log.2023-03-23-19.log.gz artemis.log.2023-03-23-20.log.gz artemis.log.2023-03-23-21.log.gz artemis.log.2023-03-23-22.log.gz artemis.log.2023-03-23-23.log.gz artemis.log.2023-03-23-24.log.gz artemis.log.2023-03-23-25.log.gz artemis.log.2023-03-23-26.log.gz artemis.log.2023-03-23-27.log.gz artemis.log.2023-03-23-28.log.gz artemis.log.2023-03-23-29.log.gz artemis.log.2023-03-23-30.log.gz artemis.log.2023-03-23-31.log.gz artemis.log.2023-03-23-32.log.gz artemis.log.2023-03-23-33.log.gz artemis.log.2023-03-23-34.log.gz artemis.log.2023-03-23-35.log.gz artemis.log.2023-03-23-36.log.gz artemis.log.2023-03-23-37.log.gz artemis.log.2023-03-23-38.log.gz artemis.log.2023-03-23-39.log.gz artemis.log.2023-03-23-40.log.gz artemis.log.2023-03-23-41.log.gz artemis.log.2023-03-23-42.log.gz artemis.log.2023-03-23-43.log.gz artemis.log.2023-03-23-44.log.gz artemis.log.2023-03-23-45.log.gz artemis.log.2023-03-23-46.log.gz artemis.log.2023-03-23-47.log.gz artemis.log.2023-03-23-48.log.gz artemis.log.2023-03-23-49.log.gz artemis.log.2023-03-23-50.log.gz artemis.log.2023-03-23-51.log.gz artemis.log.2023-03-23-52.log.gz artemis.log.2023-03-23-53.log.gz artemis.log.2023-03-23-54.log.gz artemis.log.2023-03-23-55.log.gz artemis.log.2023-03-23-56.log.gz artemis.log.2023-03-23-57.log.gz artemis.log.2023-03-23-58.log.gz artemis.log.2023-03-23-59.log.gz artemis.log.2023-03-23-60.log.gz artemis.log.2023-03-23-61.log.gz artemis.log.2023-03-23-62.log.gz artemis.log.2023-03-23-63.log.gz artemis.log.2023-03-23-64.log.gz artemis.log.2023-03-23-65.log.gz artemis.log.2023-03-23-66.log.gz artemis.log.2023-03-23-67.log.gz artemis.log.2023-03-23-68.log.gz artemis.log.2023-03-23-69.log.gz artemis.log.2023-03-23-70.log.gz artemis.log.2023-03-23-71.log.gz artemis.log.2023-03-23-72.log.gz artemis.log.2023-03-23-73.log.gz artemis.log.2023-03-23-74.log.gz artemis.log.2023-03-23-75.log.gz artemis.log.2023-03-23-76.log.gz artemis.log.2023-03-23-77.log.gz artemis.log.2023-03-23-78.log.gz artemis.log.2023-03-23-79.log.gz artemis.log.2023-03-23-80.log.gz artemis.log.2023-03-23-81.log.gz artemis.log.2023-03-23-82.log.gz artemis.log.2023-03-23-83.log.gz artemis.log.2023-03-23-84.log.gz artemis.log.2023-03-23-85.log.gz artemis.log.2023-03-23-86.log.gz artemis.log.2023-03-23-87.log.gz artemis.log.2023-03-23-88.log.gz artemis.log.2023-03-23-89.log.gz artemis.log.2023-03-23-90.log.gz artemis.log.2023-03-23-91.log.gz artemis.log.2023-03-23-92.log.gz artemis.log.2023-03-23-93.log.gz > AMQ111005: Failed to convert message. Sending it to Dead Letter Address. > > > Key: ARTEMIS-4217 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4217 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP >Affects Versions: 2.28.0 > Environment: Windows Server 2022 21H2 > openjdk 19.0.1 2022-10-18 > OpenJDK Runtime Environment (build 19.0.1+10-21) > OpenJDK 64-Bit Server VM (build
[jira] [Created] (ARTEMIS-4217) AMQ111005: Failed to convert message. Sending it to Dead Letter Address.
daves created ARTEMIS-4217:
--
Summary: AMQ111005: Failed to convert message. Sending it to Dead
Letter Address.
Key: ARTEMIS-4217
URL: https://issues.apache.org/jira/browse/ARTEMIS-4217
Project: ActiveMQ Artemis
Issue Type: Bug
Components: AMQP
Affects Versions: 2.28.0
Environment: Windows Server 2022 21H2
openjdk 19.0.1 2022-10-18
OpenJDK Runtime Environment (build 19.0.1+10-21)
OpenJDK 64-Bit Server VM (build 19.0.1+10-21, mixed mode, sharing)
Reporter: daves
Attachments: artemis.log, artemis.log.2023-03-23-1.log.gz,
artemis.log.2023-03-23-10.log.gz, artemis.log.2023-03-23-11.log.gz,
artemis.log.2023-03-23-12.log.gz, artemis.log.2023-03-23-13.log.gz,
artemis.log.2023-03-23-14.log.gz, artemis.log.2023-03-23-2.log.gz,
artemis.log.2023-03-23-3.log.gz, artemis.log.2023-03-23-4.log.gz,
artemis.log.2023-03-23-5.log.gz, artemis.log.2023-03-23-6.log.gz,
artemis.log.2023-03-23-7.log.gz, artemis.log.2023-03-23-8.log.gz,
artemis.log.2023-03-23-9.log.gz
Some of the AMQP messages sent by my client never arrive at the consumer. In
the Artemis log I found the following exception:
{code:java}
2023-03-23 18:06:58,084 WARN
[org.apache.activemq.artemis.protocol.amqp.logger] AMQ111005: Failed to convert
message. Sending it to Dead Letter Address.
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.ConversionException:
java.nio.channels.ClosedChannelException at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:318)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.checkAMQP(CoreAmqpConverter.java:79)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.proton.ProtonServerSenderContext.executeDelivery(ProtonServerSenderContext.java:561)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.server.impl.MessageReferenceImpl.run(MessageReferenceImpl.java:131)
~[artemis-server-2.28.0.jar:2.28.0] at
io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
~[netty-transport-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
~[netty-common-4.1.86.Final.jar:4.1.86.Final] at
org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
~[artemis-commons-2.28.0.jar:?] Caused by: java.lang.RuntimeException:
java.nio.channels.ClosedChannelException at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:293)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBodyLength(CoreBytesMessageWrapper.java:98)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.getBinaryFromMessageBody(CoreBytesMessageWrapper.java:68)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.coreWrapper.CoreBytesMessageWrapper.createAMQPSection(CoreBytesMessageWrapper.java:78)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.protocol.amqp.converter.CoreAmqpConverter.fromCore(CoreAmqpConverter.java:106)
~[artemis-amqp-protocol-2.28.0.jar:2.28.0] ... 10 more Caused by:
java.nio.channels.ClosedChannelException at
sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:165) ~[?:?] at
sun.nio.ch.FileChannelImpl.size(FileChannelImpl.java:416) ~[?:?] at
org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.size(NIOSequentialFile.java:339)
~[artemis-journal-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeBody.getBodyBufferSize(LargeBody.java:285)
~[artemis-server-2.28.0.jar:2.28.0] at
org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.getBodyBufferSize(LargeServerMessageImpl.java:263)
~[artemis-server-2.28.0.jar:2.28.0] at
[jira] [Commented] (ARTEMIS-4095) OpenWire clients are unable to consume from mutlicast queue after 2nd paging
[
https://issues.apache.org/jira/browse/ARTEMIS-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704232#comment-17704232
]
Artyom Tarasenko commented on ARTEMIS-4095:
---
The problem is also reproducible with WildFly-20 and the following consumer:
{code:java}
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
import org.jboss.ejb3.annotation.ResourceAdapter;
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="OrdersChannel::OrdersQueue1#OrdersChannel"),
})
@ResourceAdapter("amq-ra.rar")
public class MdbConsumer implements MessageListener {
@Override
public void onMessage(Message ignored) {
// do nothing
}
}{code}
(The code for the jms consumer is the same as in the attached
[^jmsconsumer-1.0-SNAPSHOT.jar] used in the reproducer scenario above, with one
line difference as the import for ResouceAdapter annotation has been changed
after the 4.2.3 release).
The fact that the bug is reproducible not just with the ancient JBoss, but also
with modern WildFly (and likely any other AS which use activemq-5.x.rar)
probably rises the criticality of the bug?
> OpenWire clients are unable to consume from mutlicast queue after 2nd paging
>
>
> Key: ARTEMIS-4095
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4095
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
>Affects Versions: 2.26.0, 2.27.0, 2.27.1
> Environment: Artemis, deployed through the official docker image in
> version {{2.26.0}} in an OpenShift cluster
>Reporter: Marco Bungart
>Priority: Major
> Attachments: artemis-Xmx1G.png, artemis-Xmx2G.png, graph1.png,
> graph2.png, jmeter-orders-6500-localhost.jmx, jmsconsumer-1.0-SNAPSHOT.jar
>
>
> I observed that after artemis went into paging for the 2nd time, OpenWire
> clients were not able to read messages from their corresponding addresses.
> Restarting the applications connected as clients does not fix the issue.
> Restarting artemis, however, does fix the issue.
> Both images attached show the messages of two queues.
> - The upper (orange) line in the 1st graph shows count of messages in a queue
> to which core clients are connected.
> - The lower (blue) line in the 1stg raph shows count of messages in a queue
> to which OpenWire clients are connected.
> - in the 2nd graph, the upper (violet) line shows count of messages in a
> queue to which core clients are connected.
> - in the 2nd graph, the lower (green) line shows count of messages in a queue
> to which OpenWire clients are connected.
> I have a heap dump that we could share, showing the accumulated objects. the
> dump is about 90 MB in size If this would be helpful to have, please let me
> know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
